Odum Institute Documentation Review:C.4.a
|Document Title||Requirements Where Used||Purpose or Objective of Document||Other Documents Referenced|
|Org Chart||R0., R5.|
|Data-PASS Articles of Collaboration||R0., R3.||Articles of collaboration for the Data Preservation Alliance for the Social Sciences (Data-PASS), which is sponsored by the Library of Congress. Members include ICPSR (lead member), Odum, Roper, Harvard-MIT, Murray, and NARA (no funding support). The partnership will use the services offered through its institutions to identify, appraise, acquire, catalogue, and preserve at-risk social science data. Each institution is responsible for specific areas as outlined in the Appraisal Guidelines (not included).|
|Data-PASS Confidentiality Policies||None||Provides a set of guidelines on how Data-PASS institutions will protect the privacy of study participants of the social science data their preserve.|
|Digital Preservation Policy||R1., R3., R5., R6., R7., R9., R10., R14.||Outlines the implementation of the Odum digital preservation strategic plan. The document outlines the mandate and objectives of the preservation policy, the viability of Odum in long term (including financial stability), the technological and procedural techniques used in preservation, aspects of system security, and procedural accountability.|
|Mission Statement||R1.||Outlines the mission, vision, and values of the Odum Institute for Research in Social Science.|
|Data Security Guidelines||R2., R12.||Outlines the guidelines Odum follows with regards to personally identifiable information and protected health information that could be found in the social science data preserved in the Odum data archive.|
|UNC ITS Security Policy||R2., R9., R15, R16.|
|Collection Development Policy||R4., R8., R10., R11., R12.||Provides information on the items Odum has included and wants to include in their data archive, from a social science perspective. The document also provides an outline of who Odum's designated community includes. This policy also includes information about how the data is appraised, the acceptable file formats, levels of curation, and a self-archiving option.|
|Data Curation Workflow||R4., R7., R8., R10., R11., R12.||Explains the process Odum data curation staff go through when they receive a dataset for deposit. The curation workflow is a 4-stage process: deposit, triage, processing, and access. The document includes a visualization of the workflow and a description of what's included in each stage.|
|SOP: Data Deposit||R4., R8., R10., R11., R12.||Provides step-by-step instructions as to what Odum data curators are required to do when they receive a submission information package (SIP) from a data contributor. Instructions are broken down by the 4 stages mentioned in the Data Curation Workflow: deposit, triage, processing, and access.|
|SOP: Sensitive Data Handling||R4., R12.|
A short document that outlines procedures for handling dataset files that contain personally identifiable information, protected health information, or other sensitive data. Sensitive data is identified by Odum data curators during the Triage stage. Odum's data archive (as per the Data Security Guidelines) doesn't allow sensitive data to be stored in their archive. Odum has 2 situations: (1) Under normal circumstances, deposits are rejected and returned to depositors if sensitive data is found during triage, or (2) Under specific agreements, Odum data curators will do the de-identification work on behalf of the depositor. If data curators are doing this type of work, this document outlines how to transmit and store that sensitive information until it's been de-identified.
|SOP: Cataloging||R7., R11., R12., R14.||Provides instructions for Odum data curators to use when creating records for submitted datasets, which occurs during the ingest stage of the Data Curation Workflow. These instructions include applying controlled vocabularies and generating standardized metadata. Appendix A provides a controlled vocabulary for several metadata fields in the system. Appendix B provides the rules to follow when completing specific metadata fields.|
|Metadata Guidelines||R7., R11., R13., R14.|
Provides information regarding the standardized metadata generated for datasets in the Odum data archive and what it is used for. It further outlines the different types or levels of metadata that are generated for datasets (i.e., dataset vs. file vs. variable level, descriptive vs. structural vs. administrative metadata). Finally, it outlines the metadata standards the archive has adopted and the minimum metadata requirements for each dataset.
|OAIS Document||R9., R12., R15.||Commits that Odum takes responsibility for receiving, curating, processing, and preserving the data it receives, and to disseminate that data to its designated community. The document outlines the six OAIS-defined functional entities of the technical implementation of the Odum archive. Includes a diagram outlining this process as well. Six functional entities are data ingest, data storage, data management, administration, preservation planning, and data access.|
C.4.b Interesting Items of Notes:
C.4.c File List:
Return to Documentation Review.