-
Notifications
You must be signed in to change notification settings - Fork 85
Expand file tree
/
Copy path{% if AddCitation %}next_steps_citation_issue.md{% endif %}.jinja
More file actions
30 lines (20 loc) · 2.23 KB
/
{% if AddCitation %}next_steps_citation_issue.md{% endif %}.jinja
File metadata and controls
30 lines (20 loc) · 2.23 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
---
title: 'Next step: Citation data'
---
It is likely that your `CITATION.cff` currently doesn't pass validation. The error messages you get from the [`cffconvert`]({{repository_url}}/actions/workflows/cffconvert.yml) GitHub Action are unfortunately a bit cryptic, but doing the following helps:
- [ ] Check if the `given-name` and `family-name` keys need updating. If your family name has a name particle like `von` or `van` or `de`, use the `name-particle` key; if your name has a suffix like `Sr` or `IV`, use `name-suffix`. For details, refer to the schema description: https://github.com/citation-file-format/citation-file-format
- [ ] Update the value of the `orcid` key. If you do not have an orcid yet, you can get one here [https://orcid.org/](https://orcid.org/).
- [ ] Add more authors if needed
- [ ] Update `date-released` using the YYYY-MM-DD format.
{% if AddZenodo -%}
- [ ] Update the `doi` key with the conceptDOI for your repository (see [https://help.zenodo.org](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 string `10.0000/FIXME` to pass validation.
{%- endif -%}
- [ ] Verify that the `keywords` array accurately describes your project.
Afterwards, the `cffconvert` GitHub Action should be green.
To make sure services like {% if AddZenodo -%} [Zenodo](https://zenodo.org) and {%- endif -%} the [Research Software Directory](https://research-software-directory.org/) can keep your citation data up to date, the [`cffconvert`]({{repository_url}}/actions/workflows/cffconvert.yml) GitHub Action checks the following:
1. Whether your repository includes a `CITATION.cff` file.
_By including this file, authors of the software can receive credit for the work they put in._
1. Whether your `CITATION.cff` is valid YAML.
_Visit http://www.yamllint.com/ to see if the contents of your CITATION.cff are valid YAML._
1. Whether your `CITATION.cff` adheres to the schema (as listed in the `CITATION.cff` file itself under key `cff-version`).
_The Citation File Format schema can be found [here](https://github.com/citation-file-format/citation-file-format), along with an explanation of all the keys. You're advised to use the latest available schema version._