Closed editorialbot closed 1 year ago
Done! Archive is now https://doi.org/10.5281/zenodo.7716943
@editorialbot set v1.3.4 as version
Done! version is now v1.3.4
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
:warning: Error preparing paper acceptance. The generated XML metadata file is invalid.
IDREFS attribute rid references an unknown ID "Examples"
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/S0021-9290(03)00257-4 is OK
- 10.1016/S8756-3282(02)00736-6 is OK
- 10.1016/j.jbiomech.2020.110205 is OK
- 10.1115/1.2746368 is OK
- 10.1016/j.jbiomech.2008.02.032 is OK
- 10.1115/1.2146001 is OK
- 10.1007/s10237-019-01254-x is OK
- 10.1371/journal.pone.0180151 is OK
- 10.1002/cnm.2941 is OK
- 10.1007/978-3-642-29843-1_56 is OK
- 10.1016/j.parco.2011.08.001 is OK
- 10.1016/j.jmbbm.2020.104190 is OK
- 10.1016/j.jmbbm.2018.06.022 is OK
- 10.1016/j.medntd.2021.100088 is OK
- 10.1115/1.4028968 is OK
- 10.1007/s10237-007-0109-7 is OK
- 10.1016/j.bonr.2022.101179 is OK
- 10.1016/j.jmbbm.2022.105303 is OK
- 10.1101/2021.11.30.470675 is OK
- 10.1016/j.cmpb.2022.106764 is OK
- 10.1016/j.jbiomech.2003.10.002 is OK
- 10.1109/tsmc.1979.4310076 is OK
- 10.1109/tsmc.1978.4310039 is OK
- 10.1007/s10237-008-0125-2 is OK
- 10.5281/zenodo.1173115 is OK
- 10.5281/zenodo.5564818 is OK
- 10.1107/S160057751401604X is OK
- 10.1002/adem.201900080 is OK
- 10.1016/j.jmbbm.2016.11.020 is OK
- 10.1080/10255840701848756 is OK
- 10.1080/10255840410001656408 is OK
- 10.1038/s41592-019-0686-2 is OK
- 10.7717/peerj.453 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@danasolav @gianthk β it looks like the paper is referencing a figure that doesn't exist which is causing the JATS validation to fail (https://github.com/openjournals/joss-reviews/issues/4952#issuecomment-1465576720). Can you please see if you can resolve this?
@arfon @danasolav the issue was not a missing figure, but a wrong internal ref to the Examples section. It should be fixed now, pointing to the readthedocs Examples page.
@arfon @danasolav can you please check again if the paper can build? the previous issue should be solved
@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/S0021-9290(03)00257-4 is OK
- 10.1016/S8756-3282(02)00736-6 is OK
- 10.1016/j.jbiomech.2020.110205 is OK
- 10.1115/1.2746368 is OK
- 10.1016/j.jbiomech.2008.02.032 is OK
- 10.1115/1.2146001 is OK
- 10.1007/s10237-019-01254-x is OK
- 10.1371/journal.pone.0180151 is OK
- 10.1002/cnm.2941 is OK
- 10.1007/978-3-642-29843-1_56 is OK
- 10.1016/j.parco.2011.08.001 is OK
- 10.1016/j.jmbbm.2020.104190 is OK
- 10.1016/j.jmbbm.2018.06.022 is OK
- 10.1016/j.medntd.2021.100088 is OK
- 10.1115/1.4028968 is OK
- 10.1007/s10237-007-0109-7 is OK
- 10.1016/j.bonr.2022.101179 is OK
- 10.1016/j.jmbbm.2022.105303 is OK
- 10.1101/2021.11.30.470675 is OK
- 10.1016/j.cmpb.2022.106764 is OK
- 10.1016/j.jbiomech.2003.10.002 is OK
- 10.1109/tsmc.1979.4310076 is OK
- 10.1109/tsmc.1978.4310039 is OK
- 10.1007/s10237-008-0125-2 is OK
- 10.5281/zenodo.1173115 is OK
- 10.5281/zenodo.5564818 is OK
- 10.1107/S160057751401604X is OK
- 10.1002/adem.201900080 is OK
- 10.1016/j.jmbbm.2016.11.020 is OK
- 10.1080/10255840701848756 is OK
- 10.1080/10255840410001656408 is OK
- 10.1038/s41592-019-0686-2 is OK
- 10.7717/peerj.453 is OK
MISSING DOIs
- None
INVALID DOIs
- None
: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/4064, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
@editorialbot set 10.5281/zenodo.7716943 as archive
Done! Archive is now 10.5281/zenodo.7716943
@gianthk I am the AEiC for this track and here to help process the final steps. Below are some minor points which require your attention:
On the paper:
On the archive:
Giulia Fraterrigo
appears missing from the archived versionJournal of Open Source Software (JOSS):.
but should perhaps say Journal of Open Source Software (JOSS)
. i.e. remove :.
. @gianthk π
@Kevin-Mattheus-Moerman thank you for doing a last check. I have done the following modifications:
On the paper:
- [X] Please add the town/city for affiliation 1
- [X] Please write United Kingdom, instead of UK for affiliation 3. On the archive:
- [X] Please manually edit the archive listed license to match your open source license. It currently says "Creative Commons Attribution 4.0 International", but it should refer to the MIT license you use.
- [x] You may also edit the archive title to have the same use of capitals as the paper title e.g. : "Ciclope: micro Computed Tomography to Finite Elements" I can't find the difference between paper and archive title..
Giulia Fraterrigo
appears missing from the archived versionJournal of Open Source Software (JOSS):.
but should perhaps say Journal of Open Source Software (JOSS)
. i.e. remove :.
.
:.
is there because journal volume and issue fields are empty. Once published, and if available, I can update the fields on the archive
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@gianthk thanks for working on those points. All looks good now.
@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: Iori given-names: Gianluca orcid: "https://orcid.org/0000-0001-8611-3281" - family-names: Crimi given-names: Gianluigi - family-names: Schileo given-names: Enrico orcid: "https://orcid.org/0000-0003-3515-1231" - family-names: Taddei given-names: Fulvia orcid: "https://orcid.org/0000-0002-8342-7434" - family-names: Fraterrigo given-names: Giulia - family-names: Pani given-names: Martino orcid: "https://orcid.org/0000-0002-5786-4462" contact: - family-names: Iori given-names: Gianluca orcid: "https://orcid.org/0000-0001-8611-3281" doi: 10.5281/zenodo.7716943 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Iori given-names: Gianluca orcid: "https://orcid.org/0000-0001-8611-3281" - family-names: Crimi given-names: Gianluigi - family-names: Schileo given-names: Enrico orcid: "https://orcid.org/0000-0003-3515-1231" - family-names: Taddei given-names: Fulvia orcid: "https://orcid.org/0000-0002-8342-7434" - family-names: Fraterrigo given-names: Giulia - family-names: Pani given-names: Martino orcid: "https://orcid.org/0000-0002-5786-4462" date-published: 2023-04-02 doi: 10.21105/joss.04952 issn: 2475-9066 issue: 84 journal: Journal of Open Source Software publisher: name: Open Journals start: 4952 title: "Ciclope: micro Computed Tomography to Finite Elements" type: article url: "https://joss.theoj.org/papers/10.21105/joss.04952" volume: 8 title: "Ciclope: micro Computed Tomography to Finite Elements" ```
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.
π¦π¦π¦ π Tweet for this paper π π¦π¦π¦
πππ π 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...
@gianthk congratulations on your published paper!
@danasolav thanks for editing this one!
And a special thans to the reviewers @dankusanovic and @jacobmerson !!!
: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.04952/status.svg)](https://doi.org/10.21105/joss.04952)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04952">
<img src="https://joss.theoj.org/papers/10.21105/joss.04952/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04952/status.svg
:target: https://doi.org/10.21105/joss.04952
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:
@danasolav @Kevin-Mattheus-Moerman @dankusanovic @jacobmerson thank you for the very nice review experience! We are really happy to see this work published.
Congratulations @gianthk and many thanks to @jacobmerson and @dankusanovic for reviewing and @Kevin-Mattheus-Moerman for the final edit!
Submitting author: !--author-handle-->@gianthk<!--end-author-handle-- (gianluca iori) Repository: https://github.com/gianthk/ciclope Branch with paper.md (empty if default branch): Version: v1.3.4 Editor: !--editor-->@danasolav<!--end-editor-- Reviewers: @dankusanovic, @jacobmerson Archive: 10.5281/zenodo.7716943
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
@dankusanovic & @jacobmerson, 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 @danasolav 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 @jacobmerson
π Checklist for @dankusanovic