-
Notifications
You must be signed in to change notification settings - Fork 494
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
As of 5.10, SWORD API no longer accepts NONE for dcterms:license #8551
Comments
pdurbin
added a commit
that referenced
this issue
Mar 30, 2022
pdurbin
added a commit
that referenced
this issue
Mar 31, 2022
pdurbin
added a commit
that referenced
this issue
Mar 31, 2022
pdurbin
added a commit
that referenced
this issue
Mar 31, 2022
pdurbin
added a commit
that referenced
this issue
Mar 31, 2022
pdurbin
added a commit
that referenced
this issue
Mar 31, 2022
pdurbin
added a commit
that referenced
this issue
Apr 5, 2022
pdurbin
added a commit
that referenced
this issue
Apr 5, 2022
kcondon
added a commit
that referenced
this issue
Apr 5, 2022
remove NONE as a license option for SWORD, show available licenses #8551
This was referenced Feb 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps does it take to reproduce the issue?
atom-entry-study.xml
from https://guides.dataverse.org/en/5.10/api/sword.html#create-a-dataset-with-an-atom-entryHere is the error:
What did you expect to happen?
I expect the dataset to be created.
To be honest, I'm not sure what I expect the dataset to have as a license when I specify
NONE
. We should probably check what happens in Dataverse 5.9.At the very least, the XML example in the API Guide should work.
It's possible that SWORD-based integrations like OJS and OSF are broken.
Which version of Dataverse are you using?
5.10
Any related open or closed issues to this bug report?
The text was updated successfully, but these errors were encountered: