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: 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 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

originInfo o originInfo: Information that pertains to the origin of the resource  Recommended If Applicable sub-elements of : name of entity : date published  Optional sub-element : informs how the resource was issued  For example: U.S. Government Printing Office monographic o originInfo: Information that pertains to the origin of the resource  Recommended If Applicable sub-elements of : name of entity : date published  Optional sub-element : informs how the resource was issued  For example: U.S. Government Printing Office monographic

language o language: of the resource  Required sub-elements : is a repeatable sub-element that details whether the language of the resource is in textual form or coded form.  For example: eng o language: of the resource  Required sub-elements : is a repeatable sub-element that details whether the language of the resource is in textual form or coded form.  For example: eng

Identifier o identifier: a unique number or code that identifies a resource  : is a required attribute, that indicates the type of identifier. For example, the value “local” refers to a local identifier.  For Example: V0b002ee180b003e5</identifier o identifier: a unique number or code that identifies a resource  : is a required attribute, that indicates the type of identifier. For example, the value “local” refers to a local identifier.  For Example: V0b002ee180b003e5</identifier

location o location: indicate the repository holding the resource or a URL where the resource is available  : it is a mandatory sub-element that refers to the Uniform Resource Location for the resource : is an attribute the provides information associated with the location : 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  : it is a mandatory sub-element that refers to the Uniform Resource Location for the resource : is an attribute the provides information associated with the location : is an attribute that indicates the type resource that will be accessed via the URL link

location example  For example: 111s3880is/html/BILLS-111s3880is.htm 111s3880is/pdf/BILLS-111s3880is.pdf 111s3880is/xml/BILLS-111s3880is.xml  For example: 111s3880is/html/BILLS-111s3880is.htm 111s3880is/pdf/BILLS-111s3880is.pdf 111s3880is/xml/BILLS-111s3880is.xml

physicalDescription o physicalDescription: contains all sub-elements that relate to the physical description information of the resource  : is a recommended if applicable sub-element, contains physical description that does not fall under any other sub-element.  : is a required sub-element, that describes the method use to achieve digital form of the resource  : 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  : is a recommended if applicable sub-element, contains physical description that does not fall under any other sub-element.  : is a required sub-element, that describes the method use to achieve digital form of the resource  : is a recommended if applicable sub- element, describes the number of units that make up the resource

physicalDescription Example  For example: deposited born digital 7 p.  For example: deposited born digital 7 p.

typeOfResource o typeOfResource: information describing the form of the resource o For example: text o typeOfResource: information describing the form of the resource o For example: text

recordInfo o recordInfo: contains information pertain metadata  Required sub-elements : refers to the language of the text of the MODS record o : required attribute, refers to the language of the metadata reocrd  Recommended sub-elements : information about the metadata of the original record such as who created it or modified it : shows the origin of MODS record  Optional sub-elements : the date the record was created : the date the record was modified : contains the organization and the system control number assigned to it o recordInfo: contains information pertain metadata  Required sub-elements : refers to the language of the text of the MODS record o : required attribute, refers to the language of the metadata reocrd  Recommended sub-elements : information about the metadata of the original record such as who created it or modified it : shows the origin of MODS record  Optional sub-elements : the date the record was created : the date the record was modified : contains the organization and the system control number assigned to it

recordInfo Example  For example: DGPO </recordChangeDate BILLS-111s3880is machine generated eng  For example: DGPO </recordChangeDate BILLS-111s3880is machine generated eng

Preservation Metadata 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 object o Authenticity – refers to the claim of the digital object o Preservation activity – refers to the activities that have been carried out to preserve the digital object o 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 object o Authenticity – refers to the claim of the digital object o Preservation activity – refers to the activities that have been carried out to preserve the digital object o 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 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: 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 Data Model

PREMIS Intellectual Entity Intellectual Entity – refer to content that can be describe as a unit (e.g. books, maps, articles)

PREMIS Object Entity Objects – refer to units of information in digital form. PREMIS defines different kinds of objects it can an a file, bitstream or representation o 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 representation o 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 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 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

objectIdentifier o objectIdentifier: refers to the unique identifier of the object  : refers to the classification of the domain that creates the object identifier.  : value of the object identifier. o objectIdentifier: refers to the unique identifier of the object  : refers to the classification of the domain that creates the object identifier.  : value of the object identifier.

objectIdentifier Example  For example: FDsys ACP R0b002ee180b003b0  For example: FDsys ACP R0b002ee180b003b0

objectCharacteristics o objectCharacteristics: refers to the technical properties of a file  : indicates if the object is subject to one or more processes of decoding or unbundling under  : used to verify if an object has been changed in an undocumented or unauthorized way under  : the size of the object  : the format information of the object o objectCharacteristics: refers to the technical properties of a file  : indicates if the object is subject to one or more processes of decoding or unbundling under  : used to verify if an object has been changed in an undocumented or unauthorized way under  : the size of the object  : the format information of the object

objectCharacteristics Example 0 SHA b92f0bb2642c6be368ad68a8d1d1c5dbbb db781f56a860b0a1 FDsys 9326 text/plain PRONOM x-fmt/111 Plain Text File 0 SHA b92f0bb2642c6be368ad68a8d1d1c5dbbb db781f56a860b0a1 FDsys 9326 text/plain PRONOM x-fmt/111 Plain Text File

storage o storage: information about where and how a files are stored in the repository  : information needed to retrieve a file from a storage system.  : refers to the way of accessing the location of the content.  : refers to the “location of the content used by the storage system”  : The medium on which an object is stored o storage: information about where and how a files are stored in the repository  : information needed to retrieve a file from a storage system.  : refers to the way of accessing the location of the content.  : refers to the “location of the content used by the storage system”  : The medium on which an object is stored

storage Example URI file:/u02/app/emc/documentum /data/fdsysprod1/fdsysprod1/content_storage_01/00002 ee1/80/55/b0/48.txt hard disk URI file:/u02/app/emc/documentum /data/fdsysprod1/fdsysprod1/content_storage_01/00002 ee1/80/55/b0/48.txt hard disk

PREMIS Event Entity Events – refers to actions that involve an object and an agent known to the system o Events are critical for maintaining the digital provenance of an object (helps demonstrates the authenticity of the object) Examples of Events: o modifying an document o 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 system o Events are critical for maintaining the digital provenance of an object (helps demonstrates the authenticity of the object) Examples of Events: o modifying an document o 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 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 Entity o : unique identifier for the event  : refers to the classification of the domain that creates the event identifier.  : value of the event identifier. o : classifies the nature of the event. o : date, time and type of event o : detail description of the event o : the outcome of the event o : indicates if the event was a success, partial success, or failure. o : unique identifier for the event  : refers to the classification of the domain that creates the event identifier.  : value of the event identifier. o : classifies the nature of the event. o : date, time and type of event o : detail description of the event o : the outcome of the event o : indicates if the event was a success, partial success, or failure.

Event Entity o : agents involved in the event and their specific roles; Agents role are defined here because agents can perform different roles in different events o : refers to the classification of the domain that creates the linking agent identifier. o : “value of the linking agent identifier”. o indicates the role of the agent associated to the event. o : Objects involved in the event and their specific roles o : refers to the classification of the domain that creates the linking object identifier. o : “value of the linking object identifier”. o indicates the role of the object associated to the event. o : agents involved in the event and their specific roles; Agents role are defined here because agents can perform different roles in different events o : refers to the classification of the domain that creates the linking agent identifier. o : “value of the linking agent identifier”. o indicates the role of the agent associated to the event. o : Objects involved in the event and their specific roles o : refers to the classification of the domain that creates the linking object identifier. o : “value of the linking object identifier”. o indicates the role of the object associated to the event.

PREMIS Event Example FDsys:event 1cdd2b6c-5a2d-449b-b386-ebb15eb4af11 Rendition Submitted T19:38:47-04:00 Rendition R0b002ee180b003b0, uploaded by hotfolderadmin, was submitted in the Submission Information package P0b002ee180b003af Success FDsys:agent hotfolderadmin implementer FDsys R0b002ee180b003b0 outcome FDsys:event 1cdd2b6c-5a2d-449b-b386-ebb15eb4af11 Rendition Submitted T19:38:47-04:00 Rendition R0b002ee180b003b0, uploaded by hotfolderadmin, was submitted in the Submission Information package P0b002ee180b003af Success FDsys:agent hotfolderadmin implementer FDsys R0b002ee180b003b0 outcome

PREMIS 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 Entity o PREMIS Data Dictionary defines the mandatory semantic unit (element) of agent entity  That element is the following: : is a repeatable semantic unit o PREMIS Data Dictionary defines the mandatory semantic unit (element) of agent entity  That element is the following: : is a repeatable semantic unit

Agent Entity o agentIdentifier: unique identifier for the agent  : refers to the classification of the domain that creates the agent identifier.  : “value of the agent identifier” o : the agent’s name o : the type of agent (people, organization, or software) o agentIdentifier: unique identifier for the agent  : refers to the classification of the domain that creates the agent identifier.  : “value of the agent identifier” o : the agent’s name o : the type of agent (people, organization, or software)

PREMIS Agent Example FDsys:agent hotfolderadmin hotfolderadmin Person FDsys:agent hotfolderadmin hotfolderadmin Person

References o Data Dictionary for Preservation Metadata  o Digital Library Federation/Acquifer Implementation Guidelines for Shareable MODS Records  Guidelines.pdf Guidelines.pdf o Fdsys Requirements Document  o MODS User Guidelines  o MODS: Uses and Features  o Understanding PREMIS  o W3C Schools  o Data Dictionary for Preservation Metadata  o Digital Library Federation/Acquifer Implementation Guidelines for Shareable MODS Records  Guidelines.pdf Guidelines.pdf o Fdsys Requirements Document  o MODS User Guidelines  o MODS: Uses and Features  o Understanding PREMIS  o W3C Schools 