70 likes | 214 Views
The PREMIS of the UCSD DAMS. Arwen Hutt & Bradley D. Westbrook Metadata Analysis and Specification Unit UCSD Libraries For PREMIS Workshop La Jolla, CA, 11 Feb 2008. Local Context. UCSD Libraries’ Digital Content
E N D
The PREMIS of the UCSD DAMS Arwen Hutt & Bradley D. Westbrook Metadata Analysis and Specification Unit UCSD Libraries For PREMIS Workshop La Jolla, CA, 11 Feb 2008
Local Context • UCSD Libraries’ Digital Content • Digital production distributed throughout the libraries (MSCL, SIO, AAL, etc.) • Projects dating from the mid-nineties • Metadata (descriptive & technical) varies • Formats are fairly, but not completely, homogenous; primarily images at this point, but also text, audio and video. • UCSD Libraries’ DAMS • Bring together Libraries’ digital objects to facilitate management • Normalize metadata
Arriving at PREMIS • Problem of Technical Metadata • Common semantic units encoded/stored in many different ways (both standard and local) • Simplify management • Support format specific metadata • Choice of PREMIS • Express non format specific metadata • (Current) management procedures utilize the same elements regardless of file format • Extensible for supporting future additional management functions
Object Requirements • METS Profiles • Codify requirements for the DAMS • Simple Object Profile & Complex Object Profile • PREMIS techMD section required • Additional, techMD sections optional for format specific metadata • MIX • Audio Spec / Guidelines (potential)
Required PREMIS Elements • Elements • Required: • pre/object/objectIdentifier/objectIdentifierType • pre/object/objectIdentifier/objectIdentifierValue • pre/object/preservationLevel • pre/object/objectCategory (file) • pre/object/objectCharacteristics/fixity/messageDigestAlgorithm • pre/object/objectCharacteristics/fixity/messageDigest • pre/object/objectCharacteristics/size • pre/object/objectCharacteristics/format/formatName • pre/object/creatingApplication/dateCreatedByApplication • Encouraged, but not required: • pre/object/storage/storageMedium • pre/object/objectCharacteristics/formatDesignation/formatVersion pre/object/creatingApplication/creatingApplicationName • pre/object/originalName
Implementing PREMIS • Where does it come from? • Automated extraction and recording (jhove) • Taken from legacy metadata (either recorded in house or vendor supplied) • Management Functions • Authenticity verification • Replication of files to CDL’s DPR • Format migration
Limitations of the DAMS’ PREMIS • Use only base level object assertions • No use of event, agent, or rights assertions