Differences between revisions 45 and 47 (spanning 2 versions)
⇤ ← Revision 45 as of 2010-01-05 11:58:07 →
Size: 3961
Editor: ek
Comment:
← Revision 47 as of 2010-01-05 12:39:45 → ⇥
Size: 3758
Editor: ek
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

Metadata in a variety of forms — technical, structural, rights, and provenance — lies at the heart of most preservation activities. While a number of detailed metadata standards exist in many specific areas, the purpose of the joint OCLC/RLG PREMIS activity was to develop an overall framework and core element set for preservation metadata. The PREMIS data model defines a number of properties of preservation significance for digital objects, events, agents, rights and permissions, and the relationships between these entities.
Line 49: Line 47:
 * 1.8 environment (O, R)
 * 1.8.1 environmentCharacteristic (O, NR)
 * 1.8.2 environmentPurpose (O, R)
 * 1.8.3 environmentNote (O, R)
 * 1.8.4 dependency O, R)
 * 1.8.4.1 dependencyName(O, R)
 * 1.8.4.2 dependencyIdentifier (O, R)
 * 1.8.4.2.1 dependencyIdentifierType (M, NR)
 * 1.8.4.2.2 dependencyIdentifierValue (M, NR)

PREMIS in DOMS

[under construction]

The PREMIS preservation metadata as defined in the PREMIS Data Dictionary is "the information a repository uses to support the digital preservation process." One of the main principles behind PREMIS is that you need to be very clear about what you are describing. PREMIS defines five kind of entities: Intellectual, Objects, Events, Agents and Rights. This is called the PREMIS data model: [indsæt figur]

  • 1. Intellectual entities are conceptual and might be called "bibliographic entities".

  • 2. Object entities are what are actually stores and managed in the preservation repository

  • 3. Event entities aggregate information about actions that affect objects in the repository

  • 4. Agent entities are actors that have roles in events and in rights statements

  • 5. Rights entities aggregate information about rights and permissionsthat are directly relevant to preserving objects in the repository.

We have chosen to use only the entity Object (or Digital Object). Below is an outline of the semantic units and components we are going to adopt:

  • 1.1 objectIdentifier (M, R)
  • 1.1.1 objectIdentifierType (M, NR)
  • 1.1.2 objectIdentifierValue (M, NR)
  • 1.2 objectCategory (M, NR)
  • 1.3 preservationLevel (O, R) [representation, file]
  • 1.3.1 preservationLevelValue (M, NR) [representation, file]
  • 1.3.2 preservationLevelRole (O, NR) [representation, file]
  • 1.3.3 preservationLevelRationale (O, R) [representation, file]
  • 1.3.4 preservationLevelDateAssigned (O, NR) [representation, file]
  • 1.5 objectCharacteristics (M, R) [file, bitstream]
  • 1.5.1 compositionLevel (M, NR) [file, bitstream]
  • 1.5.2 fixity (O, R) [file, bitstream]
  • 1.5.2.1 messageDigestAlgorithm (M, NR) [file, bitstream]
  • 1.5.2.2 messageDigest (M, NR) [file, bitstream]
  • 1.5.2.3 messageDigestOriginator (O, NR) [file, bitstream]
  • 1.5.3 size (O, NR) [file, bitstream]
  • 1.5.4 format (M, R) [file, bitstream]
  • 1.5.4.1 formatDesignation (O, NR) [file, bitstream]
  • 1.5.4.1.1 formatName (M, NR) [file, bitstream]
  • 1.5.4.1.2 formatVersion (O, NR) [file, bitstream]
  • 1.5.4.2 formatRegistry (O, NR) [file, bitstream]
  • 1.5.4.2.1 formatRegistryName (M, NR) [file, bitstream]
  • 1.5.4.2.2 formatRegistryKey (M, NR) [file, bitstream]
  • 1.5.4.2.3 formatRegistryRole (O, NR) [file, bitstream]
  • 1.5.4.3 formatNote (O, R) [file, bitstream]
  • 1.5.5 creatingApplication (O, R) [file, bitstream]
  • 1.5.5.1 creatingApplicationName (O, NR) [file, bitstream]
  • 1.5.5.2 creatingApplicationVersion (O, NR) [file, bitstream]
  • 1.5.5.3 dateCreatedByApplication (O, NR) [file, bitstream]
  • 1.5.5.4 creatingApplicationExtension (O, R) [file, bitstream]
  • 1.5.7 objectCharacteristicsExtension (O, R) [file, bitstream
  • 1.6 originalName (O, NR) [representation, file]
  • 1.8 environment (O, R)
  • 1.8.1 environmentCharacteristic (O, NR)
  • 1.8.2 environmentPurpose (O, R)
  • 1.8.3 environmentNote (O, R)
  • 1.8.4 dependency O, R)
  • 1.8.4.1 dependencyName(O, R)
  • 1.8.4.2 dependencyIdentifier (O, R)
  • 1.8.4.2.1 dependencyIdentifierType (M, NR)
  • 1.8.4.2.2 dependencyIdentifierValue (M, NR)
  • 1.8.5 software (O, R)
  • 1.8.5.1 swName (M, NR)
  • 1.8.5.2 swVersion (O, NR)
  • 1.8.5.3 swType (M, NR)
  • 1.8.5.4 swOtherInformation (O, R)
  • 1.8.5.5 swDependency (O, R)
  • 1.8.6 hardware (O, R)
  • 1.8.6.1 hwName (M, NR)
  • 1.8.6.2 hwType (M, NR)
  • 1.8.6.3 hwOtherInformation (O, R)
  • 1.8.7 environmentExtension (O, R)

References

PREMIS Data Dictionary for Preservation Metadata, version 2.0, PREMIS Editorial Committee, March 2008

Caplan, Priscilla: Understanding PREMIS, February 2009

PREMIS not in DOMS (last edited 2010-09-24 06:58:00 by ek)