1 / 7

The PREMIS of the UCSD DAMS

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

italia
Download Presentation

The PREMIS of the UCSD DAMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 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

  2. 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

  3. 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

  4. 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)

  5. 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

  6. 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

  7. Limitations of the DAMS’ PREMIS • Use only base level object assertions • No use of event, agent, or rights assertions

More Related