Closed whedon closed 4 years ago
@ckoerber actually, it looks like one of your citations to an arXiv preprint (Berkowitz 2018) has since been published, can you update the info? https://doi.org/10.1109/sc.2018.00058
@kyleniemeyer Thank you for pointing this out. We have updated the citation.
@whedon generate pdf
@whedon accept
Attempting dry run of processing paper acceptance...
Reference check summary:
OK DOIs
- 10.1109/sc.2018.00054 is OK
- 10.1109/SC.2018.00060 is OK
- 10.1109/SC.2018.00058 is OK
- 10.1038/s41586-018-0161-8 is OK
- 10.1103/PhysRevLett.121.172501 is OK
- 10.1051/epjconf/201817509007 is OK
- 10.1103/PhysRevD.82.094502 is OK
- 10.1093/nar/gkt328 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Check final proof :point_right: https://github.com/openjournals/joss-papers/pull/1333
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/1333, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
Sorry... The new citation was referenced twice. I missed the second time.
@cchang5 did you correct this? nothing has been finalized yet
Hello @kyleniemeyer,
Yes the second reference is now updated as well. The updates to the references (only changes) are on the master branch which is now ahead of the previous v1.1.0
tag. Do we have to move or create a new tag for the submission (if so, do we have to updated the Zenodo doi as well)?
@ckoerber no, we aren't concerned with a minor update to the article—we archive that. I'll proceed with the existing Zenodo archive and version.
@whedon accept
Attempting dry run of processing paper acceptance...
Reference check summary:
OK DOIs
- 10.1109/sc.2018.00054 is OK
- 10.1109/SC.2018.00060 is OK
- 10.1109/SC.2018.00058 is OK
- 10.1038/s41586-018-0161-8 is OK
- 10.1103/PhysRevLett.121.172501 is OK
- 10.1051/epjconf/201817509007 is OK
- 10.1103/PhysRevD.82.094502 is OK
- 10.1093/nar/gkt328 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Check final proof :point_right: https://github.com/openjournals/joss-papers/pull/1334
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/1334, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
@whedon accept deposit=true
Doing it live! Attempting automated processing of paper acceptance...
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨
Here's what you must now do:
Party like you just published a paper! 🎉🌈🦄💃👻🤘
Any issues? notify your editorial technical team...
Congrats @ckoerber & @cchang5 on your article's publication in JOSS!
Many thanks to @remram44 and @ixjlyons for reviewing this, and @gkthiruvathukal for editing.
: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.02007/status.svg)](https://doi.org/10.21105/joss.02007)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.02007">
<img src="https://joss.theoj.org/papers/10.21105/joss.02007/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.02007/status.svg
:target: https://doi.org/10.21105/joss.02007
This is how it will look in your documentation:
We need your help!
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: @ckoerber (Christopher Körber) Repository: https://github.com/callat-qcd/espressodb Version: v1.1.0 Editor: @gkthiruvathukal Reviewer: @remram44, @ixjlyons Archive: 10.5281/zenodo.3677432
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
@remram44 & @ixjlyons, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @gkthiruvathukal know.
✨ Please try and complete your review in the next two weeks ✨
Review checklist for @remram44
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @ixjlyons
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper