|
Size: 6914
Comment:
|
← Revision 54 as of 2010-09-24 06:58:00 ⇥
Size: 4270
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == PREMIS in DOMS == | ## page was renamed from PREMIS in DOMS == PREMIS not in DOMS == |
| Line 3: | Line 4: |
| '''''[under construction]''''' | ''We have decided not to use PREMIS in DOMS, at least when it comes to audio files we have digitized via the Quadriga system. That is due to the fact that all the needed technical metadata are automatically generated or manually written in the Quadriga system. And those metadata will be exported to DOMS together with the audio file.'' |
| Line 5: | Line 6: |
| 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. | ''Below are the investigations we made in order to find out which components from PREMIS we would use for digital resources without automatically generated technical metadata'' |
| Line 7: | Line 8: |
| 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]'' | 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. |
| Line 10: | Line 11: |
| * '''2. Object entities''' are what are actually stores and managed in the preservation repository | * '''2. Object entities''' are what are actually stored and managed in the preservation repository |
| Line 15: | Line 16: |
| We have chosen to use only one of the entities '''Object (or Digital Object)'''. Objects are what are actually stored and managed in the preservation repository. Most of PREMIS is devoted to describing digital objects. The information that can be recorded includes: * a unique identifier for the object (type and value), * fixity information such as a checksum (message digest) and the algorithm used to derive it, * the size of the object, * the format of the object, which can be specified directly or by linking to a format registry, * the original name of the object, * information about its creation, * information about inhibitors, * information about its significant properties, * information about its environment (see below), * where and on what medium it is stored, * digital signature information, * relationships with other objects and other types of entities. '''Object Entity Semantic Units''' |
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: |
| Line 36: | Line 23: |
| 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.4 significantProperties (O, R) 1.4.1 significantPropertiesType (O, NR) 1.4.2 significantPropertiesValue (O, NR) 1.4.3 significantPropertiesExtension (O, R) 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.6 inhibitors (O, R) [file, bitstream] 1.5.6.1 inhibitorType (M, NR) [file, bitstream] 1.5.6.2 inhibitorTarget (O, R) [file, bitstream] 1.5.6.3 inhibitorKey (O, NR) [file, bitstream] 1.5.7 objectCharacteristicsExtension (O, R) [file, bitstream 1.6 originalName (O, NR) [representation, file] 1.7 storage (M, R) [file, bitstream] 1.7.1 contentLocation (O, NR) [file, bitstream] 1.7.1.1 contentLocationType (M, NR) [file, bitstream] 1.7.1.2 contentLocationValue (M, NR) [file, bitstream] 1.7.2 storageMedium (O, NR) [file, bitstream] 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) 1.9 signatureInformation (O, R) [file, bitstream] 1.9.1 signature (O, R) 1.9.1.1 signatureEncoding (M, NR) [file, bitstream] 1.9.1.2 signer (O, NR) [file, bitstream] 1.9.1.3 signatureMethod (M, NR) [file, bitstream] 1.9.1.4 signatureValue (M, NR) [file, bitstream] 1.9.1.5 signatureValidationRules (M, NR) [file, bitstream] 1.9.1.6 signatureProperties (O, R) [file, bitstream] 1.9.1.7 keyInformation (O, NR) [file, bitstream] 1.9.2 signatureInformationExtension (O, R) [file, bitstream] 1.10 relationship (O, R) 1.10.1 relationshipType (M, NR) 1.10.2 relationshipSubType (M, NR) 1.10.3 relatedObjectIdentification (M, R) 1.10.3.1 relatedObjectIdentifierType (M, NR) 1.10.3.2 relatedObjectIdentifierValue (M, NR) 1.10.3.3 relatedObjectSequence (O, NR) 1.10.4 relatedEventIdentification (O, R) 1.10.4.1 relatedEventIdentifierType (M, NR) 1.10.4.2 relatedEventIdentifierValue (M, NR) 1.10.4.3 relatedEventSequence (O, NR) 1.11 linkingEventIdentifier (O, R) 1.11.1 linkingEventIdentifierType (M, NR) 1.11.2 linkingEventIdentifierValue (M, NR) 1.12 linkingIntellectualEntityIdentifier (O, R) 1.12.1 linkingIntellectualEntityIdentifierType (M, NR) 1.12.2 linkingIntellectualEntityIdentifierValue (M, NR) 1.13 linkingRightsStatementIdentifier (O, R) 1.13.1 linkingRightsStatementIdentifierType (M, NR) 1.13.2 linkingRightsStatementIdentifierValue (M, NR) |
* 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) |
PREMIS not in DOMS
We have decided not to use PREMIS in DOMS, at least when it comes to audio files we have digitized via the Quadriga system. That is due to the fact that all the needed technical metadata are automatically generated or manually written in the Quadriga system. And those metadata will be exported to DOMS together with the audio file.
Below are the investigations we made in order to find out which components from PREMIS we would use for digital resources without automatically generated technical metadata
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.
1. Intellectual entities are conceptual and might be called "bibliographic entities".
2. Object entities are what are actually stored 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