-
Notifications
You must be signed in to change notification settings - Fork 488
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
Allow terms metadata to be changed with Native API #5899
Comments
|
Yesterday at standup I said I'd push what I have (which isn't much) to a branch so here it is: pdurbin@60ff805 One thing I re-discovered along that way is that we already have an API to enable or disable the "Request Access" button: http://guides.dataverse.org/en/4.19/api/dataaccess.html#allow-access-requests Here's a dump of the doc I stubbed out, which gives an idea of where my head's at:
|
Interesting!
Just posting for consideration that the SWORD API guide describes similar logic, in the section with the crosswalk, where if the given xml file has dcterms:license set to "CC0," the CC0 waiver is retained. Otherwise, "enter “NONE” and fill in the dcterms:rights field". Could this functionality borrow that logic? E.g. users who don't want to use CC0 for license should enter NONE, and for termsOfUse enter CC-BY (and even better, include the URL https://creativecommons.org/licenses/by/2.0)? |
@pdurbin -just wanted to mention #6497 work. It would let you set any metadata on a dataset (without having to read the existing metadata, update the one field, and send it back), but it doesn't yet cover bulk operations. It could though - wondering if adding bulk options to this, (or at least thinking that if you write bulk operation code, it could be reused for this) would help. I do have some working code for this - got busy on other things and didn't make a PR yet but I could post what I have if that would help. |
There's a new kid on the block with related goals #7440 |
Heads up that pull request #7414 might close this issue. |
Some users want to be able to change Terms of Use metadata for multiple datasets in bulk (without need to open and edit each dataset's metadata). Users can use the Native API to add or edit metadata in the metadata fields that are in Dataverse's metadata blocks, but as of 4.19 the Native API doesn't let users do the same for Terms of Use and Terms of Access fields (in the Terms tab). In fact, if you use the "Update Metadata" endpoint to create or edit a dataset draft, which will overwrite any existing dataset metadata, all values in the Terms of Use and Terms of Access fields are also removed.
It would also be helpful to document in some brief way which fields can and can't be edited using the Native API.
(This is following discussion from the related issue at #2585)
The text was updated successfully, but these errors were encountered: