descriptive metadata o when will mods.xml be used by mets (aip.xml) ? mets will use the mods.xml to...
Post on 22-Dec-2015
217 Views
Preview:
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">
<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>
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>
MODSMODS
o MODS elements considered mandatory are essential to the ingestion of the content to a repository: Those elements are the following:
• originInfo• language• identifier• location• physicalDescription• typeOfResource• recordInfo
o MODS elements considered mandatory are essential to the ingestion of the content to a repository: Those elements are the following:
• originInfo• language• identifier• location• physicalDescription• typeOfResource• recordInfo
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.
For example:<language>
<languageTerm type="code" authority="iso639 2b">eng</languageTerm>
</language>
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.
For example:<language>
<languageTerm type="code" authority="iso639 2b">eng</languageTerm>
</language>
IdentifierIdentifier
o identifier: a unique number or code that identifies a resource <type>: is a required attribute, that indicates the type
of identifier. For example, the value “local” refers to a local identifier.
For Example: <identifier type="local">V0b002ee180b003e5</identifier
o identifier: a unique number or code that identifies a resource <type>: is a required attribute, that indicates the type
of identifier. For example, the value “local” refers to a local identifier.
For Example: <identifier type="local">V0b002ee180b003e5</identifier
locationlocation
o location: indicate the repository holding the resource or a URL where the resource is available <url>: it is a mandatory sub-element that refers to
the Uniform Resource Location for the resource• <displayLabel>: is an attribute the provides information
associated with the location• <access>: is an attribute that indicates the type
resource that will be accessed via the URL link
o location: indicate the repository holding the resource or a URL where the resource is available <url>: it is a mandatory sub-element that refers to
the Uniform Resource Location for the resource• <displayLabel>: is an attribute the provides information
associated with the location• <access>: is an attribute that indicates the type
resource that will be accessed via the URL link
location examplelocation example For example:
<location xmlns:exslt="http://exslt.org/common"><url displayLabel="HTML rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/html/BILLS-111s3880is.htm</url> <url displayLabel="PDF rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/pdf/BILLS-111s3880is.pdf</url> <url displayLabel="XML rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/xml/BILLS-111s3880is.xml</url>
</location>
For example:<location xmlns:exslt="http://exslt.org/common">
<url displayLabel="HTML rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/html/BILLS-111s3880is.htm</url> <url displayLabel="PDF rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/pdf/BILLS-111s3880is.pdf</url> <url displayLabel="XML rendition" access="raw object">http://www.gpo.gov/fdsys/pkg/BILLS-111s3880is/xml/BILLS-111s3880is.xml</url>
</location>
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
For example:<physicalDescription>
<note type="source contenttype">deposited</note> <digitalOrigin>born digital</digitalOrigin><extent>7 p.</extent>
</physicalDescription>
For example:<physicalDescription>
<note type="source contenttype">deposited</note> <digitalOrigin>born digital</digitalOrigin><extent>7 p.</extent>
</physicalDescription>
typeOfResourcetypeOfResource
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
number assigned to it
recordInfo ExamplerecordInfo Example For example:
<recordInfo> <recordContentSource authority="marcorg">DGPO</recordContentSource><recordCreationDate encoding="w3cdtf">2010-10-06</recordCreationDate>
<recordChangeDate encoding="w3cdtf">2010-10-06</recordChangeDate <recordIdentifier source="DGPO">BILLS-111s3880is</recordIdentifier>
<recordOrigin>machine generated</recordOrigin> <languageOfCataloging> <languageTerm type="code" authority="iso639-2b">eng</languageTerm> </languageOfCataloging>
</recordInfo>
For example:<recordInfo>
<recordContentSource authority="marcorg">DGPO</recordContentSource><recordCreationDate encoding="w3cdtf">2010-10-06</recordCreationDate>
<recordChangeDate encoding="w3cdtf">2010-10-06</recordChangeDate <recordIdentifier source="DGPO">BILLS-111s3880is</recordIdentifier>
<recordOrigin>machine generated</recordOrigin> <languageOfCataloging> <languageTerm type="code" authority="iso639-2b">eng</languageTerm> </languageOfCataloging>
</recordInfo>
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:
<!-- PREMIS OBJECT --> <mets:amdSec ID="AMD_OTHER">
<mets:techMD ID="D09002ee180affcca-TEC"><mets:mdRef ID="M09002ee180affcca-tdiv" MDTYPE="PREMIS" MIMETYPE="text/xml" LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/premis.xml" />
</mets:techMD><mets:digiprovMD ID="D09002ee180affcca-DIG">
<mets:mdRef ID="M09002ee180affcca-ddiv" MDTYPE="PREMIS" MIMETYPE="text/xml" LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/premis.xml" />
</mets:digiprovMD></mets:amdSec>
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:
<!-- PREMIS OBJECT --> <mets:amdSec ID="AMD_OTHER">
<mets:techMD ID="D09002ee180affcca-TEC"><mets:mdRef ID="M09002ee180affcca-tdiv" MDTYPE="PREMIS" MIMETYPE="text/xml" LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/premis.xml" />
</mets:techMD><mets:digiprovMD ID="D09002ee180affcca-DIG">
<mets:mdRef ID="M09002ee180affcca-ddiv" MDTYPE="PREMIS" MIMETYPE="text/xml" LOCTYPE="URL" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="file:/premis.xml" />
</mets:digiprovMD></mets:amdSec>
PREMIS Data ModelPREMIS Data Model
PREMIS Intellectual EntityPREMIS Intellectual Entity
• 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:
<object xsi:type="representation"><objectIdentifier>
<objectIdentifierType>FDsys ACP</objectIdentifierType><objectIdentifierValue>R0b002ee180b003b0</objectIdentifierValue></objectIdentifier>
</object>
For example:<object xsi:type="representation">
<objectIdentifier><objectIdentifierType>FDsys ACP</objectIdentifierType>
<objectIdentifierValue>R0b002ee180b003b0</objectIdentifierValue></objectIdentifier>
</object>
objectCharacteristicsobjectCharacteristics
o objectCharacteristics: refers to the technical properties of a file <compositeLevel>: indicates if the object is
subject to one or more processes of decoding or unbundling under
<fixity>: used to verify if an object has been changed in an undocumented or unauthorized way under
<size>: the size of the object <format>: the format information of the object
o objectCharacteristics: refers to the technical properties of a file <compositeLevel>: indicates if the object is
subject to one or more processes of decoding or unbundling under
<fixity>: used to verify if an object has been changed in an undocumented or unauthorized way under
<size>: the size of the object <format>: the format information of the object
objectCharacteristics ExampleobjectCharacteristics Example<objectCharacteristics> <compositionLevel>0</compositionLevel> <fixity> <messageDigestAlgorithm>SHA-256</messageDigestAlgorithm>
<messageDigest>4977070b92f0bb2642c6be368ad68a8d1d1c5dbbb3310544db781f56a860b0a1</messageDigest> <messageDigestOriginator>FDsys</messageDigestOriginator> </fixity> <size>9326</size> <format> <formatDesignation> <formatName>text/plain</formatName> </formatDesignation>
<formatRegistry> <formatRegistryName>PRONOM</formatRegistryName> <formatRegistryKey>x-fmt/111</formatRegistryKey> </formatRegistry> <formatNote>Plain Text File</formatNote> </format> </objectCharacteristics>
<objectCharacteristics> <compositionLevel>0</compositionLevel> <fixity> <messageDigestAlgorithm>SHA-256</messageDigestAlgorithm>
<messageDigest>4977070b92f0bb2642c6be368ad68a8d1d1c5dbbb3310544db781f56a860b0a1</messageDigest> <messageDigestOriginator>FDsys</messageDigestOriginator> </fixity> <size>9326</size> <format> <formatDesignation> <formatName>text/plain</formatName> </formatDesignation>
<formatRegistry> <formatRegistryName>PRONOM</formatRegistryName> <formatRegistryKey>x-fmt/111</formatRegistryKey> </formatRegistry> <formatNote>Plain Text File</formatNote> </format> </objectCharacteristics>
storagestorage
o storage: information about where and how a files are stored in the repository <contentLocation>: information needed to
retrieve a file from a storage system. <contentLocationType>: refers to the way of accessing
the location of the content. <contentLocationValue>: refers to the “location of the
content used by the storage system” <storageMedium>: The medium on which an
object is stored
o storage: information about where and how a files are stored in the repository <contentLocation>: information needed to
retrieve a file from a storage system. <contentLocationType>: refers to the way of accessing
the location of the content. <contentLocationValue>: refers to the “location of the
content used by the storage system” <storageMedium>: The medium on which an
object is stored
storage Examplestorage Example
<storage><contentLocation>
<contentLocationType>URI</contentLocationType> <contentLocationValue>file:/u02/app/emc/
documentum /data/fdsysprod1/fdsysprod1/content_storage_01/00002 ee1/80/55/b0/48.txt</contentLocationValue>
</contentLocation> <storageMedium>hard disk</storageMedium> </storage>
<storage><contentLocation>
<contentLocationType>URI</contentLocationType> <contentLocationValue>file:/u02/app/emc/
documentum /data/fdsysprod1/fdsysprod1/content_storage_01/00002 ee1/80/55/b0/48.txt</contentLocationValue>
</contentLocation> <storageMedium>hard disk</storageMedium> </storage>
PREMIS Event EntityPREMIS Event Entity
• 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
P0b002ee180b003af</eventDetail> <eventOutcomeInformation>
<eventOutcome>Success</eventOutcome> </eventOutcomeInformation>
<linkingAgentIdentifier> <linkingAgentIdentifierType>FDsys:agent</linkingAgentIdentifierType> <linkingAgentIdentifierValue>hotfolderadmin</linkingAgentIdentifierValue> <linkingAgentRole>implementer</linkingAgentRole> </linkingAgentIdentifier>
<linkingObjectIdentifier> <linkingObjectIdentifierType>FDsys</linkingObjectIdentifierType> <linkingObjectIdentifierValue>R0b002ee180b003b0</linkingObjectIdentifierValue> <linkingObjectRole>outcome</linkingObjectRole> </linkingObjectIdentifier></event>
<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
P0b002ee180b003af</eventDetail> <eventOutcomeInformation>
<eventOutcome>Success</eventOutcome> </eventOutcomeInformation>
<linkingAgentIdentifier> <linkingAgentIdentifierType>FDsys:agent</linkingAgentIdentifierType> <linkingAgentIdentifierValue>hotfolderadmin</linkingAgentIdentifierValue> <linkingAgentRole>implementer</linkingAgentRole> </linkingAgentIdentifier>
<linkingObjectIdentifier> <linkingObjectIdentifierType>FDsys</linkingObjectIdentifierType> <linkingObjectIdentifierValue>R0b002ee180b003b0</linkingObjectIdentifierValue> <linkingObjectRole>outcome</linkingObjectRole> </linkingObjectIdentifier></event>
PREMIS Agent EntityPREMIS Agent Entity
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,
organization, or software)
PREMIS Agent ExamplePREMIS Agent Example<agent>
<agentIdentifier> <agentIdentifierType>FDsys:agent</agentIdentifierType> <agentIdentifierValue>hotfolderadmin</agentIdentifierValue> </agentIdentifier> <agentName>hotfolderadmin</agentName> <agentType>Person</agentType> </agent>
<agent><agentIdentifier>
<agentIdentifierType>FDsys:agent</agentIdentifierType> <agentIdentifierValue>hotfolderadmin</agentIdentifierValue> </agentIdentifier> <agentName>hotfolderadmin</agentName> <agentType>Person</agentType> </agent>
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
https://wiki.dlib.indiana.edu/download/attachments/24288/DLFMODS_ImplementationGuidelines.pdf
o Fdsys Requirements Document http://www.gpo.gov/pdfs/fdsys-info/documents/FDsys_RD_v2.1.pdf
o MODS User Guidelines http://www.loc.gov/standards/mods/userguide/
o MODS: Uses and Features http://www.loc.gov/standards/mods/mods-overview.html
o Understanding PREMIS http://www.loc.gov/standards/premis/understanding-premis.pdf
o W3C Schools http://www.w3schools.com/xml/default.asp
o Data Dictionary for Preservation Metadata http://www.oclc.org/research/activities/past/orprojects/pmwg/premis-final.pdf
o Digital Library Federation/Acquifer Implementation Guidelines for Shareable MODS Records https://wiki.dlib.indiana.edu/download/attachments/24288/
DLFMODS_ImplementationGuidelines.pdfo Fdsys Requirements Document
http://www.gpo.gov/pdfs/fdsys-info/documents/FDsys_RD_v2.1.pdfo MODS User Guidelines
http://www.loc.gov/standards/mods/userguide/o MODS: Uses and Features
http://www.loc.gov/standards/mods/mods-overview.htmlo Understanding PREMIS
http://www.loc.gov/standards/premis/understanding-premis.pdfo W3C Schools
http://www.w3schools.com/xml/default.asp
top related