Implementation of PREMIS in METS Rebecca Guenther Sr. Networking & Standards Specialist, Library of Congress PREMIS Implementation Fair San Francisco, CA October 7, 2009

 METS records the (possibly hierarchical) structure of digital objects, the names and locations of the files that comprise those objects, and the associated metadata  A METS document may be a unit of storage (e.g. OAIS AIP) or a transmission format (e.g. OAIS SIP or DIP)  METS is extensible and modular  METS uses the XML Schema facility for combining vocabularies from different Namespaces  The METS Editorial Board has endorsed PREMIS as an extension schema  Many institutions trying to use PREMIS within the METS context

Structure of a METS file

Archival Information Package Descriptive Information Content Information described by derived from delimited by identifies further described by Representation Information Data Object Semantics Provenance Information Reference Information Fixity Information Context Information Preservation Description Information Packaging Information Structure described by premis:event MODS MARCXML DC premis:object metsRights premis:rights File formatspremis:object textMD MIX OAIS, METS and PREMIS Legend Black Arial = OAIS Red Times New Roman = METS Primary Schema Blue Times New Roman Italics = Extension Schema

METS extension schemas  “wrappers” or “sockets” where elements from other schemas can be plugged in  Provides extensibility  Uses the XML Schema facility for combining vocabularies from different Namespaces  Endorsed extension schemas: Descriptive: MODS, DC, MARCXML Technical metadata: MIX (image); textMD (text) Preservation related: PREMIS

Why do we need guidelines for using PREMIS with METS?  Contents of each information package may vary depending on its function within a repository  Need to determine how to include representation metadata and associate it with package components  PREMIS data entities (objects, events, rights, agents) do not map perfectly to METS categories for representation metadata (techMD, digiProvMD, rightsMD, sourceMD)  There are redundant elements between the two standards  Both have extensibility mechanisms  Flexibility of both standards requires implementation choices

Development of Guidelines for Using PREMIS with METS for Exchange  PREMIS in METS Guidelines Working Group Consists of PREMIS and METS experts Focuses on the METS document as a mechanism of exchange of digital objects and their metadata (SIP or DIP) Facilitates communication when internal requirements and technical environments vary  Tension between flexibility and being prescriptive to facilitate interoperability Consider usage scenarios If a SIP it may get unwrapped and stored in different structures If a DIP it is converted from internal structures to PREMIS A more liberal approach is possible for a SIP than a DIP  Establishing guidelines, a METS profile, and examples

Implementation issues in using PREMIS with METS  Location of PREMIS metadata within METS documents  Whether to record elements redundantly if they occur in both PREMIS and METS  Relationship of different structural metadata mechanisms in PREMIS and METS  How to record PREMIS Agent entities in METS documents  Use of identifiers to link elements in PREMIS and METS  How to record elements that are also part of a format specific technical metadata schema (e.g. MIX)

Some recommendations from Guidelines  METS sections Use Object in techMD or digiProvMD Use Event in digiProvMD Use Rights in rightsMD Use Agent in digiProvMD or rightsMD  PREMIS Container -- use only if keeping all PREMIS metadata together. Do not use if separating PREMIS metadata into different amdSec subelements  PREMIS and METS redundancies -- Choosing which options to use is an implementation decision, document in profile e.g. METS element attributes and subelements of in PREMIS

Recommendations (cont.)  Structural relationship elements -- use the METS structMap to record structural relationships, use PREMIS relationship elements to record preservation and derivation relationships and structural if desired  ID/IDREF and PREMIS identifier elements -- use METS ID/IDREF mechanisms, best practices for using these ID/IDREF mechanisms apply  Use PREMIS extensibility mechanism for format specific technical metadata  Document decisions in METS profiles

SHA bc65c5b d09ad373eefd147382ecbf EchoDep/messageDigestOriginator> Elements defined in both METS and PREMIS: METS: Checksum, Checksumtype attribute of not repeatable  PREMIS: fixity also includes messageDigestOriginator allows multiples

<file ID="FID1" ADMID="TMD1PREMIS DP1EVENT DP1AGENT“ MIMETYPE="image/jpeg" <techMD ID="TMD1PREMIS“ image/jpeg 1.02 Elements defined both in METS and PREMIS: METS: MIMETYPE attribute of optional  PREMIS: more granular; includes name and version (although name may be MIMETYPE) mandatory

ECHODEP Hub Event echo12345 ECHODEP Hub Event echo12345 ingestion T15:12:53 Elements defined both in METS and PREMIS  METS ID/Idref: used to associate metadata in different sections and for different files  PREMIS identifiers: explicit linking between entity types

structural is sibling of UCB FID2 1 Elements defined both in METS and PREMIS:  METS: structMap details structural relationships and is the heart of the METS document hierarchical, so may be more expressive than PREMIS semantic units links the elements of the structure to content files and metadata  PREMIS: details all kinds of relationships, including structural data dictionary says that implementations may record by other means

Some METS profiles with PREMIS  UCSD simple and complex object  UC Berkeley  ECHO Dep Generic METS Profile for Preservation and Digital Repository Interoperability  LC Profile for Recorded Events  Australian METS Profile  TIPR  … many others

Additional changes to Guidelines  Make extensibility mechanism consistent with METS significantPropertiesExtension objectCharacteristicsExtension creatingApplicationExtension environmentExtension signatureInformationExtension eventOutcomeDetailExtension rightsExtension

Additional changes to Guidelines (cont.)  Add the same elements and attributes as in METS to PREMIS extension elements in schema and data dictionary mdRef, mdWrap binData, xmlData Attributes: ID, LABEL, MDTYPE, MIMETYPE, SIZE, CREATED, CHECKSUM, CHECKSUMTYPE  Allow URI or string for MDTYPE  Add use cases/examples to illustrate choices made  Clarify structural relationships

Implementing an Exchange Standard  PREMIS Implementation Tool Some tools documented on the PREMIS website php php PiM tool developed by Florida Center for Library Automation PiM Further work to generate metadata from digital files in PREMIS elements