Closed editorialbot closed 1 week ago
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Thank you, @rwood-97 ! I've updated the archive and confirmed that it the paper rendering looks correct.
I'm now happy to recommend MapReader to the JOSS EiC team for publication.
Thank you again to @geekysquirrel, @PipGrylls, and @jordibc for all of your work throughout this review process ! 💐
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
✅ OK DOIs
- 10.1145/3557919.3565812 is OK
- 10.5281/ZENODO.7147906 is OK
- 10.1093/jvcult/vcab009 is OK
- 10.1016/j.regsciurbeco.2021.103711 is OK
- 10.1145/3394486.3403381 is OK
- 10.48550/ARXIV.2101.12478 is OK
- 10.21105/joss.01800 is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: Dynamic phenotyping of whole oilseed rape (Brassic...
❌ 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/5793, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Hi @emdupre
Would it be possible to hold off publishing for ~1 week as we've decided to do the repo transfer and would ideally like to do this before publication of the JOSS paper incase we need to update any links. I do this asap will update you when its done.
👋 Hi @rwood-97, EiC @kthyng has OK'ed a wait so this should be fine on our end.
I'll go ahead and set a reminder here to check back with you in one week in case we haven't heard anything by then !
@editorialbot remind @rwood-97 in one week
@rwood-97 doesn't seem to be a reviewer or author for this submission.
@editorialbot remind @kmcdono2 in one week
Reminder set for @kmcdono2 in one week
Hi, we've just transferred the repo to https://github.com/maps-as-data/MapReader! I think we need to update one link in the paper (the contributors right at the end) and then should be good to go. Both myself and @kmcdono2 are off the rest of this week so will do this first thing next week :)
:wave: @kmcdono2, please update us on how things are progressing here (this is an automated reminder).
Hi, could you update the DOI for the zenodo record to: 10.5281/zenodo.13643609.
We are happy for this to proceed now on our end, sorry for all the last minute changes!
@editorialbot set 10.5281/zenodo.13643609 as archive
Done! archive is now 10.5281/zenodo.13643609
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
👋 @kthyng This is now ready !
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
✅ OK DOIs
- 10.1145/3557919.3565812 is OK
- 10.5281/ZENODO.7147906 is OK
- 10.1093/jvcult/vcab009 is OK
- 10.1016/j.regsciurbeco.2021.103711 is OK
- 10.1145/3394486.3403381 is OK
- 10.48550/ARXIV.2101.12478 is OK
- 10.21105/joss.01800 is OK
🟡 SKIP DOIs
- No DOI given, and none found for title: Dynamic phenotyping of whole oilseed rape (Brassic...
❌ 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/5855, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Sorry, I found a few typos in my final read! Fixing these now.
Fixes done!
@emdupre do you need to check again? (Sorry!)
Ok I changed the repo link at the top of this review issue to https://github.com/maps-as-data/MapReader.
@openjournals/dev this submission is just about to be published and the authors changed the organization of the repo. Is there anywhere else the link needs to be updated?
Hi! I'll take over now as Track Associate Editor in Chief to do some final submission editing checks. After these checks are complete, I will publish your submission!
@kmcdono2 I'm seeing multiple versions associated with this JOSS paper:
Which is it meant to be?
Also in the JOSS-associated Zenodo version archive we request that the title and author list match the JOSS paper (not sure if you already discussed this above because the page is really long). Can you update the Zenodo metadata so these match? (it's a request not a requirement)
Hi @kthyng ,
We'd like to link to v1.3.10 which is the version after we moved to maps-as-data org.
I'll update the order of authors on this zenodo record now Apparently I'd already done this
@editorialbot set v1.3.10 as version
Done! version is now v1.3.10
@rwood-97 Ok great about the author order in Zenodo — how about the title? Did you want to update that for this version to match your JOSS paper or leave it as is?
Hi, just done this. Title for the zenodo record is now "MapReader: Open software for the visual analysis of maps" too
All good here now?
@kmcdono2 @rwood-97 That finalizes my checks but I am not sure if there is anything else to be done to make sure your new github address has been updated everywhere. I am pinging the dev team elsewhere to follow up.
@kthyng I've updated the repository URL for this submission in the JOSS site, nothing else needs updating before acceptance.
@xuanxu Thank you!
Sorry for my delay — I've been traveling. Everything is ready to go!
@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: Wood given-names: Rosie orcid: "https://orcid.org/0000-0003-1623-1949" - family-names: Hosseini given-names: Kasra orcid: "https://orcid.org/0000-0003-4396-6019" - family-names: Westerling given-names: Kalle orcid: "https://orcid.org/0000-0002-2014-332X" - family-names: Smith given-names: Andrew orcid: "https://orcid.org/0000-0002-4465-2284" - family-names: Beelen given-names: Kaspar orcid: "https://orcid.org/0000-0001-7331-1174" - family-names: Wilson given-names: Daniel C. S. orcid: "https://orcid.org/0000-0001-6886-775X" - family-names: McDonough given-names: Katherine orcid: "https://orcid.org/0000-0001-7506-1025" contact: - family-names: McDonough given-names: Katherine orcid: "https://orcid.org/0000-0001-7506-1025" doi: 10.5281/zenodo.13643609 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Wood given-names: Rosie orcid: "https://orcid.org/0000-0003-1623-1949" - family-names: Hosseini given-names: Kasra orcid: "https://orcid.org/0000-0003-4396-6019" - family-names: Westerling given-names: Kalle orcid: "https://orcid.org/0000-0002-2014-332X" - family-names: Smith given-names: Andrew orcid: "https://orcid.org/0000-0002-4465-2284" - family-names: Beelen given-names: Kaspar orcid: "https://orcid.org/0000-0001-7331-1174" - family-names: Wilson given-names: Daniel C. S. orcid: "https://orcid.org/0000-0001-6886-775X" - family-names: McDonough given-names: Katherine orcid: "https://orcid.org/0000-0001-7506-1025" date-published: 2024-09-26 doi: 10.21105/joss.06434 issn: 2475-9066 issue: 101 journal: Journal of Open Source Software publisher: name: Open Journals start: 6434 title: "MapReader: Open software for the visual analysis of maps" type: article url: "https://joss.theoj.org/papers/10.21105/joss.06434" volume: 9 title: "MapReader: Open software for the visual analysis of maps" ```
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 on your new publication @kmcdono2! Many thanks to editor @emdupre and to reviewers @geekysquirrel, @PipGrylls, and @jordibc for your time, hard work, and expertise!! JOSS wouldn't be able to function nor succeed without your efforts.
@kmcdono2 I see you are in our reviewer database (thank you!) though you don't have any keywords associated with yourself, so you will never come up in a search when we're trying to find reviewers. It would be great if you'd be willing to update that. Just a heads up! https://reviewers.joss.theoj.org/
: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.06434/status.svg)](https://doi.org/10.21105/joss.06434)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06434">
<img src="https://joss.theoj.org/papers/10.21105/joss.06434/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06434/status.svg
:target: https://doi.org/10.21105/joss.06434
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-->@kmcdono2<!--end-author-handle-- (Katherine McDonough) Repository: https://github.com/maps-as-data/MapReader Branch with paper.md (empty if default branch): Version: v1.3.10 Editor: !--editor-->@emdupre<!--end-editor-- Reviewers: @geekysquirrel, @PipGrylls, @jordibc Archive: 10.5281/zenodo.13643609
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
@geekysquirrel & @PipGrylls & @jordibc, 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 @PipGrylls
📝 Checklist for @jordibc
📝 Checklist for @geekysquirrel