Closed editorialbot closed 9 months ago
@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: Otis given-names: Jessica M. orcid: "https://orcid.org/0000-0001-5519-8331" - family-names: Safley given-names: James - family-names: Brett given-names: Megan orcid: "https://orcid.org/0000-0002-7474-7196" - family-names: Mullen given-names: Lincoln orcid: "https://orcid.org/0000-0001-5103-6917" doi: 10.5281/zenodo.10379756 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Otis given-names: Jessica M. orcid: "https://orcid.org/0000-0001-5519-8331" - family-names: Safley given-names: James - family-names: Brett given-names: Megan orcid: "https://orcid.org/0000-0002-7474-7196" - family-names: Mullen given-names: Lincoln orcid: "https://orcid.org/0000-0001-5103-6917" date-published: 2024-01-07 doi: 10.21105/joss.05661 issn: 2475-9066 issue: 93 journal: Journal of Open Source Software publisher: name: Open Journals start: 5661 title: "DataScribe: An Omeka S module for structured data transcription" type: article url: "https://joss.theoj.org/papers/10.21105/joss.05661" volume: 9 title: "DataScribe: An Omeka S module for structured data transcription" ```
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.
🐘🐘🐘 👉 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...
@luxaritas, @koenedaele – many thanks for your reviews here! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨
@jmotis – your paper is now accepted and published in JOSS :zap::rocket::boom:
: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.05661/status.svg)](https://doi.org/10.21105/joss.05661)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05661">
<img src="https://joss.theoj.org/papers/10.21105/joss.05661/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05661/status.svg
:target: https://doi.org/10.21105/joss.05661
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-->@jmotis<!--end-author-handle-- (Jessica Otis) Repository: https://github.com/chnm/Datascribe-module Branch with paper.md (empty if default branch): JOSS Version: v1.1.0 Editor: !--editor-->@arfon<!--end-editor-- Reviewers: @luxaritas, @koenedaele Archive: 10.5281/zenodo.10379756
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
@luxaritas & @koenedaele, 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 @arfon 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 @luxaritas
📝 Checklist for @koenedaele