[REVIEW]: dwctaxon, an R package for editing and validating taxonomic data in Darwin Core format

[editorialbot]

Submitting author: @joelnitta (Joel Nitta)
Repository: https://github.com/ropensci/dwctaxon
Branch with paper.md (empty if default branch): joss
Version: v2.0.3
Editor: @Kevin-Mattheus-Moerman
Reviewers: @Kevin-Mattheus-Moerman
Archive: 10.5281/zenodo.6388271

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/e7945e455a68ba0adedd2a6fd23450e0"><img src="https://joss.theoj.org/papers/e7945e455a68ba0adedd2a6fd23450e0/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/e7945e455a68ba0adedd2a6fd23450e0/status.svg)](https://joss.theoj.org/papers/e7945e455a68ba0adedd2a6fd23450e0)

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

@Kevin-Mattheus-Moerman, 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:

@editorialbot generate my checklist

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 ✨

Checklists

@Kevin-Mattheus-Moerman, please create your checklist typing: @editorialbot generate my checklist

[editorialbot]

Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1080/14888386.2003.9712683 is OK
- 10.1007/s10531-013-0472-x is OK
- 10.1371/journal.pone.0029715 is OK
- 10.3897/phytokeys.25.3100 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.88  T=0.05 s (1457.5 files/s, 219548.0 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
R                               47            343           1119           5910
Markdown                        10            293              0            977
JSON                             1              0              0            359
Rmd                              5            280            437            258
YAML                             4             12             11            173
TeX                              1              3              9             59
-------------------------------------------------------------------------------
SUM:                            68            931           1576           7736
-------------------------------------------------------------------------------


gitinspector failed to run statistical information for the repository

[editorialbot]

Wordcount for paper.md is 1946

[editorialbot]

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

[Kevin-Mattheus-Moerman]

This concerns the following rOpenSci submission: ropensci/software-review#574

[Kevin-Mattheus-Moerman]

@editorialbot set v2.0.3 as version

[editorialbot]

Done! version is now v2.0.3

[Kevin-Mattheus-Moerman]

@editorialbot set 10.5281/zenodo.6388271 as archive

[editorialbot]

Done! archive is now 10.5281/zenodo.6388271

[Kevin-Mattheus-Moerman]

@editorialbot recommend-accept

[editorialbot]

Attempting dry run of processing paper acceptance...

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1080/14888386.2003.9712683 is OK
- 10.1007/s10531-013-0472-x is OK
- 10.1371/journal.pone.0029715 is OK
- 10.3897/phytokeys.25.3100 is OK

MISSING DOIs

- None

INVALID DOIs

- None

[editorialbot]

👋 @openjournals/bcm-eics, this paper is ready to be accepted and published.

Check final proof 👉📄 Download article

If the paper PDF and the deposit XML files look good in openjournals/joss-papers#4901, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

[Kevin-Mattheus-Moerman]

@editorialbot accept

[editorialbot]

Doing it live! Attempting automated processing of paper acceptance...

[editorialbot]

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:

CITATION.cff

cff-version: "1.2.0"
authors:
- family-names: Nitta
  given-names: Joel H.
  orcid: "https://orcid.org/0000-0003-4719-7472"
- family-names: Iwasaki
  given-names: Wataru
  orcid: "https://orcid.org/0000-0002-9169-9245"
doi: 10.5281/zenodo.6388271
message: If you use this software, please cite our article in the
  Journal of Open Source Software.
preferred-citation:
  authors:
  - family-names: Nitta
    given-names: Joel H.
    orcid: "https://orcid.org/0000-0003-4719-7472"
  - family-names: Iwasaki
    given-names: Wataru
    orcid: "https://orcid.org/0000-0002-9169-9245"
  date-published: 2024-01-12
  doi: 10.21105/joss.06215
  issn: 2475-9066
  issue: 93
  journal: Journal of Open Source Software
  publisher:
    name: Open Journals
  start: 6215
  title: dwctaxon, an R package for editing and validating taxonomic
    data in Darwin Core format
  type: article
  url: "https://joss.theoj.org/papers/10.21105/joss.06215"
  volume: 9
title: dwctaxon, an R package for editing and validating taxonomic data
  in Darwin Core format

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.

Find more information on .cff files here and here.

[editorialbot]

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

[editorialbot]

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

0. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.06215 joss-papers#4902
1. Wait five minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.06215
2. If everything looks good, then close this review issue.
3. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

[Kevin-Mattheus-Moerman]

@joelnitta congratulations on this JOSS publication!

[editorialbot]

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

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.06215/status.svg)](https://doi.org/10.21105/joss.06215)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.06215">
  <img src="https://joss.theoj.org/papers/10.21105/joss.06215/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.06215/status.svg
   :target: https://doi.org/10.21105/joss.06215

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:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://reviewers.joss.theoj.org/join
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss