-
Notifications
You must be signed in to change notification settings - Fork 241
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
CITATION.cff: array values for license
are no longer permitted (non-compliant with spec), vague error message
#2515
Comments
|
Update: I got a release to happen, but I don't know why. Here's what I removed to make it work:
I have no idea what part of that is the problem... EDIT: I re-tested an earlier failed release in case the issue was intermittent, and that release failed again. So it's definitely something in the above diff. For all these different versions, |
I determined the issue: I'm updating the OP with the new information! Thank you :) |
license
are no longer permitted (non-compliant with spec), vague error message
This should fix a bug discussed here: zenodo/zenodo#2515
Browser & OS (see also https://www.whatismybrowser.com/): Firefox:Pop!_OS
Describe the bug
My org has many repos which are set up with the integration so each release triggers a new DOI. Recently, all repos that were working started reporting
Citation metadata load failed
with no further detail, e.g.:Impacted repos include:
Citation metadata load failed
from Zenodo.I eventually determined that the problem is that in my org we always use array values for the
license
key. The Citation File Format specification permits array values, however, and Zenodo pre-InvenioRDM migration accepted these array values.Steps to Reproduce
license
key inCITATION.cff
(this doesn't require a change; any repository that was working >1 month ago using an array of strings broke when the InvenioRDM migration occurred)Workaround
Change the value of the
license
key to a string.If your project is multi-license, you may need to manually edit your Zenodo record to correctly indicate this
Expected behavior
Screenshots (if applicable)
Additional context
The text was updated successfully, but these errors were encountered: