-
Notifications
You must be signed in to change notification settings - Fork 3
Description
It is likely that your CITATION.cff currently doesn't pass validation. The error messages you get from the cffconvert GitHub Action are unfortunately a bit cryptic, but doing the following helps:
- Check if the
given-nameandfamily-namekeys need updating. If your family name has a name particle likevonorvanorde, use thename-particlekey; if your name has a suffix likeSrorIV, usename-suffix. For details, refer to the schema description: https://github.com/citation-file-format/citation-file-format - Update the value of the
orcidkey. If you do not have an orcid yet, you can get one here https://orcid.org/. - Add more authors if needed
- Update
date-releasedusing the YYYY-MM-DD format. - Update the
doikey with the conceptDOI for your repository (see https://help.zenodo.org for more information on what a conceptDOI is). If your project doesn't have a DOI yet, you can use the string10.0000/FIXMEto pass validation. - Verify that the
keywordsarray accurately describes your project.
Afterwards, the cffconvert GitHub Action should be green.
To make sure services like Zenodo and the Research Software Directory can keep your citation data up to date, the cffconvert GitHub Action checks the following:
-
Whether your repository includes a
CITATION.cfffile.By including this file, authors of the software can receive credit for the work they put in.
-
Whether your
CITATION.cffis valid YAML.Visit http://www.yamllint.com/ to see if the contents of your CITATION.cff are valid YAML.
-
Whether your
CITATION.cffadheres to the schema (as listed in theCITATION.cfffile itself under keycff-version).The Citation File Format schema can be found here, along with an explanation of all the keys. You're advised to use the latest available schema version.