Closed whedon closed 2 years ago
@editorialbot check references
@editorialbot check references
@openjournals/dev Looks like she's dead Jim :point_up:
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-1-4614-7657-3_19 is OK
- 10.1007/s11517-008-0420-1 is OK
- 10.1109/ipta50016.2020.9286658 is OK
- 10.3390/app11114895 is OK
- 10.1109/icpr48806.2021.9412362 is OK
- 10.1016/j.diii.2019.05.008 is OK
- 10.1038/s41467-021-26216-9 is OK
- 10.1016/j.crad.2013.12.021 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@antoinevacavant we can now proceed to process this work for acceptance in JOSS. Before we proceed, can you please:
Thanks.
Hi @Kevin-Mattheus-Moerman the link with ZENODO is done, the DOI is: 10.5281/zenodo.6513517
@editorialbot set 10.5281/zenodo.6513517 as archive
Done! Archive is now 10.5281/zenodo.6513517
@antoinevacavant thanks for creating that archived version. Now can you please edit the title and author list so they match the paper?
@editorialbot set 1.0.2 as version
Done! version is now 1.0.2
@antoinevacavant I've incremented the version tag to match that of the ZENODO archived version. Can you confirm this is correct?
Yes, this is the correct version (1.0.2)
Great @antoinevacavant, and did you see this question too? :point_down:
@antoinevacavant thanks for creating that archived version. Now can you please edit the title and author list so they match the paper?
Hi @Kevin-Mattheus-Moerman, well I missed this point, but now the title and authors have been changed according to the paper!
@antoinevacavant it seems that the title for https://zenodo.org/record/6513517 still has not been amended. Can you do this and let me know when it is done? Thanks. FYI if you wanted to add ORCID details for the authors (not a requirement but an option for you) you should be able to do that for the ZENODO archive too.
@Kevin-Mattheus-Moerman everything's fine now! ;)
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-1-4614-7657-3_19 is OK
- 10.1007/s11517-008-0420-1 is OK
- 10.1109/ipta50016.2020.9286658 is OK
- 10.3390/app11114895 is OK
- 10.1109/icpr48806.2021.9412362 is OK
- 10.1016/j.diii.2019.05.008 is OK
- 10.1038/s41467-021-26216-9 is OK
- 10.1016/j.crad.2013.12.021 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:wave: @openjournals/joss-eics, this paper is ready to be accepted and published.
Check final proof :point_right: https://github.com/openjournals/joss-papers/pull/3200
If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/3200, 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...
🐦🐦🐦 👉 Tweet 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...
@antoinevacavant congratulations on getting this work published in JOSS! :tada:
A special thanks to @lassoan and @deepakri201 for their great review efforts! :bow:
: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.03920/status.svg)](https://doi.org/10.21105/joss.03920)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03920">
<img src="https://joss.theoj.org/papers/10.21105/joss.03920/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03920/status.svg
:target: https://doi.org/10.21105/joss.03920
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-->@antoinevacavant<!--end-author-handle-- (Antoine Vacavant) Repository: https://github.com/R-Vessel-X/SlicerRVXLiverSegmentation Branch with paper.md (empty if default branch): Version: 1.0.2 Editor: !--editor-->@Kevin-Mattheus-Moerman<!--end-editor-- Reviewers: @lassoan, @deepakri201 Archive: 10.5281/zenodo.6513517
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
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
@lassoan & @deepakri201, 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 @Kevin-Mattheus-Moerman 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 ✨
Review checklist for @deepakri201
✨ Important: Please do not use the Convert to issue functionality when working through this checklist, instead, please open any new issues associated with your review in the software repository associated with the submission. ✨
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper