cffconvert
cffconvert copied to clipboard
Command line program to validate and convert CITATION.cff files.
I'm in the process of using cffconvert to analyze validation errors in a dataset of CFF files. `jsonschema` > 4 introduces a property `jsonschema.exceptions.ValidationError`.`json_path` that the currently bundled dependency (3.2.0)...
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...
I tested with `jsonschema` 4.6.0 and found that all the tests in `test/` and `livetest/` still pass.
When converting `CITATION.cff` containing ``` license: MIT ``` to `.zenodo.json`, the resulting file contains ```json "license": { "id": "MIT" } ``` According to [Zenodo documentation about the file](https://developers.zenodo.org/?python#add-metadata-to-your-github-repository-release): * [The...
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 ```
Roberto di Cosmo has suggested to me that we could support the [biblatex-software](https://www.ctan.org/tex-archive/macros/latex/contrib/biblatex-contrib/biblatex-software) style extension ([docs](https://ctan.space-pro.be/tex-archive/macros/latex/contrib/biblatex-contrib/biblatex-software/software-biblatex.pdf)) as a target style for BibTeX. I think this is a great idea, because...
Howdy @jspaaks 👋, I'm currently working on a [project](https://software-metadata.pub) aiming to automate compiling software metadata from different sources in a source code repo, including `CITATION.cff`. The internal data model is...
refs: https://github.com/nltk/nltk/pull/2944#issuecomment-1136556541
The converted codemeta includes an affiliation key `legalName` which is not valid in the codemeta schema if trying to validate using their [online validator](https://codemeta.github.io/codemeta-generator/): `Unknown field "legalName" in "affiliation"` I...
Currently `cffconvert --validate` leads to a traceback: ``` Exception: "1.2.0" is not a supported release. Instead, use one of "1.0.1", "1.0.2", "1.0.3", "1.1.0". ``` In addition I think cffconvert should...