3.2Use of MODS file, mods.xml

The second file within Archival Information Package (AIP) will be the MODS file, named mods.xml. The MODS standard file will be coded using XML so that it does not depend on any other software package and its archives are robust. The MODS standard uses the English-language and provides ease of use by reducing the standard to smaller elements and reorganizing its components, frequently re-grouping them into more logical ones. (Maybe provide an example of such). Additionally, MODS provides granularity, meaning that it can be utilized to describe items as either whole or as sub-components. MODS allows for comprehensive cross-linking within a record, it allows for elements to be referenced externally. For instance a MODS file can be used as an extension schema to METS. The MODS file will be access by the METS (aip.xml) via a xlink:ref, which is a pointer that indicates the location of the MODS file. Therefore complex and comprehensive linking between MODS files and other XML based applications is supported within the MODS schema.

MODS file will be used to encode descriptive metadata. More specifically it will consist of information that describes, classifies, and characterizes the identity of the content. This information will be expressed within elements, sub-elements and their appropriate attributes, defined in the XML coded MODS schema. The elements, sub-elements, and attributes can be defined from their given names. The elements in MODS, just like in XML, are tags of descriptive keywords contained in a pair of angle brackets. Binding elements are subdivided into sub-elements with its own semantic scope, while other elements have no internal structure therefore essentially containing free text. The sub-elements are nested tags inside an element. The attributes are names and values contained in a pair of angle brackets, defined within an element or sub-element.

MODS top-level elements defined in the MODS schema are illustrated in Figure 3. As indicated in Figure 3, MODS mandatory, recommended, and optional elements can be either repeatable, R, or not repeatable, NR. The repeatable elements or sub-elements can be used more than once. The recommended and optional elements as well as the sub-elements are both based on the decision of the implementer to either omit or included the element. The recommended element or sub-element is an “if applicable” element. The mandatory elements or sub-elements must be provided. Figure 3

Although all MODS elements and sub-elements defined in the MODS schema will be considered valid in the FDsys generated mods.xml file. The FDsys will consider some MODS elements and sub-elements to be mandatory, that is, essential to the ingestion of the content to a repository. This document will only discuss the FDsys mandatory elements and sub-elements to access a complete detailed list of the elements and sub-elements defined in the MODS standard use the following link, The FDsys mandatory elements are the following: originInfo, language, identifier, location, physicalDescription, typeOfResource, recordInfo. The following are the FDsys mandatory sub-elements: publisher, dateIssued, dateCaptured, dateCreated, dateModified, dateValid, dateOther, languageTerm, and url. The elements and sub-elements will be described using the following format: element names and descriptions, sub-element names and descriptions, attributes names and descriptions, followed by examples that were provided from the FDsys sample data.

3.2.1originInfo

Element / Description
originInfo / information that pertains to the origin of the resource
Sub-element(s) / Description
publisher / name of entity
dateIssued / date published
Attribute(s) / Description
Encoding / refers to the W3C date time format that is being used, value is “w3cdtf”
dateCaptured / date resource was digitalized
dateCreated / date resource was created
dateModified / date resource was modified
dateValid / date the resource had valid content
dateOther / generic date element for other important information
Example:
<originInfo>
<publisher>U.S. Government Printing Office</publisher>
<dateIssued encoding="w3cdtf">2010-09-29</dateIssued>
<issuance>monographic</issuance>
</originInfo>

3.2.2language

Element / Description
language / language of the resource
Sub-element(s) / Description
languageTerm / a repeatable sub-element that details whether the language of the resource is in textual form or coded form.
Attribute(s) / Description
Type / can have a value of text, states the express language is in textual form or coded, states the express language is in coded form [is required]
Authority / values obtained from a controlled list [is required]
Example
<language>
<languageTerm type="code" authority="iso639 2b">eng</languageTerm>
</language>

3.2.3identifier

Element / Description
identifier / a unique number or code that identifies a resource
Attribute(s) / Description
type / indicates the type of identifier [is required]
Example
<identifier type="local">V0b002ee180b003e5</identifier>

3.2.4location

Element / Description
location / indicate the repository holding the resource or a URL where the resource is available
Sub-element(s) / Description
url / refers to the Uniform Resource Location for the resource [is required]
Attribute(s) / Description
displayLabel / provides information associated with the location
Access / indicates the type resource that will be accessed via the URL link
Example
<location xmlns:exslt="
<url displayLabel="HTML rendition" access="raw object">
<url displayLabel="PDF rendition" access="raw object">
<url displayLabel="XML rendition" access="raw object">
</location>

3.2.5physicalDescription

Element / Description
physicalDescription / physical description information of the resource
Sub-element(s) / Description
note / contains physical description that does not fall under any other sub-element [is recommended]
Attribute(s) / Description
Type / value of the physical description
digitalOrigin / describes the method used to achieve digital form of the resource [is required]
extent / describes the number of units that make up the resource [is recommended]
Example
<physicalDescription>
<note type="source contenttype">deposited</note>
<digitalOrigin>born digital</digitalOrigin>
<extent>7 p.</extent>
</physicalDescription>

3.2.6typeOfResource

Element / Description
typeOfResource / information describing the form of the resource
Example
<typeOfResource>text</typeOfResource>

3.2.7 recordInfo

Element / Description
recordInfo / contains information pertaining to the metadata
Sub-element / Description
languageOfCataloging / refers to the language of the text of the MODS record [is required]
Attribute(s) / Description
Type / can have a value of text, states the express language is in textual form or coded, states the express language is in coded form [is required]
Authority / values obtained from a controlled list [is required]
recordContentSource / information about the metadata of the original record such as who created it or modified it [is recommended]
Attribute(s) / Description
Authority / values obtained from a controlled list
recordOrigin / shows the origin of MODS record [is recommended]
recordCreationDate / the date the record was created [is optional]
Attribute(s) / Description
Encoding / refers to the W3C date time format that is being used, value is “w3cdtf”
recordChangeDate / the date the record was modified [is optional]
Attribute(s) / Description
Encoding / refers to the W3C date time format that is being used, value is “w3cdtf”
recordIdentifier / contains the organization and the system control number assigned to it [is optional]
Attribute(s) / Description
Source / refers to code or name of the institution whose system control number is located in the recordIdentifier
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>