Closed editorialbot closed 1 year ago
It is possible to edit the metadata on zenodo, which is what we usually do to reflect the authors on the paper. If you are not able to do it, it's not a big deal, we can wave this requirement, which is why I didn't mention it in my last message.
@Bisaloo I believe I was able to update the metadata.
@editorialbot set 10.5281/zenodo.8015102 as archive
Done! archive is now 10.5281/zenodo.8015102
@editorialbot set v1.0.0 as version
Done! version is now v1.0.0
Thanks for the PR @Bisaloo, I merged it.
@editorialbot generate pdf
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1111/faf.12174 is OK
- 10.1016/j.fishres.2018.03.010 is OK
- 10.1111/faf.12398 is OK
- 10.1101/2022.03.24.485545 is OK
- 10.1016/j.fishres.2018.10.013 is OK
- 10.1111/1365-2664.12664 is OK
- 10.1093/icesjms/fsz048 is OK
- 10.1093/icesjms/fsv229 is OK
- 10.1890/14-0739.1 is OK
- 10.1093/icesjms/fsw230 is OK
- 10.1111/j.1467-2979.2011.00452.x is OK
- 10.1146/annurev.ecolsys.39.110707.173406 is OK
- 10.1111/faf.12550 is OK
- 10.1139/F08-170 is OK
- 10.1139/f03-105 is OK
- 10.1890/14-0739.1 is OK
- 10.1111/j.1467-2979.2012.00488.x is OK
MISSING DOIs
- None
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Thanks, I submitted one last PR (https://github.com/pedersen-fisheries-lab/sspm/pull/144) to fix the format for co-first authors and everything is ready for acceptance after this!
just saw, I merged it
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1111/faf.12174 is OK
- 10.1016/j.fishres.2018.03.010 is OK
- 10.1111/faf.12398 is OK
- 10.1101/2022.03.24.485545 is OK
- 10.1016/j.fishres.2018.10.013 is OK
- 10.1111/1365-2664.12664 is OK
- 10.1093/icesjms/fsz048 is OK
- 10.1093/icesjms/fsv229 is OK
- 10.1890/14-0739.1 is OK
- 10.1093/icesjms/fsw230 is OK
- 10.1111/j.1467-2979.2011.00452.x is OK
- 10.1146/annurev.ecolsys.39.110707.173406 is OK
- 10.1111/faf.12550 is OK
- 10.1139/F08-170 is OK
- 10.1139/f03-105 is OK
- 10.1890/14-0739.1 is OK
- 10.1111/j.1467-2979.2012.00488.x is OK
MISSING DOIs
- None
INVALID DOIs
- None
:warning: Error preparing paper acceptance. The generated XML metadata file is invalid.
ID ref-thorson_importance_2015 already defined
I see the error, the ref thorson_importance_2015
is defined twice. I'll fix it now.
It should be fixed now.
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1111/faf.12174 is OK
- 10.1016/j.fishres.2018.03.010 is OK
- 10.1111/faf.12398 is OK
- 10.1101/2022.03.24.485545 is OK
- 10.1016/j.fishres.2018.10.013 is OK
- 10.1111/1365-2664.12664 is OK
- 10.1093/icesjms/fsz048 is OK
- 10.1093/icesjms/fsv229 is OK
- 10.1890/14-0739.1 is OK
- 10.1093/icesjms/fsw230 is OK
- 10.1111/j.1467-2979.2011.00452.x is OK
- 10.1146/annurev.ecolsys.39.110707.173406 is OK
- 10.1111/faf.12550 is OK
- 10.1139/F08-170 is OK
- 10.1139/f03-105 is OK
- 10.1111/j.1467-2979.2012.00488.x is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/ese-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/joss-papers/pull/4328, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Looks good to me.
Here is my to do list:
@editorialbot accept
Doing it live! Attempting automated processing of paper acceptance...
Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.
If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.
You can copy the contents for your CITATION.cff file here:
``` cff-version: "1.2.0" authors: - family-names: Lucet given-names: Valentin orcid: "https://orcid.org/0000-0003-0268-818X" - family-names: Pedersen given-names: Eric J. orcid: "https://orcid.org/0000-0003-1016-540X" doi: 10.5281/zenodo.8015102 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Lucet given-names: Valentin orcid: "https://orcid.org/0000-0003-0268-818X" - family-names: Pedersen given-names: Eric J. orcid: "https://orcid.org/0000-0003-1016-540X" date-published: 2023-06-22 doi: 10.21105/joss.04724 issn: 2475-9066 issue: 86 journal: Journal of Open Source Software publisher: name: Open Journals start: 4724 title: The sspm R package for spatially-explicit surplus production population models type: article url: "https://joss.theoj.org/papers/10.21105/joss.04724" volume: 8 title: The sspm R package for spatially-explicit surplus production population models ```
If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦
🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨
Here's what you must now do:
Any issues? Notify your editorial technical team...
Congratulations @VLucet @eric-pedersen :tada::tada:!
Thanks a lot for your thorough and informative reviews @kellijohnson-NOAA @quang-huynh :pray::pray:!
Yay! Thanks to you @Bisaloo as well!
Congrats on your new publication @VLucet!! Many thanks to editor @Bisaloo and reviewers @quang-huynh and @kellijohnson-NOAA for your time, hard work, and expertise!!
:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:
If you would like to include a link to your paper from your README use the following code snippets:
Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.04724/status.svg)](https://doi.org/10.21105/joss.04724)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04724">
<img src="https://joss.theoj.org/papers/10.21105/joss.04724/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04724/status.svg
:target: https://doi.org/10.21105/joss.04724
This is how it will look in your documentation:
We need your help!
The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:
Submitting author: !--author-handle-->@VLucet<!--end-author-handle-- (Valentin Lucet) Repository: https://github.com/pedersen-fisheries-lab/sspm Branch with paper.md (empty if default branch): main Version: v1.0.0 Editor: !--editor-->@Bisaloo<!--end-editor-- Reviewers: @quang-huynh, @kellijohnson-NOAA Archive: 10.5281/zenodo.8015102
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
@quang-huynh & @kellijohnson-NOAA, 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://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @Bisaloo 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 @quang-huynh
📝 Checklist for @kellijohnson-NOAA