Descriptive Metadata o When will mods.xml be used by METS (aip.xml) ? METS will use the mods.xml to encode descriptive metadata. • Information that describes, classifies, and characterizes the identity of the content. o How will METS (aip.xml) access MODS (mods.xml)? METS uses a pointer to the metadata that is located outside of the METS document. More specifically, it uses a xlink:href to indicate the location of mods file. o For example: <!-- MODS object --> <mets:dmdSec ID="DMD_OTHER"> <mets:mdRef ID="D09002ee180b004da" MDTYPE="MODS" MIMETYPE="text/xml" LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/mods.xml" /> </mets:dmdSec>
35
Embed
Descriptive Metadata o When will mods.xml be used by METS (aip.xml) ? METS will use the mods.xml to encode descriptive metadata. Information that describes,
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Descriptive MetadataDescriptive Metadatao When will mods.xml be used by METS (aip.xml) ?
METS will use the mods.xml to encode descriptive metadata.• Information that describes, classifies, and characterizes the identity of the
content.o How will METS (aip.xml) access MODS (mods.xml)?
METS uses a pointer to the metadata that is located outside of the METS document. More specifically, it uses a xlink:href to indicate the location of mods file.
o For example:<!-- MODS object --> <mets:dmdSec ID="DMD_OTHER">
originInfooriginInfoo originInfo: Information that pertains to the origin of the resource
Recommended If Applicable sub-elements of <originInfo>• <publisher>: name of entity • <dateIssued>: date published
Optional sub-element• <issuance>: informs how the resource was issued
For example:
<originInfo><publisher>U.S. Government Printing Office</publisher><dateIssued encoding="w3cdtf">2010-09-29</dateIssued><issuance>monographic</issuance>
</originInfo>
o originInfo: Information that pertains to the origin of the resource Recommended If Applicable sub-elements of <originInfo>
• <publisher>: name of entity • <dateIssued>: date published
Optional sub-element• <issuance>: informs how the resource was issued
For example:
<originInfo><publisher>U.S. Government Printing Office</publisher><dateIssued encoding="w3cdtf">2010-09-29</dateIssued><issuance>monographic</issuance>
</originInfo>
languagelanguage
o language: of the resource Required sub-elements • <languageTerm>: is a repeatable sub-element that
details whether the language of the resource is in textual form or coded form.
physicalDescriptionphysicalDescriptiono physicalDescription: contains all sub-elements
that relate to the physical description information of the resource <note>: is a recommended if applicable sub-element,
contains physical description that does not fall under any other sub-element.
<digitalOrigin>: is a required sub-element, that describes the method use to achieve digital form of the resource
<extent>: is a recommended if applicable sub-element, describes the number of units that make up the resource
o physicalDescription: contains all sub-elements that relate to the physical description information of the resource <note>: is a recommended if applicable sub-element,
contains physical description that does not fall under any other sub-element.
<digitalOrigin>: is a required sub-element, that describes the method use to achieve digital form of the resource
<extent>: is a recommended if applicable sub-element, describes the number of units that make up the resource
physicalDescription ExamplephysicalDescription Example
o typeOfResource: information describing the form of the resource
o For example:<typeOfResource>text</typeOfResource>
o typeOfResource: information describing the form of the resource
o For example:<typeOfResource>text</typeOfResource>
recordInforecordInfoo recordInfo: contains information pertain metadata
Required sub-elements• <languageOfCataloging>: refers to the language of the text of the
MODS recordo <languageTerm>: required attribute, refers to the language of the metadata
reocrd
Recommended sub-elements• <recordContentSource>: information about the metadata of the
original record such as who created it or modified it • <recordOrigin>: shows the origin of MODS record
Optional sub-elements• <recordCreationDate>: the date the record was created• <recordChangeDate>: the date the record was modified• <recordIdentifier>: contains the organization and the system control
number assigned to it
o recordInfo: contains information pertain metadata Required sub-elements
• <languageOfCataloging>: refers to the language of the text of the MODS recordo <languageTerm>: required attribute, refers to the language of the metadata
reocrd
Recommended sub-elements• <recordContentSource>: information about the metadata of the
original record such as who created it or modified it • <recordOrigin>: shows the origin of MODS record
Optional sub-elements• <recordCreationDate>: the date the record was created• <recordChangeDate>: the date the record was modified• <recordIdentifier>: contains the organization and the system control
Preservation MetadataPreservation Metadatao When will premis.xml be used by METS (aip.xml) ?
METS will use the premis.xml to encode preservation metadata.• “information a repository uses to support the digital preservation
process”• Which includes information such as:
o Provenance – refers to who has ownership of the digital objecto Authenticity – refers to the claim of the digital objecto Preservation activity – refers to the activities that have been carried
out to preserve the digital objecto Technical environment – refers to the tasks required to interpret and
use the digital object o Rights management – refers the intellectual property rights that
must be declared
o When will premis.xml be used by METS (aip.xml) ? METS will use the premis.xml to encode preservation metadata.
• “information a repository uses to support the digital preservation process”
• Which includes information such as:o Provenance – refers to who has ownership of the digital objecto Authenticity – refers to the claim of the digital objecto Preservation activity – refers to the activities that have been carried
out to preserve the digital objecto Technical environment – refers to the tasks required to interpret and
use the digital object o Rights management – refers the intellectual property rights that
must be declared
Preservation MetadataPreservation Metadata
o How will METS (aip.xml) access PREMIS (premis.xml)? METS uses a pointer to the metadata that is located outside of the METS document.
More specifically, it uses a xlink:href to indicate the location of mods file. Example code from aip.xml:
• Intellectual Entity – refer to content that can be describe as a unit (e.g. books, maps, articles)
• Intellectual Entity – refer to content that can be describe as a unit (e.g. books, maps, articles)
PREMIS Object EntityPREMIS Object Entity
• Objects – refer to units of information in digital form. PREMIS defines different kinds of objects it can an a file, bitstream or representationo File – it is a computer file, such as a pdf, txt or JPEG o Bitstream – refer to data bits within a file that
contain common properties for preservation purposes
• Objects – refer to units of information in digital form. PREMIS defines different kinds of objects it can an a file, bitstream or representationo File – it is a computer file, such as a pdf, txt or JPEG o Bitstream – refer to data bits within a file that
contain common properties for preservation purposes
PREMIS Object EntityPREMIS Object Entity
o Representation – refer to a set of files, that includes structural metadata, required to be identified, stored and maintained in order to assemble a complete rendition of an Intellectual unit. For example, text files and images files of a magazine
are required to form a representation.
o Representation – refer to a set of files, that includes structural metadata, required to be identified, stored and maintained in order to assemble a complete rendition of an Intellectual unit. For example, text files and images files of a magazine
are required to form a representation.
PREMIS Object EntityPREMIS Object Entity
o PREMIS Data Dictionary defines the mandatory semantic units (elements) of object entity Those elements are the following:• objectIdentifier *• objectCategory• objectCharacteristics * • format *• storage *
* Indicates repeatable semantic unit
o PREMIS Data Dictionary defines the mandatory semantic units (elements) of object entity Those elements are the following:• objectIdentifier *• objectCategory• objectCharacteristics * • format *• storage *
* Indicates repeatable semantic unit
objectIdentifierobjectIdentifier
o objectIdentifier: refers to the unique identifier of the object <objectIdentifierType>: refers to the classification
of the domain that creates the object identifier. <objectIdentifierValue>: value of the object
identifier.
o objectIdentifier: refers to the unique identifier of the object <objectIdentifierType>: refers to the classification
of the domain that creates the object identifier. <objectIdentifierValue>: value of the object
identifier.
objectIdentifier ExampleobjectIdentifier Example For example:
• Events – refers to actions that involve an object and an agent known to the systemo Events are critical for maintaining the digital provenance of an
object (helps demonstrates the authenticity of the object)• Examples of Events:
o modifying an documento actions that create new relationships
Object could be related to another object as a result of a particular event, for instance if a program takes file 1 and generates a different version known as file 2
o Actions that check the validity and integrity of the objects (i.e. virus scan)
• Events – refers to actions that involve an object and an agent known to the systemo Events are critical for maintaining the digital provenance of an
object (helps demonstrates the authenticity of the object)• Examples of Events:
o modifying an documento actions that create new relationships
Object could be related to another object as a result of a particular event, for instance if a program takes file 1 and generates a different version known as file 2
o Actions that check the validity and integrity of the objects (i.e. virus scan)
PREMIS Event EntityPREMIS Event Entity
o PREMIS Data Dictionary defines the mandatory semantic units (elements) of event entity Those elements are the following:• eventIdentifier• eventType• eventDateTime
o PREMIS Data Dictionary defines the mandatory semantic units (elements) of event entity Those elements are the following:• eventIdentifier• eventType• eventDateTime
Event EntityEvent Entityo <eventIdentifier>: unique identifier for the event
<eventIdentifierType>: refers to the classification of the domain that creates the event identifier.
<eventIdentifierValue>: value of the event identifier.o <eventType>: classifies the nature of the event.o <eventDataTime>: date, time and type of evento <eventDetail>: detail description of the evento <eventOctomeInformation>: the outcome of the
evento <eventOutcome>: indicates if the event was a
success, partial success, or failure.
o <eventIdentifier>: unique identifier for the event <eventIdentifierType>: refers to the classification of
the domain that creates the event identifier. <eventIdentifierValue>: value of the event identifier.
o <eventType>: classifies the nature of the event.o <eventDataTime>: date, time and type of evento <eventDetail>: detail description of the evento <eventOctomeInformation>: the outcome of the
evento <eventOutcome>: indicates if the event was a
success, partial success, or failure.
Event EntityEvent Entityo <linkingAgentIdentifier>: agents involved in the event and their specific roles;
Agents role are defined here because agents can perform different roles in different eventso <linkingAgentIdentifierType>: refers to the classification of the domain
that creates the linking agent identifier. o <linkingAgentIdentifierValue>: “value of the linking agent identifier”. o <linkingAgentRole> indicates the role of the agent associated to the event.
o <linkingObjectIdentifier>: Objects involved in the event and their specific roles o <linkingObjectIdentifierType>: refers to the classification of the domain
that creates the linking object identifier. o <linkingObjectIdentifierValue>: “value of the linking object identifier”. o <linkingObjectRole> indicates the role of the object associated to the
event.
o <linkingAgentIdentifier>: agents involved in the event and their specific roles; Agents role are defined here because agents can perform different roles in different eventso <linkingAgentIdentifierType>: refers to the classification of the domain
that creates the linking agent identifier. o <linkingAgentIdentifierValue>: “value of the linking agent identifier”. o <linkingAgentRole> indicates the role of the agent associated to the event.
o <linkingObjectIdentifier>: Objects involved in the event and their specific roles o <linkingObjectIdentifierType>: refers to the classification of the domain
that creates the linking object identifier. o <linkingObjectIdentifierValue>: “value of the linking object identifier”. o <linkingObjectRole> indicates the role of the object associated to the
event.
PREMIS Event ExamplePREMIS Event Example<event>
<eventIdentifier> <eventIdentifierType>FDsys:event</eventIdentifierType> <eventIdentifierValue>1cdd2b6c-5a2d-449b-b386-ebb15eb4af11</eventIdentifierValue> </eventIdentifier> <eventType>Rendition Submitted</eventType> <eventDateTime>2010-10-06T19:38:47-04:00</eventDateTime> <eventDetail>Rendition R0b002ee180b003b0, uploaded by hotfolderadmin, was submitted in the Submission Information package
<eventIdentifierType>FDsys:event</eventIdentifierType> <eventIdentifierValue>1cdd2b6c-5a2d-449b-b386-ebb15eb4af11</eventIdentifierValue> </eventIdentifier> <eventType>Rendition Submitted</eventType> <eventDateTime>2010-10-06T19:38:47-04:00</eventDateTime> <eventDetail>Rendition R0b002ee180b003b0, uploaded by hotfolderadmin, was submitted in the Submission Information package
o Agents – refer to people, organizations, or software associated with events, more specifically preservation events, of an object In the data model diagram, there is no arrow from
Agent entity to the Object entity, that is because Agents influence Objects indirectly through Events.
o Agents – refer to people, organizations, or software associated with events, more specifically preservation events, of an object In the data model diagram, there is no arrow from
Agent entity to the Object entity, that is because Agents influence Objects indirectly through Events.
PREMIS Agent EntityPREMIS Agent Entity
o PREMIS Data Dictionary defines the mandatory semantic unit (element) of agent entity That element is the following:• <agentIdentifier>: is a repeatable semantic unit
o PREMIS Data Dictionary defines the mandatory semantic unit (element) of agent entity That element is the following:• <agentIdentifier>: is a repeatable semantic unit
Agent EntityAgent Entity
o agentIdentifier: unique identifier for the agent <agentIdentifierType>: refers to the classification
of the domain that creates the agent identifier. <agentIdentifierValue>: “value of the agent
identifier”o <agentName>: the agent’s name o <agentType>: the type of agent (people,
organization, or software)
o agentIdentifier: unique identifier for the agent <agentIdentifierType>: refers to the classification
of the domain that creates the agent identifier. <agentIdentifierValue>: “value of the agent
identifier”o <agentName>: the agent’s name o <agentType>: the type of agent (people,
ReferencesReferenceso Data Dictionary for Preservation Metadata
http://www.oclc.org/research/activities/past/orprojects/pmwg/premis-final.pdfo Digital Library Federation/Acquifer Implementation Guidelines for Shareable MODS Records