Jurriaan H. Spaaks

Citation File Format 1.2.0 defines a `type` which can be `software` or `data`. It would be convenient if the conversion to Zenodo's metadata format would use this field to have...

The useful information is usally at the top. Current workaround is piping the `stderr` into `stdout`, then `head`ing that: ``` cffconvert --validate 2>&1 | head -n 10 ```

refs: https://github.com/nltk/nltk/pull/2944#issuecomment-1136556541

1. scripts in `.githooks/pre-commit` could be replaced by `.pre-commit-config.yaml` in the root of the project. 2. When we make this change the developer documentation in `README.dev.md` should be updated accordingly....

Thanks @sverhoeven for the suggestion

For example when a repo has default branch named `develop` or still has branch `master`, this is what should be used by default if the user doesn't list their branch...

add related identifiers to zenodo export

1

collect necessary data from: - `identifiers[i].type == 'url'` - `repository` - `repository-artifact` - `repository-code` - `url`

See also https://github.com/citation-file-format/cff-converter-python/tree/e68bc1d24835721021c7b7a396ecb8ca328f46e5/test/1.2.0/authors-creators Related: #238 - [ ] `GFANAO` - [ ] `GFANA_` - [ ] `GFAN_O` - [ ] `GFAN__` - [x] `GFA_AO` - [ ] `GFA_A_` - [...

Given the following `CITATION.cff` contents ```yaml authors: - name: Team cff-version: 1.2.0 title: Title type: dataset message: message ``` converting to schema.org with `cffconvert -f schema.org` yields: ```json { "@context":...