Open Czaki opened 11 months ago
When going through the documentation I found that link to zenodo points to release 0.1 not the current one 0.4.1.
Thanks for the bump, @Czaki!
As you do not have zenodod.json and do not provide bibtext entry are you thinking that add one of these things could be a good idea (as bibtex generated by zenodo has different content to example citation string in the documentation)?
zenodod.json is news to me. I had previously looked into CITATION.cff (https://github.com/ome/ngff/pull/175). Do you have a recommendation?
CITATION.cff
is for me something like just list of author, when .zenodo.json
allow to define much more detailed metadata.
Also in zenodo FAQ there is:
Do you support other software metadata files, like CITATION.cff or codemeta.json?
Part of our plans and ongoing work is to take into account or improve our integration of other software metadata schemas such as the Citation File Format (CFF) and CodeMeta. We are working closely with our users and scholarly software and citation communities to figure out exactly when, in what form, and how all these different metadata schemas and their files will be integrated into Zenodo.
Also other responses suggest that CITATION.cff
is not fully supported.
I'm not sure what is need for this project. So I'm not sure if ability to fill all zenodo metadata from code is required for project (like license, funding etc). To read about metadata that could be stored in .zenodo.json
see https://developers.zenodo.org/#github
When going through the documentation I found that link to zenodo points to release 0.1 not the current one 0.4.1.
As you do not have
zenodo.json
and do not provide bibtext entry are you thinking that add one of these things could be a good idea (as bibtex generated by zenodo has different content to example citation string in the documentation)?