New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
github: make it easier to validate/generate a ".zenodo.json" #1606
Comments
I want to wholeheartedly support this Enhancement proposal.
I followed the description on http://developers.zenodo.org/#representation so I had: "grants": [
{"id": "10.13039/501100000925"}
], NB well - that error helped me now to see that I took the DOI for the above entry (National Health and Medical Research Council) instead of NSF, will fix now After another reading, my current guess is that the correct format must have not just the DOI of the funder, but also some ID (grant ID I guess, but which one since there is at times a number of them) after "grants": [
{"id": "10.13039/100000001::1429999"}
], to refer to https://www.nsf.gov/awardsearch/showAward?AWD_ID=1429999 . But I would not know if that is correct until we kick out the next release. Having a validator, which could also verify correct composition of the grant entries, and possibly refer to the easy search for funders' DOIs (now there is only a text "OpenAIRE-supported grants", and still do not know where to look e.g. for BMBF's DOI), would be of great help! ref: datalad/datalad#3032 |
Could not even find a good readme file on how to create that file... |
Poor consolation, but FWIW there exists https://sandbox.zenodo.org to make trial-and-error easier with dummy repos |
Heyo! Is there still no automated way to generate this file for an existing archive? Using the API? |
FYI I have been working on a JSONschema for the metadata in |
A lot of people are having issues with creating a valid
.zenodo.json
, since the only way to test it at the moment, is via just trying things out. Ideally there should be a simple JSON validator on the GitHub settings page, which does some basic validation of the metadata (e.g. if thelicense
field is correct/resolvable).The text was updated successfully, but these errors were encountered: