Licensing & Terms of Use: Add CC0 and Custom Terms of Use to Dataset

[eaquigley]

---

Author Name: Kevin Condon (@kcondon)
Original Redmine Issue: 2963, https://redmine.hmdc.harvard.edu/issues/2963
Original Date: 2013-05-17

---

This was requested by Merce and Eleni, see RT #158870:

Yes, good point, it would be CC0 and CC-BY, which are the most standard
options offered in other data repositories.

From the technical side, we should plan this for v3.6 and decide where in
the study cataloging these licenses would appear and how the data depositor
would choose a license.

From the legal, policy side, I'll talk to some people in the Berkman
center/Law School to check if choosing one of these licenses is consistent
with the current DVN terms of use.

Merce

[eaquigley]

Sending to @mheppler to create mockups based off discussion on 7/17/2014

[eaquigley]

For CC-0, CC-BY, and Terms of Use we want two workflows:

1. For when it is a dataset added in 4.0
2. For when it is a dataset that was added to Dataverse prior to 4.0 and migrated over

For workflow 1, @mheppler will create mockups that show when the user would be able to decide on CC-0, CC-BY, or add in their own custom Terms of Use. Dataverse should be able to check if there are any files with restriction permissions when a user goes to publish a dataset so they are given the option to add a CC-0 or CC-BY if there are no restricted files or add their own custom Terms of Use (for mockups, will use ToU form found in 3.6). ToU will appear in a separate tab on the dataset page, CC-0 or CC-BY logo will appear near the title of the dataset

For workflow 2, mockups will show a user being able to click on Edit Dataset->a Terms of Use option->and then edit them or choose CC-0 or CC-BY if the dataset is eligible (i.e.-no restricted files).

[eaquigley]

More notes:
-Set license and terms of use, at the version level. Once, a user sets them at a particular version, they are frozen for that version and can never be changed. Additionally, changing terms of use or license is a MAJOR version change so the version number will be bumped up.
-Terms of Use for a dataset in 3.x, should be carried over to 4.0

[mheppler]

[mheppler]

Assigning this issue to Eleni, for her to get clarification from Berkman on the mockups. She can pass it back to me to begin wireframe development or mockup revisions based upon their feedback.