DataverseNO Documentation Review:C.3.a
|Document Title||Requirements Where Used||Purpose or Objective of Document||Other Documents Referenced|
|Partner Agreement (not public)||R0.|
|About DataverseNO||R0., R5., R13.||Outlines who owns and operates DataverseNO and information for both Norwegian research institutions and individual researchers. It also includes information about data curation and preservation, metadata harvesting, the structure of the repository, the governance of the repository, collections management, and the designated community. It also includes information about where to get support/help.|
|Deposit Agreement||R0., R2., R3., R4., R5., R7., R8., R10., R12.||Agreement between DataverseNO and depositors. It outlines that the depositor must have ownership of the data or permission to post the data and that they've removed all personal info. It also outlines that DataverseNO is given non-exclusive rights to reproduce, translate, and distribute the dataset being deposited. The agreement also gives DataverseNO permission to convert data or metadata into applicable formats for preservation purposes.|
|Preservation Policy||R0., R1., R2., R3., R7., R9., R10., R12., R14., R15.||Outlines DataverseNO's responsibilities regarding long-term stewardship of datasets. It also notes that the preservation policy reflects the seven attributes of a trusted digital repository. The policy also outlines the policy with regards to OAIS compliance, pre-ingest, ingest, archival storage, data management, version control and change procedures, data deaccessioning, access, administration, preservation planning, administrative responsibility, DataverseNO mandate and commitments, preservation objectives, constraints, organizational viability, scope, operating principles, roles and responsibilities, selection and accession, access and use, challenges and risks, financial and organizational sustainability, institutional commitment, partner institutions, funding model, deposit requirements, preservation strategies, levels of preservation, continuity of access, planning and monitoring, communication and training, systems security and disaster recovery, audit and transparency, and policy administration.|
|Curator Guidelines||R0., R4., R5., R7., R8., R12.||Contains guidelines and instructions on how partner (member) institutions are supposed to curate the data they receive. Guidelines include instructions on how to check that the dataset to ensure it meets the Accession Policy requirements and that the depositor placed the dataset in the correct location. It then provides instructions on how to curate metadata, file types and formats (including a readme file), and terms and license agreements. It also includes instructions on how to publish the curated dataset, what happens when a new version is published, how to access unpublished datasets or locked files, how to move datasets, and how to delete a published dataset.|
|Accession Policy||R0., R4., R8., R10., R11., R12., R14.||Explains specific requirements all datasets must meet in order to be published in the DataverseNO repository. Includes a list of inclusion criteria; quality control; discovery and access; copyright, IP and digital rights; and DataverseNO's commitment to published datasets.|
|Deaccession Procedure||None||Provides criteria about when and why datasets can be deaccessioned. Criteria include not meeting the requirements of Accession Policy, detection of malware, copyright or contract violation, research misconduct, legal requirements, national security, or research ethics violations. Only DataverseNO staff are about to deaccession a dataset|
|Deaccession Guidelines||None||Contains guidelines on what is done when a depositor finds an error in their dataset. It specifically directs the depositor to submit a corrected file and a new version of the dataset will be created. It also outlines what DataverseNO considers if they're told the error may pose a risk to the accuracy of future scholarship.|
|Steering Document||R1., R3., R5., R16.||Includes information about DataverseNO and its funding and commitments.|
|Policy Framework & Definitions||R1., R5., R8.||Includes an overview of DataverseNO and its objectives/purpose. It also includes DataverseNO's quality commitments, policies, and the policy review process. It also includes a list of terms and their definitions as per the DataverseNO repository.|
|Access & Use Policy||R2.||Includes an overview of DataverseNO's commitment to facilitating maximum access and use of research data to data published in the DataverseNO repository. These commitments include the dissemination of content via indexing and harvesting, public access to the content, collection of web analytics for tracking the use of the data, and copyright and licensing responsibilities.|
|Deposit Guidelines||R2., R5., R7., R8., R10., R11., R12., R14.|
(Contained in files titled "Prepare your data" and "Deposit your data.")
"Prepare your data" outlines what criteria datasets must meet in order to be considered for deposit in DataverseNO. This includes file naming, preferred file formats, data descriptions including metadata and a ReadMe file, and file size.
"Deposit your data" provides specific instructions on creating a user account and/or logging in, creating a dataset draft, entering metadata, confirming licenses and attributions, uploading data files, and how to submit an unpublished dataset for review.
|Administrator Guidelines||R5.||Not available in English.|
|Preservation Plan||R10., R14.||The Preservation Plan documents the implementation of the Preservation Policy. In addition to describing preservation steps used by DataverseNO, it also provides justification for why this specific plan was selected. This plan specifically indicates that it was created in order to comply with CTS requirements. Outlines that the application of the plan is based on the regular review of the five digital asset groups. The plan further defines three preservation levels (bit-level, normalization, and format migration) and which of these levels are applied to which digital asset group.|
C.3.b Interesting Items of Note:
- The DataverseNO CTS application is much longer than a CTS application needs to be. While it's an excellent example of a well-documented repository, CTS application, in general, should be much shorter and more succinct. CTS specifically requests that text within an application should not be repeated, but instead cross-referenced.
- The various DataverseNO policies and guidelines are excellent examples of how these items could be documented. These policies and guidelines could be used as starting points for similar policies and guidelines for both Scholars Portal and member institutions.
C.3.c File List:
Back to Documentation Review.