Open editorialbot opened 5 months ago
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
β
OK DOIs
- 10.1017/cbo9780511617652.004 is OK
- 10.1093/acrefore/9780190228620.013.826 is OK
π‘ SKIP DOIs
- None
β MISSING DOIs
- None
β INVALID DOIs
- None
@editorialbot set v1.0.3 as version
I'm sorry @dhruvbalwada, I'm afraid I can't do that. That's something only editors are allowed to do.
@editorialbot set v1.0.3 as version
Done! version is now v1.0.3
@editorialbot set 10.5281/zenodo.13357587 as doi
I'm sorry human, I don't understand that. You can see what commands I support by typing:
@editorialbot commands
@editorialbot set 10.5281/zenodo.13357587 as archive
Done! archive is now 10.5281/zenodo.13357587
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
β
OK DOIs
- 10.1017/cbo9780511617652.004 is OK
- 10.1093/acrefore/9780190228620.013.826 is OK
π‘ SKIP DOIs
- None
β MISSING DOIs
- None
β INVALID DOIs
- None
:wave: @openjournals/jose-eics, this paper is ready to be accepted and published.
Check final proof :point_right::page_facing_up: Download article
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/jose-papers/pull/150, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@magsol - wondering if we need to do anything else for the final/next step?
@dhruvbalwada Nope, only @openjournals/jose-eics can make the final acceptance. We just have to sit tight :)
@magsol - I noticed that the tag @openjournals/jose-eics doesn't seem to link to anything. Is there anything else we can do to help push things along?
@dhruvbalwada Like the checkboxes in the editor checklist above, that link requires certain permissions to view; suffice to say it does link to the list of EiCs for JOSE.
That said, we still just have to sit tight. I'm pinging the EiCs but otherwise they're the only ones who can finalize the acceptance. I know it's taking awhile and I deeply appreciate your patience; we're almost there.
Submitting author: !--author-handle-->@dhruvbalwada<!--end-author-handle-- (Dhruv Balwada) Repository: https://github.com/m2lines/L96_demo Branch with paper.md (empty if default branch): Version: v1.0.3 Editor: !--editor-->@magsol<!--end-editor-- Reviewers: @micky774, @AnonymousFool Archive: 10.5281/zenodo.13357587 Paper kind: learning module
Status
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@micky774 & @AnonymousFool, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review. First of all you need to run this command in a separate comment to create the checklist:
The reviewer guidelines are available here: https://openjournals.readthedocs.io/en/jose/reviewer_guidelines.html. Any questions/concerns please let @magsol know.
β¨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest β¨
Checklists
π Checklist for @Micky774
π Checklist for @AnonymousFool