Dataverse Community Norms

CC0 Waiver for Datasets

By default, all datasets added into Dataverse are granted the CC0 Public Domain Dedication. Dataverse uses the CC0 waiver by default for all datasets (4.0 and on) because of its name recognition in the scientific community, making it a familiar option for data (for which in general copyright does not apply), and is in use by repositories as well as scientific journals that require the deposit of open data. For more information on the CC0 waiver, please visit the Creative Commons website (http://creativecommons.org/about/cc0). Data depositors can opt-out of using the CC0 waiver for their datasets, if needed.

Dataverse asks that all users who download datasets from Dataverse’s services follow the following Community Norms.*

Crediting any research used with data citations

Any materials (books, articles, conference papers, theses, dissertations, reports, and other such publications) created that employ, reference, or otherwise utilize the data (in whole or in part) gathered from deposited datasets should credit the source with the applicable data citation generated by Dataverse (found on the dataset page). These citations include the data authors, data identifier, and other information in accordance with the Joint Declaration of Data Citation Principles (http://force11.org/datacitation) for all research data. To find out more, visit our Data Citation Best Practices guide (http://best-practices.dataverse.org/data-citation/).

Maintaining anonymity of human subjects

Users of the Service should not abuse the available data that relate to human subjects and use the materials to:

  1. obtain information that could directly or indirectly identify any research subjects, or obtain information to attempt to directly or indirectly identify any research subjects;
  2. produce and/or publish connections among datasets that could identify individuals or organizations; or
  3. obtain (additional) information about or (additional) means of contact for already-identified subjects.

Legal Disclaimer: these Community Norms are not a substitute for the CC0 or custom licenses applicable to each dataset. Please be advised that the Community Norms are not a binding contractual agreement, and that downloading datasets from Dataverse does not create a legal obligation to follow these policies.

Third Party API Applications

If you are interested in building an API application designed (exclusively or not) to allow and provide access to Harvard Dataverse and its materials and services, please keep in mind that such applications:

  1. must ensure that all users of the application read and agree to both the Dataverse API Terms of Use (http://best-practices.dataverse.org/harvard-policies/harvard-api-tou.html) and Harvard Dataverse’s General Terms of Use (http://best-practices.dataverse.org/harvard-policies/harvard-terms-of-use.html);
  2. must post both the Dataverse API Terms of Use and Harvard Dataverse’s General Terms of Use in an adequately noticeable and conveniently-accessible place so that all users of the application and easily find and view it;
  3. acknowledge and agree that Harvard Dataverse is not otherwise affiliated with any third-party Dataverse API applications that provide access to Harvard Dataverse, and therefore will not be held responsible or liable (in whole or in part) for any suits or damages incurred by the third-party Dataverse API application owners, administrators, and affiliates; and
  4. must clearly publish its third-party non-affiliation status in relation to Harvard Dataverse in its application and disclaim any special relationship with Harvard Dataverse outside of the ones arising out of the obligations agreed upon from this Terms of Use and Harvard Dataverse’s General Terms of Use agreements.