Closed editorialbot closed 7 months ago
@crvernon ๐ Please check the following repo:
:wave: @SongshGeo - Please change your declared license in the Zenodo archive (currently creative commons attribution 4.0 international) to match what you use for your software (Apache License 2.0).
Also, your Zenodo archive name has to match the name of your paper. Please adjust accordingly.
Let me know when you have this done and I'll move forward. Thanks!
@editorialbot set 0.5.5 as version
Done! version is now 0.5.5
@editorialbot set 10.5281/zenodo.10934351 as archive
Done! archive is now 10.5281/zenodo.10934351
@crvernon Hi, thanks for reminding me. I've changed the information. However, when I double-checked the paper, I found that the funding information needs to be slightly modified. Thus, I created a new release, v0.5.6. There are also some format improvements without changing features in this latest version. Please set 0.5.6 as the version and archive. Sorry about this change.
v0.5.6: 10.5281/zenodo.10935937
@editorialbot set 0.5.6 as version
Done! version is now 0.5.6
@editorialbot set 10.5281/zenodo.10935937 as archive
Done! archive is now 10.5281/zenodo.10935937
@editorialbot set <DOI here> as archive
@editorialbot set <version here> as version
@editorialbot generate pdf
@editorialbot check references
and ask author(s) to update as needed@editorialbot recommend-accept
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@SongshGeo it looks like one of your co-authors names appear differently between what is in the paper (Elรญas Josรฉ Mantilla) versus what is in the Zenodo archive (Elรญas Josรฉ Mantilla Ibarra).
Also, you have ORCIDs for some authors in archive that do not have the ORCID listed in the paper.
Please make these consistent.
No need to conduct another release. Thanks!
@crvernon Hi, Sorry. I sometimes struggle with Western names ๐. Now, I updated the ORCIDs in the paper and the name in the Zenodo archive.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
๐ - @SongshGeo I am recommending that this submission be accepted for publication. An EiC will review shortly and if all goes well this will go live soon! Thanks to @wang-boyu and @jamesdamillington for a timely and constructive review!
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1201/9780429496639 is OK
- 10.1680/ensu.2011.164.2.129 is OK
- 10.1038/s41562-022-01478-5 is OK
- 10.4324/9781003021339 is OK
- 10.1016/j.envsoft.2015.08.018 is OK
- 10.1038/s41562-017-0181-7 is OK
- 10.1111/gwat.12569 is OK
- 10.1016/j.gloenvcha.2019.101972 is OK
- 10.1007/978-3-030-29443-4_9 is OK
- 10.1177/1745691614527464 is OK
- 10.5751/es-03610-150420 is OK
- 10.5751/ES-08748-210341 is OK
- 10.21105/joss.03065 is OK
- 10.1016/j.ecocom.2018.07.007 is OK
- 10.1017/S1355770X12000460 is OK
- 10.1146/annurev-environ-110615-085349 is OK
- 10.1016/j.ecolecon.2016.08.008 is OK
- 10.18564/jasss.3423 is OK
- 10.3389/fnins.2015.00332 is OK
- 10.1145/3557989.3566157 is OK
- 10.1177/1464993413486544 is OK
- 10.1073/pnas.2215674121 is OK
- 10.1073/pnas.2215676120 is OK
- 10.5334/jors.148 is OK
MISSING DOIs
- No DOI given, and none found for title: Applying Plural Rationality to Some Wicked Problem...
- No DOI given, and none found for title: Plural Rationality and Interactive Decision Proces...
- No DOI given, and none found for title: Towards a Community Framework for Agent-Based Mode...
- No DOI given, and none found for title: Utilizing Python for agent-based modeling: The Mes...
- No DOI given, and none found for title: MODFLOW 6 modular hydrologic model version 6.2. 1:...
- No DOI given, and none found for title: Complexity: A guided tour
- No DOI given, and none found for title: Understanding Institutional Diversity
- 10.1007/978-3-319-67217-5_2 may be a valid DOI for title: ABCE: A Python library for economic agent-based mo...
- No DOI given, and none found for title: NetLogo: A simple environment for modeling complex...
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/5228, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@crvernon Hi, I cannot download the proof article from the above link. When I tried to check the PDF file from JOSS's GitHub repo, I got the following error:
Error rendering embedded code Invalid PDF
Hi I can take over from here. My steps are:
@SongshGeo Please check the capitalization in your references. You can preserve capitalization by placing {} around characters/words in your .bib file. I think "earth" and "anthropocene" should be capitalized right?
@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 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: Song given-names: Shuang orcid: "https://orcid.org/0000-0002-8112-8780" - family-names: Wang given-names: Shuai orcid: "https://orcid.org/0000-0003-1595-9858" - family-names: Jiao given-names: Chentai orcid: "https://orcid.org/0000-0003-1737-9814" - family-names: Ibarra given-names: Elรญas Josรฉ Mantilla contact: - family-names: Wang given-names: Shuai orcid: "https://orcid.org/0000-0003-1595-9858" doi: 10.5281/zenodo.10935937 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Song given-names: Shuang orcid: "https://orcid.org/0000-0002-8112-8780" - family-names: Wang given-names: Shuai orcid: "https://orcid.org/0000-0003-1595-9858" - family-names: Jiao given-names: Chentai orcid: "https://orcid.org/0000-0003-1737-9814" - family-names: Ibarra given-names: Elรญas Josรฉ Mantilla date-published: 2024-04-10 doi: 10.21105/joss.06298 issn: 2475-9066 issue: 96 journal: Journal of Open Source Software publisher: name: Open Journals start: 6298 title: "ABSESpy: An agent-based modeling framework for social-ecological systems" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06298" volume: 9 title: "ABSESpy: An agent-based modeling framework for social-ecological systems" ```
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.
๐๐๐ ๐ 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...
Congrats on your new publication @SongshGeo! Many thanks to editor @crvernon and reviewers @wang-boyu and @jamesdamillington 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.06298/status.svg)](https://doi.org/10.21105/joss.06298)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06298">
<img src="https://joss.theoj.org/papers/10.21105/joss.06298/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06298/status.svg
:target: https://doi.org/10.21105/joss.06298
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:
@SongshGeo if you're interested in reviewing for JOSS in the future, please sign up here: https://reviewers.joss.theoj.org/
@kthyng @crvernon @jamesdamillington @wang-boyu
Thanks for the efforts from you all. The comments helped us improve our package. Sure! I'm delighted to help with potential reviews in the future. I signed up just now.
By the way, does anyone know how to change JOSS's badge style? It seems not supported by Shields. I cannot add ?style=
to make it consistent with my other badges.
@SongshGeo I got an answer for you: We (JOSS) make them badges ourselves and they can't be re-styled. Sorry!
@kthyng OK! It's such a pity!
Submitting author: !--author-handle-->@SongshGeo<!--end-author-handle-- (Shuang Song) Repository: https://github.com/ABSESpy/ABSESpy Branch with paper.md (empty if default branch): dev Version: 0.5.6 Editor: !--editor-->@crvernon<!--end-editor-- Reviewers: @wang-boyu, @jamesdamillington Archive: 10.5281/zenodo.10935937
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
@wang-boyu & @jamesdamillington, 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 @crvernon 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 @wang-boyu
๐ Checklist for @jamesdamillington