[REVIEW]: localcovid19now: processing and mapping COVID-19 case data at subnational scales

[editorialbot]

Submitting author: !--author-handle-->@sjbeckett<!--end-author-handle-- (Stephen Beckett) Repository: https://github.com/sjbeckett/localcovid19now Branch with paper.md (empty if default branch): Version: v0.1 Editor: !--editor-->@galessiorob<!--end-editor-- Reviewers: @richelbilderbeek, @mbkumar, @welch16, @Epic19mz Archive: 10.5281/zenodo.7542478

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/a350d5e6dd0610b411aee8fdcc05472d"><img src="https://joss.theoj.org/papers/a350d5e6dd0610b411aee8fdcc05472d/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/a350d5e6dd0610b411aee8fdcc05472d/status.svg)](https://joss.theoj.org/papers/a350d5e6dd0610b411aee8fdcc05472d)

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

@richelbilderbeek, 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:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @galessiorob 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 @mbkumar

📝 Checklist for @welch16

📝 Checklist for @Epic19mz

📝 Checklist for @Epic19mz

📝 Checklist for @Epic19mz

📝 Checklist for @Epic19mz

📝 Checklist for @carinogurjao

[galessiorob]

@editorialbot remove @carinogurjao as reviewer

[editorialbot]

@carinogurjao removed from the reviewers list!

[galessiorob]

@editorialbot remove @epic19mz as reviewer

[editorialbot]

@epic19mz removed from the reviewers list!

[galessiorob]

@editorialbot generate pdf

[editorialbot]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[galessiorob]

I think we're ready for the final steps @sjbeckett!

@mbkumar could you please take a look at the final paper and the last updates to the code and check all remaining items on your list if you are satisfied?

@Epic19mz I checked off yours based on your comment ✅ . I also removed your duplicated handle (@epic19mz.)

@sjbeckett the next thing we need from you is to deposit your software in Zenodo and post the DOI here and the most recent version. After that, we can set the final version, generate a final proof, and have an Editor in Chief do the publishing. 🙏

[mbkumar]

@galessiorob I checked the updates and I am OK.

@sjbeckett Well done!

[sjbeckett]

Thanks @mbkumar!

Thank you @galessiorob! I have archived a version with Zenodo with doi: 10.5281/zenodo.7542478 The software version is 0.1.

[galessiorob]

@editorialbot set 10.5281/zenodo.7542478 as archive

[editorialbot]

Done! Archive is now 10.5281/zenodo.7542478

[galessiorob]

@editorialbot set v0.1 as version

[editorialbot]

Done! version is now v0.1

[galessiorob]

@editorialbot generate pdf

[editorialbot]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[galessiorob]

@editorialbot recommend-accept

[editorialbot]

Attempting dry run of processing paper acceptance...

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1038/s41562-020-0884-z is OK
- 10.1098/rsif.2010.0142 is OK
- 10.1016/S0140-6736(22)00484-6 is OK
- 10.1038/s41597-021-00955-2 is OK
- 10.1073/pnas.2009911117 is OK
- 10.1038/s41562-020-01000-9 is OK
- 10.21105/joss.03290 is OK
- 10.1073/pnas.2100970118 is OK
- 10.1038/s43587-021-00095-7 is OK
- 10.31234/osf.io/v8tdf is OK
- 10.1038/s41597-022-01245-1 is OK
- 10.1016/S1473-3099(20)30120-1 is OK
- 10.1590/SciELOPreprints.362 is OK
- 10.1503/cmaj.75262 is OK
- 10.1016/S2468-2667(20)30225-5 is OK
- 10.21105/joss.02376 is OK
- 10.18637/jss.v084.i06 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[galessiorob]

@sjbeckett an editor in chief will run the final steps to get it published. Thanks so much for working through the review, and congrats!

@mbkumar @richelbilderbeek @Epic19mz @welch16 thank you so, so much for lending your time and expertise to this paper 🎉

[editorialbot]

:wave: @openjournals/bcm-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/3881, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

[Kevin-Mattheus-Moerman]

@sjbeckett I am the AEiC for this track and here to help process the final steps towards acceptance in JOSS. The archive and paper look good. On the paper's affiliations, can you please spell out USA as United States of America for each? Thanks.

[sjbeckett]

@editorialbot generate pdf

[editorialbot]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[sjbeckett]

Many thanks @Kevin-Mattheus-Moerman, I have updated the affiliations in the paper.

[Kevin-Mattheus-Moerman]

@editorialbot accept

[editorialbot]

Doing it live! Attempting automated processing of paper acceptance...

[editorialbot]

:warning: Couldn't acccept/publish paper. An error happened.

[Kevin-Mattheus-Moerman]

@editorialbot accept

[editorialbot]

Doing it live! Attempting automated processing of paper acceptance...

[editorialbot]

🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦

[editorialbot]

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

[editorialbot]

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

0. Check final PDF and Crossref metadata that was deposited :point_right: https://github.com/openjournals/joss-papers/pull/3897
1. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.04898
2. If everything looks good, then close this review issue.
3. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

[Kevin-Mattheus-Moerman]

Congratulations on this JOSS publication @sjbeckett !

Thanks @galessiorob for editing this work, and a special thank you to the reviewers: @richelbilderbeek, @mbkumar, @welch16, and @Epic19mz!

[editorialbot]

: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.04898/status.svg)](https://doi.org/10.21105/joss.04898)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04898">
  <img src="https://joss.theoj.org/papers/10.21105/joss.04898/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04898/status.svg
   :target: https://doi.org/10.21105/joss.04898

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:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://joss.theoj.org/reviewer-signup.html
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss