DefiningImageAccess/Standard/PREMIS
From ImageWeb
| DefiningImageAccess/Standard/PREMIS | |
|---|---|
| Link:=http://www.oclc.org/research/projects/pmwg/}} | |
| Status:=Standard}} | |
| JISCProject:=False}} | |
| Focus:=Metadata for Preservation}} | |
| [[ReferencedBy::{{{ReferencedBy}}}]]}} | |
| [[PublishedBy::{{{PublishedBy}}}]]}} | |
| [[UsedBy::{{{UsedBy}}}]]}} | |
| [[DescribedBy::{{{DescribedBy}}}]]}} | |
| [[Partner::{{{Partner}}}]]}} | |
| [[Contact::{{{Contact}}}]]}} | |
PREMIS data dictionary for preservation metadata
- http://www.oclc.org/research/projects/pmwg/
- http://www.oclc.org/research/projects/pmwg/premis-final.pdf - PREMIS data dictionary for preservation metadata
- http://www.oclc.org/research/projects/pmwg/premis-report.pdf - PREMIS final report
| The Data Dictionary defines and describes an implementable set of core preservation metadata with broad applicability to digital preservation repositories. [The PREMIS Final Report] is intended to put the Data Dictionary into context, explain the underlying assumptions and data model, and provide additional information about the meaning and use of semantic units defined in the Data Dictionary. |
Comments
The PREMIS data dictionary is a heavyweight 237-page document. It contains:
- A data model covering the relationships between intellectual works, objects (digital representations), rights, events and agents. (I think there is some overlap here with CIDOC CRM, FRBR and INDECS.)
- Further notions of semantic units (which are value properties of an entity, which confusingly seem to be like OWL datatype properties), container and semantic components (echos of MPEG-21 DID, etc?).
- Several kinds of object, including file, bitstream (data within a file), representation (collection of files and metadata).
- The notion of representation is defined with particular reference to preservation: "For an intellectual entity to be displayed, played, or otherwise made useable to a human, all of the files making up at least one version of that intellectual entity must be identified, stored, and maintained so that they can be assembled and rendered to a user at any given point. A representation is the set of files required to do this." This notion is explicitly distinguished from FRBR's "manifestation".
The data dictionary itself, comprising about 80 pages of the total document, describes properties (semantic units) applicable to four kinds of entity:
- objects (about 85 semantic units, many of which are components of about 13 "top-level" semantic units). The top-level values are:
- objectIdentifier
- preservationLevel
- objectCategory
- objectCharacteristics
- creatingApplication
- originalName
- storage
- environment
- signatureInformation
- relationship
- linkingEventIdentifier
- linkingIntellectualEntityIdentifier
- linkingPermissionStatementIdentifier
- events (16 properties, 7 top-level):
- eventIdentifier
- eventType
- eventDateTime
- eventDetail
- eventOutcomeInformation
- linkingAgentIdentifier
- linkingObjectIdentifier
- agents (5 properties, 3 toop-level):
- agentIdentifier
- agentName
- agentType
- rights (16 properties, 1 top-level):
- permissionStatement
Examples account for another 90 pages of the document.
Remaining sections cover special topics (important aspects considered too detailed to include in the dictionary itself), methodology, implementation considerations and a glossary.
