Closed editorialbot closed 4 months ago
@emdupre Thanks for the update for the captions, that's been merged now! Also the affiliations now include additional address information.
@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 set 10.5281/zenodo.11490673 as archive
Done! archive is now 10.5281/zenodo.11490673
@editorialbot set v1.0.0 as version
Done! version is now v1.0.0
Thank you for those updates !
The remaining steps that I see :
@emdupre The capitalization in the references has now been fixed. I also went through and updated the Zenodo archive to match the author list and verified the ORCIDs are all matching now as well
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Thank you, @david-mathews-1994 ! The archive and software paper now look correct to me.
I'm now happy to recommend Delta-Rice to the EiC team for publication in JOSS β¨π
Thank you, too, to @macrocosme, @DanNixon, and @dineshchitlangia for your reviews ! JOSS works because of your work π
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.nima.2020.163961 is OK
- 10.1109/TIT.1966.1053907 is OK
- 10.1109/TCOM.1971.1090789 is OK
- 10.1016/j.ascom.2015.07.002 is OK
- 10.11578/dc.20180330.1 is OK
- 10.13023/etd.2022.446 is OK
- 10.1051/epjconf/201921904002 is OK
- 10.1109/99.660313 is OK
- 10.1088/1748-0221/14/11/P11017 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/csism-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/5527, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@david-mathews-1994 - As track editor, I'll now proofread this and let you know if anything else is needed from you
@david-mathews-1994 - the few needed changes I found are in https://github.com/david-mathews-1994/deltarice/pull/9
Please merge this, or let me know what you disagree with, and then we can finish the acceptance and publication of this work.
@danielskatz Those changes should be merged and taken care of now, thank you!
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/j.nima.2020.163961 is OK
- 10.1109/TIT.1966.1053907 is OK
- 10.1109/TCOM.1971.1090789 is OK
- 10.1016/j.ascom.2015.07.002 is OK
- 10.11578/dc.20180330.1 is OK
- 10.13023/etd.2022.446 is OK
- 10.1051/epjconf/201921904002 is OK
- 10.1109/99.660313 is OK
- 10.1088/1748-0221/14/11/P11017 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/csism-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/5528, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@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: Mathews given-names: D. G. orcid: "https://orcid.org/0000-0002-4897-4379" - family-names: Crawford given-names: C. B. orcid: "https://orcid.org/0000-0002-1932-4334" - family-names: BaeΓler given-names: S. orcid: "https://orcid.org/0000-0001-7732-9873" - family-names: Birge given-names: N. orcid: "https://orcid.org/0000-0003-1894-5494" - family-names: Broussard given-names: L. J. orcid: "https://orcid.org/0000-0001-9182-2808" - family-names: Gonzalez given-names: F. orcid: "https://orcid.org/0000-0002-5954-4155" - family-names: Hayen given-names: L. orcid: "https://orcid.org/0000-0002-9471-0964" - family-names: Jezghani given-names: A. orcid: "https://orcid.org/0000-0002-4302-4227" - family-names: Li given-names: H. orcid: "https://orcid.org/0000-0003-3726-9663" - family-names: Mammei given-names: R. orcid: "https://orcid.org/0009-0005-3481-4832" - family-names: Mendelsohn given-names: A. orcid: "https://orcid.org/0000-0002-4847-2133" - family-names: Randall given-names: G. orcid: "https://orcid.org/0000-0002-9713-8465" - family-names: Riley given-names: G. V. orcid: "https://orcid.org/0000-0001-7323-8448" - family-names: Schaper given-names: D. C. orcid: "https://orcid.org/0000-0002-6219-650X" contact: - family-names: Mathews given-names: D. G. orcid: "https://orcid.org/0000-0002-4897-4379" doi: 10.5281/zenodo.11490673 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Mathews given-names: D. G. orcid: "https://orcid.org/0000-0002-4897-4379" - family-names: Crawford given-names: C. B. orcid: "https://orcid.org/0000-0002-1932-4334" - family-names: BaeΓler given-names: S. orcid: "https://orcid.org/0000-0001-7732-9873" - family-names: Birge given-names: N. orcid: "https://orcid.org/0000-0003-1894-5494" - family-names: Broussard given-names: L. J. orcid: "https://orcid.org/0000-0001-9182-2808" - family-names: Gonzalez given-names: F. orcid: "https://orcid.org/0000-0002-5954-4155" - family-names: Hayen given-names: L. orcid: "https://orcid.org/0000-0002-9471-0964" - family-names: Jezghani given-names: A. orcid: "https://orcid.org/0000-0002-4302-4227" - family-names: Li given-names: H. orcid: "https://orcid.org/0000-0003-3726-9663" - family-names: Mammei given-names: R. orcid: "https://orcid.org/0009-0005-3481-4832" - family-names: Mendelsohn given-names: A. orcid: "https://orcid.org/0000-0002-4847-2133" - family-names: Randall given-names: G. orcid: "https://orcid.org/0000-0002-9713-8465" - family-names: Riley given-names: G. V. orcid: "https://orcid.org/0000-0001-7323-8448" - family-names: Schaper given-names: D. C. orcid: "https://orcid.org/0000-0002-6219-650X" date-published: 2024-06-21 doi: 10.21105/joss.06598 issn: 2475-9066 issue: 98 journal: Journal of Open Source Software publisher: name: Open Journals start: 6598 title: "Delta-Rice: A HDF5 Compression Plugin optimized for Digitized Detector Data" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06598" volume: 9 title: "Delta-Rice: A HDF5 Compression Plugin optimized for Digitized Detector Data" ```
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...
Congratulations to @david-mathews-1994 (David Mathews) and co-authors on your publication!!
And thanks to @macrocosme, @DanNixon, and @dineshchitlangia for reviewing, and to @emdupre for editing! JOSS depends on volunteers and we couldn't do this without you
: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.06598/status.svg)](https://doi.org/10.21105/joss.06598)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06598">
<img src="https://joss.theoj.org/papers/10.21105/joss.06598/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06598/status.svg
:target: https://doi.org/10.21105/joss.06598
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-->@david-mathews-1994<!--end-author-handle-- (David Mathews) Repository: https://github.com/david-mathews-1994/deltarice Branch with paper.md (empty if default branch): Version: v1.0.0 Editor: !--editor-->@emdupre<!--end-editor-- Reviewers: @macrocosme, @DanNixon, @dineshchitlangia Archive: 10.5281/zenodo.11490673
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
@macrocosme & @DanNixon & @dineshchitlangia, 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 @emdupre 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 @DanNixon
π Checklist for @dineshchitlangia
π Checklist for @macrocosme