Closed editorialbot closed 1 year ago
@editorialbot set 10.5281/zenodo.8319843 as archive
Done! archive is now 10.5281/zenodo.8319843
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1038/s41586-020-2649-2 is OK
- 10.5281/zenodo.3509134 is OK
- 10.5281/zenodo.5884351 is OK
- 10.18141/1503876 is OK
- 10.18141/1614852 is OK
- 10.1190/INT-2019-0019.1 is OK
- 10.1016/j.coal.2011.11.001 is OK
- 10.1016/j.gsf.2018.12.005 is OK
- 10.1007/s11053-023-10163-x is OK
- 10.18141/1891489 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Nothing else you have to do @justaPCWingo - thanks!
: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/4538, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Ok next steps on my end:
Looks great!
@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: Wingo given-names: Patrick orcid: "https://orcid.org/0000-0003-3934-7733" - family-names: Justman given-names: Devin - family-names: Creason given-names: C. Gabriel orcid: "https://orcid.org/0000-0002-3440-1174" - family-names: Mark-Moser given-names: Mackenzie orcid: "https://orcid.org/0000-0001-5138-5527" - family-names: Montross given-names: Scott orcid: "https://orcid.org/0000-0002-6551-7700" - family-names: Rose given-names: Kelly orcid: "https://orcid.org/0000-0001-6130-4727" contact: - family-names: Wingo given-names: Patrick orcid: "https://orcid.org/0000-0003-3934-7733" doi: 10.5281/zenodo.8319843 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Wingo given-names: Patrick orcid: "https://orcid.org/0000-0003-3934-7733" - family-names: Justman given-names: Devin - family-names: Creason given-names: C. Gabriel orcid: "https://orcid.org/0000-0002-3440-1174" - family-names: Mark-Moser given-names: Mackenzie orcid: "https://orcid.org/0000-0001-5138-5527" - family-names: Montross given-names: Scott orcid: "https://orcid.org/0000-0002-6551-7700" - family-names: Rose given-names: Kelly orcid: "https://orcid.org/0000-0001-6130-4727" date-published: 2023-09-08 doi: 10.21105/joss.05500 issn: 2475-9066 issue: 89 journal: Journal of Open Source Software publisher: name: Open Journals start: 5500 title: A Python Tool for Predicting and Assessing Unconventional Rare-Earth and Critical Mineral Resources type: article url: "https://joss.theoj.org/papers/10.21105/joss.05500" volume: 8 title: A Python Tool for Predicting and Assessing Unconventional Rare-Earth and Critical Mineral Resources ```
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 @justaPCWingo!! Many thanks to editor @elbeejay and reviewers @jeinsle, @jameshgrn, and @FrancescoPerrone for your time, hard work, and expertise!!
(I will close this issue once the DOI resolves)
: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.05500/status.svg)](https://doi.org/10.21105/joss.05500)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05500">
<img src="https://joss.theoj.org/papers/10.21105/joss.05500/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05500/status.svg
:target: https://doi.org/10.21105/joss.05500
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-->@justaPCWingo<!--end-author-handle-- (Patrick Wingo) Repository: https://github.com/NETL-RIC/URC-Assessment-Method Branch with paper.md (empty if default branch): joss-submit Version: v1.0.1 Editor: !--editor-->@elbeejay<!--end-editor-- Reviewers: @jeinsle, @jameshgrn, @FrancescoPerrone Archive: 10.5281/zenodo.8319843
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
@jeinsle & @jameshgrn, 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 @elbeejay 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 @jeinsle
📝 Checklist for @FrancescoPerrone
📝 Checklist for @jameshgrn