Skip to content
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

Feature Request/Idea: Add Standard CC and Custom Licenses to DDI Export Metadata #9871

Open
amberleahey opened this issue Aug 31, 2023 · 3 comments

Comments

@amberleahey
Copy link

amberleahey commented Aug 31, 2023

Overview of the Feature Request
We are using DDI XML exports from Dataverse in our Odesi data catalogue for searching and exploring datasets. We'd like to be able to display the Terms and Conditions as a button with a pop-up window containing the terms of use (including licenses) and terms of access stored in Dataverse's metadata for a given dataset before a user can download from the catalogue interface.

See beta site: https://beta.odesi.ca fully connected to Dataverse repository in the backend

What kind of user is the feature intended for?
All users of DDI metadata coming from a Dataverse will benefit from having Dataverse's standard licenses (Terms of Use / Terms) be cross walked and made available in DDI Exports. Standard licenses such as Creative Commons CC-0 or CC-By are not mapped to DDI exports only the Terms of Access fields.
See example DDI exports 1) Dataverse Record example 2) DDI export of that example (https://borealisdata.ca/api/datasets/export?exporter=ddi&persistentId=doi%3A10.5683/SP/AUCWOZ

What inspired the request?
we noticed that not all the terms metadata is being exported to DDI, especially CC licenses

What existing behavior do you want changed?
Would be great to map this Dataverse terms metadata to DDI's
dataAccs>setAvail/>useStmt/>dataAccs> section, like how it's done for when a Custom License is added to Dataverse
see: DDI export with custom license available (https://dataverse.harvard.edu/api/datasets/export?exporter=ddi&persistentId=doi%3A10.7910/DVN/ICISE4)

For example (custom license mapping to DDI from example linked above):
dataAccs>setAvail/>useStmt>
disclaimer>The American Journal of Political Science and the Odum Institute for Research in Social Science are not responsible for the accuracy or quality of data uploaded within the AJPS Dataverse, for the use of those data, or for interpretations or conclusions based on their use. /disclaimer>
useStmt>
dataAccs>

Any brand new behavior do you want to add to Dataverse?
Support for licenses in DDI 2.6 is a bit better than DDI 2.5 --- see https://ddi-alliance.atlassian.net/wiki/spaces/DDI4/pages/2851340301/Codebook+Tree+Diagram+Version+2.6

I'm thinking about this, but could confirm if 1.1.4.4 license (0-n) [URI, type] may work or there are additional fields supported under 2.6 dataAccs (0-n) has some new fields....TBD

Any open or closed issues related to this feature request?
Yes this seems related a bit, in terms of the examples provided:

@jggautier
Copy link
Contributor

jggautier commented Aug 31, 2023

I added that #8355 is related, too.

@jggautier
Copy link
Contributor

I rediscovered that Terms of Use metadata is missing from the exports of Dataverse installations running more recent versions of Dataverse, so I noted that in the related GitHub issue I opened at #8355, then realized that this issue already mentions that Terms of Use metadata is missing. So I closed #8355 in favor of this GitHub issue.

@jggautier
Copy link
Contributor

@amberleahey, do you mind if we edit this issue's title to reflect that we're also talking about including metadata of "custom licenses"?

@amberleahey amberleahey changed the title Feature Request/Idea: Add Standard CC Licenses to DDI Export Metadata Feature Request/Idea: Add Standard CC and Custom Licenses to DDI Export Metadata Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

No branches or pull requests

3 participants