Скачать презентацию The PREMIS of the UCSD DAMS Arwen Hutt Скачать презентацию The PREMIS of the UCSD DAMS Arwen Hutt

74ecf99befc8bb2b2cb94f0f03579b9a.ppt

  • Количество слайдов: 7

The PREMIS of the UCSD DAMS Arwen Hutt & Bradley D. Westbrook Metadata Analysis 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, 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 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 Object Requirements METS Profiles ◦ ◦ Codify requirements for the DAMS Simple Object Profile & Complex Object Profile PREMIS tech. MD section required Additional, tech. MD sections optional format specific metadata MIX Audio Spec / Guidelines (potential)

Required PREMIS Elements Required: pre/object. Identifier/object. Identifier. Type pre/object. Identifier/object. Identifier. Value pre/object/preservation. Level Required PREMIS Elements Required: pre/object. Identifier/object. Identifier. Type pre/object. Identifier/object. Identifier. Value pre/object/preservation. Level pre/object. Category (file) pre/object. Characteristics/fixity/message. Digest. Algorithm pre/object. Characteristics/fixity/message. Digest pre/object. Characteristics/size pre/object. Characteristics/format. Name pre/object/creating. Application/date. Created. By. Application Encouraged, but not required: pre/object/storage. Medium pre/object. Characteristics/format. Designation/format. Version pre/object/creating. Application. Name ◦ pre/object/original. Name ◦ ◦ ◦ ◦

Implementing PREMIS Where does it come from? ◦ Automated extraction and recording (jhove) ◦ 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 Limitations of the DAMS’ PREMIS Use only base level object assertions No use of event, agent, or rights assertions