Digital Preservation Metadata
Introduction
This activity entails annotating a Metadata Encoding and Transmission Standard (METS) record for one item. The purpose of the assignment is to learn how the elements of a simple METS record work together and how preservation metadata derived from the PREservation Metadata Implementation Strategies (PREMIS) can be used to document preservation activities and changes to the item over time. The activity involves saving a record containing rich METS records locally and annotating that METS record to describe the major components of the METS record, including PREMIS components. The net result of the activity is a demonstration of the capability to “read” METS and PREMIS records and explain what happened to the item.
Preparation
- To do this activity, you will need to use a text editing program or application to annotate the data. Suggested text editors that you may download are Notepad++ (Windows) or Sublime (Mac or Windows).
- If you do not have a text editor, you can save the METS as an XML file to your computer, upload it to your Google Drive, and use Drive’s text editor to annotate.
- Additionally, it will be good to have the METS and PREMIS standards documents up in a separate tab for reference during this activity.
Steps to Take
Save this METS file locally by opening it in a separate web browser tab, right-clicking anywhere within the text, and selecting “Save As.” When saving, make sure that you are saving it as an XML file by selecting “XML” from the list of file formats available.
Open the METS XML file using the text editing program of your choice.
Within the text editor, compare the METS record for your item with the METS Schema 1.12.1 (current version), METS Primer, and other documentation on the METS website. The goal of this first step is to get comfortable with METS tags, to figure out which elements of the METS schema are included in the record and which might be missing.
Annotate the METS record by identifying all the major (and sub-) elements listed below and also commenting on the additional items I listed. Not all the elements are in the record, so make sure to comment on the missing ones. For repeating elements, you do not need to identify each, but add a single comment to explain. The syntax for inline comments in XML is:
<!-- Your Comment -->.
- METS
- Does the record include
<mdWrap>or<mdRef>? - Header
<metsHdr>- Indicate version of METS
- Indicate version of PREMIS
- Indicate version of MODS
- Descriptive metadata section
<dmdSec>- Indicate what descriptive standard the METS uses
- Administrative
<amdSec>- Technical
<techMD> - Digital Provenance
<digiprovMD> - Source
<sourceMD> - Rights
<rightsMD>
- Technical
- File Section
<fileSec>- Indicate if the File section uses
<FLocat>(pointer to resource) or<FContent>(content in XML).
- Indicate if the File section uses
- Structural Map
<structMap>- Indicate if the
<div>sections contain multiple METS pointers (<mptr>) and/or file pointer (<fptr>)
- Indicate if the
- Structural links
<smLink> - Behavior
<behavior>
- Does the record include
- PREMIS
- Objects: What are the objects?
- Intellectual Entity
- Representation
- File
- Bitstream
- Environment
- Agents: What is the agent? Person, organization, software
- Events: Comment to indicate what the events are
- Rights statement
- Objects: What are the objects?
Reporting
- Attach your annotated METS record as .xml in Brightspace.
Resources
The following are links to websites with relevant documentation: