Feature Request/Idea: Add Standard CC and Custom Licenses to DDI Export Metadata #9871
Labels
Feature: Metadata
Feature: Terms & Licensing
Type: Suggestion
an idea
User Role: Guest
Anyone using the system, even without an account
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:
The text was updated successfully, but these errors were encountered: