Closed editorialbot closed 1 year ago
Thanks @ppxasjsm , I have incorporated your edits and have deposited v0.3.5 on Zenodo here: https://doi.org/10.5281/zenodo.7887039
@editorialbot set https://doi.org/10.5281/zenodo.7887039 as archive
Done! archive is now 10.5281/zenodo.7887039
@editorialbot generate pdf
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1146/annurev.biophys.37.092707.153558 is OK
- 10.1080/152165401317291147 is OK
- 10.1136/mp.53.1.8 is OK
- 10.1016/j.sbi.2019.05.024 is OK
- 10.1038/s41586-021-03819-2 is OK
- 10.1126/science.abj8754 is OK
- 10.1016/j.sbi.2007.01.009 is OK
- 10.1093/bioinformatics/bts172 is OK
- 10.1002/(sici)1097-0134(20000501)39:2<112::aid-prot2>3.0.co;2-b is OK
- 10.1002/prot.1163 is OK
- 10.1021/acs.jpcb.0c02924 is OK
- 10.1021/acs.jpca.2c03726 is OK
- 10.1016/j.str.2018.10.016 is OK
- 10.1093/nar/28.1.235 is OK
- 10.1021/acs.jpclett.6b00885 is OK
- 10.1073/pnas.1800690115 is OK
- 10.1093/bioinformatics/bts701 is OK
- 10.1021/jacs.6b00351 is OK
- 10.48550/ARXIV.2206.12667 is OK
- 10.1038/s42004-020-0323-0 is OK
- 10.1007/978-1-0716-0270-6_15 is OK
- 10.1039/c9sc06561j is OK
- 10.1021/ja003724j is OK
- 10.1107/s1600576717007786 is OK
- 10.1016/j.bpj.2018.01.002 is OK
- 10.1021/ja0000908 is OK
- 10.1021/jacs.1c06264 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot recommend-accept
Attempting dry run of processing paper acceptance...
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1146/annurev.biophys.37.092707.153558 is OK
- 10.1080/152165401317291147 is OK
- 10.1136/mp.53.1.8 is OK
- 10.1016/j.sbi.2019.05.024 is OK
- 10.1038/s41586-021-03819-2 is OK
- 10.1126/science.abj8754 is OK
- 10.1016/j.sbi.2007.01.009 is OK
- 10.1093/bioinformatics/bts172 is OK
- 10.1002/(sici)1097-0134(20000501)39:2<112::aid-prot2>3.0.co;2-b is OK
- 10.1002/prot.1163 is OK
- 10.1021/acs.jpcb.0c02924 is OK
- 10.1021/acs.jpca.2c03726 is OK
- 10.1016/j.str.2018.10.016 is OK
- 10.1093/nar/28.1.235 is OK
- 10.1021/acs.jpclett.6b00885 is OK
- 10.1073/pnas.1800690115 is OK
- 10.1093/bioinformatics/bts701 is OK
- 10.1021/jacs.6b00351 is OK
- 10.48550/ARXIV.2206.12667 is OK
- 10.1038/s42004-020-0323-0 is OK
- 10.1007/978-1-0716-0270-6_15 is OK
- 10.1039/c9sc06561j is OK
- 10.1021/ja003724j is OK
- 10.1107/s1600576717007786 is OK
- 10.1016/j.bpj.2018.01.002 is OK
- 10.1021/ja0000908 is OK
- 10.1021/jacs.1c06264 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/4192, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept
Excellent! Thanks Toni. I'm just wondering before the EiC proceeds if we need to update the version number to v0.3.5 and the list of reviewers?
You mean on the paper?
Good point about the version. In terms of reviewers...I am not sure actually.
@editorialbot set v0.3.5 as version
Done! version is now v0.3.5
Thanks! And yes on the paper for the list of reviewers, I thought it was just mirrored from the first bot comment in this issue? But it's no problem, I'm okay to wait for what the EiC says about that :)
@menoliu I've reviewed the paper, the archive, and the repository, and most seem in order. I only have the minor points below that require your attention:
Other (Open)
)cartesian
as Cartesian
throughout. USA
as United States of America
. Also zip codes are not a requirement so you may remove them if you wish. @ppxasjsm thanks for editing here. Minor side note, note sure if you've tried it yet but you can now call @editorialbot create post-review checklist
before you recommend acceptance, it can help double-check some of the final bits and pieces, for instance it will list the thing about the license listed on the archive too. Thanks again
Oh thank you! I didn't know about the checklist, I'll use it next time!
Thank you @Kevin-Mattheus-Moerman , I have completed all of the tasks
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Just a small update, I was reading over the paper and have corrected co-ordinate
to coordinate
to maintain consistency. There were some GitHub actions issues too but I have since resolved them. I am happy with everything now!
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@menoliu the paper change is fine. On the other changes, should we update the version tag here, e.g. to v0.3.9? And create a new ZENODO archive for it? Or should we proceed with the current ones?
@Kevin-Mattheus-Moerman great! I think we should proceed with the current one (v0.3.5) as ReadTheDocs has issues building v0.3.9 (even though I have not changed any code/requirements from v0.3.5 only made edits to paper.md
).
Edit: I should note that tox -e docs
is not giving any issues (as per all my ci tests passing) so I will look into this another time with RtD.
@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: Liu given-names: Zi Hao orcid: "https://orcid.org/0000-0002-8357-8507" - family-names: Zhang given-names: Oufan - family-names: Teixeira given-names: JoΓ£o M. C. orcid: "https://orcid.org/0000-0002-9113-0622" - family-names: Li given-names: Jie orcid: "https://orcid.org/0000-0002-4727-1786" - family-names: Head-Gordon given-names: Teresa orcid: "https://orcid.org/0000-0003-0025-8987" - family-names: Forman-Kay given-names: Julie D. orcid: "https://orcid.org/0000-0001-8265-972X" contact: - family-names: Liu given-names: Zi Hao orcid: "https://orcid.org/0000-0002-8357-8507" - family-names: Forman-Kay given-names: Julie D. orcid: "https://orcid.org/0000-0001-8265-972X" doi: 10.5281/zenodo.7887039 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Liu given-names: Zi Hao orcid: "https://orcid.org/0000-0002-8357-8507" - family-names: Zhang given-names: Oufan - family-names: Teixeira given-names: JoΓ£o M. C. orcid: "https://orcid.org/0000-0002-9113-0622" - family-names: Li given-names: Jie orcid: "https://orcid.org/0000-0002-4727-1786" - family-names: Head-Gordon given-names: Teresa orcid: "https://orcid.org/0000-0003-0025-8987" - family-names: Forman-Kay given-names: Julie D. orcid: "https://orcid.org/0000-0001-8265-972X" date-published: 2023-05-10 doi: 10.21105/joss.04861 issn: 2475-9066 issue: 85 journal: Journal of Open Source Software publisher: name: Open Journals start: 4861 title: "SPyCi-PDB: A modular command-line interface for back-calculating experimental datatypes of protein structures." type: article url: "https://joss.theoj.org/papers/10.21105/joss.04861" volume: 8 title: "SPyCi-PDB: A modular command-line interface for back-calculating experimental datatypes of protein structures." ```
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...
Many congratulations @menoliu!
Congratulations on this publication @menoliu !!
Thanks for editing @ppxasjsm, and a special thanks to the reviewers: @dotsdl, @lohedges, @JenkeScheen, @Sulstice !! :tada:
: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.04861/status.svg)](https://doi.org/10.21105/joss.04861)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.04861">
<img src="https://joss.theoj.org/papers/10.21105/joss.04861/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.04861/status.svg
:target: https://doi.org/10.21105/joss.04861
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-->@menoliu<!--end-author-handle-- (Zi Hao Liu) Repository: https://github.com/julie-forman-kay-lab/SPyCi-PDB Branch with paper.md (empty if default branch): Version: v0.3.5 Editor: !--editor-->@ppxasjsm<!--end-editor-- Reviewers: @dotsdl, @lohedges, @JenkeScheen, @sulstice Archive: 10.5281/zenodo.7887039
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
@dotsdl, 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 @ppxasjsm 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 @dotsdl
π Checklist for @lohedges
π Checklist for @JenkeScheen