Prepared by: DLP Metadata Implementation Working Group (M-IWG)
...
Status: Final Draft for Approval
Reviewed by: M-IWG, DLP Core Team
...
| Table of Contents |
|---|
...
Overview
...
This document includes specifications for Preservation Events and Workflows metadata relative to requirements identified by the M-IWG and Digital Preservation Functional Requirements Group. Requirements for individual digital files’ characteristics is documented separately in M-IWG’sTechnical/Characterization Metadata Specification. Additional supplemental preservation metadata (aka “Source Metadata”) that describes the original carrier or originating environment from which a digital surrogate is derived may be included in a digital object’s preservation package, but is not directly actionable by the DLP repository software.
...
Detailed information about specific metadata units is documented in thePreservation Events and Workflows worksheet.
Work Process
A review of current state metadata and practices was conducted, including the following sources:
The Keep
OpenEmory
ETDs (legacy application)
Library of Congress Preservation Event Types (2017 revision)
Emory Libraries Digital Preservation Policy
Emory Libraries Digital Collections Retention Policy
...
Full details for the metadata described below are found in thePreservation Events and Workflows worksheet. (Note: this spreadsheet includes information for some metadata units documented in theRights Metadata Inventory.)
The diagram that follows shows the relationship of preservation workflows and events as related to individual objects in the repository context.
...
Adjust or expand metadata as needed to accommodate specific event-level functionality once more implementation details are known. Specific event outcome details (e.g. fixity check results) could be stored as lengthy text notes, but may benefit from more granular field definitions.
Revisit metadata units for optimization in their final implementation serialization: revisions may be needed if the metadata is stored in RDF vs. XML vs. a relational database
Index and/or enable events and workflows metadata in search or reporting capabilities, so that content curators are able to monitor preservation health of their content and the system as a whole
Work with implementation team to determine any required events that should always occur for a given preservation workflow, so that if the events do not run when expected, this information is also recorded
For migration purposes, migrate legacy content’s PREMIS and/or audit trails as supplemental preservation files and generate new preservation metadata moving forward relative to the date of re-ingest to the DLP repository
Establish a local vocabulary for labeling/relating supplemental preservation files, extending the PCDM File Use vocabulary if appropriate (see suggested values)