All applications of the MODS schema in conforming METS documents should follow the MODS User Guidelines published by Library of Congress' Network Development and MARC Standards Office. (http://www.loc.gov/standards/mods/v3/mods-userguide.html).
mets/@TYPE
This profile specifies the required vocabulary for the TYPE attribute value on the root <mets> element. It is required that this attribute appear.
DMDSEC/MDWRAP/@MIMETYPE
This profile specifies the required vocabulary for the MIMETYPE attribute value on the <dmdSec:mdWrap> element. It is required that this attribute appear.
TECHMD/MDWRAP/@MDTYPE
TECHMD/MDWRAP/@OTHERMDTYPE
This profile specifies MDTYPE attribute value on the <techMD:mdWrap> element. If the MDTYPE="OTHER", then a value must be declared for OTHERMDTYPE from the listed attribute values.
mets/fileSec/fileGrp/@USE
These are the supported values for <fileGrp> USE attributes in METS documents implementing this profile. They are intended mainly to help presentation programs know how they should treat particular content files. In particular, they should help a presentation program distinguish between content files that are text or image based. They can also provide a presentation program with information that can help it or the end user decide what is the most appropriate content file for a particular purpose when this information is not apparent from the content file's MIME type. For example, the USE attribute can help identify TEI encoded files and to distinguish these from other structured text files. The individual USE attribute values are defined below.
"transcription" and "reference image" are appropriate values to describe the intended use of manuscript image and corresponding TEI transcription files encoded according to TEI rules that make up digital objects.
mets/structMap/div/@TYPE
These are the supported values for <structMap> div TYPE attributes in METS documents implementing this profile. They are intended mainly to help presentation programs know how they should treat particular content files. In particular, they should help a presentation program distinguish the relationship between manuscript pages.
"manuscript" is the appropriate value to describe the highest level div pointing to the manuscript digital object as a whole, and "page" is the appropriate value to describe the individual page references that constitute the manuscript digital object as a whole.
The root <mets> element must include an OBJID attribute value containing a valid Whitman Archive Manuscript Tracking Number and uniquely identifying the digital object represented by the METS document.
The root <mets> element requires a TYPE attribute value. This profile specifies only one vocabulary for the TYPE attribute: Manuscript.
The root <mets> element must include a PROFILE attribute value. mets_profile_MANUSCRIPT.xml is the current standard profile of reference for all Whitman Archive METS files for manuscript digital objects.
Conforming METS documents must contain a metsHdr element.
The <metsHdr> element must include the CREATEDATE attribute value. It must also include the LASTMODDATE attribute value if this does not coincide with the CREATEDATE.
The <metsHdr> element must include a child <agent> element identifying the person or institution responsible for creating the METS object. The <agent> element must include the ROLE attribute with the following possible values: CREATOR, EDITOR, [...].
Conforming METS documents must contain one or more <dmdSec> elements. Each <dmdSec> must contain an <mdWrap>
Conforming METS documents must contain a unique ID for each <dmdSec> (dmd1, dmd2, etc).
At least one version of any descriptive metadata appearing in <mdWrap> elements in a compliant document must conform to the MODS schema.
Each <mdWrap> element must contain the attributes ID, MDTYPE, and MIMETYPE. The ID attributes must reflect the MDTYPE in consecutive numerical order. If the MDTYPE attribute for the first mdWrap is, for example, MODS, then the ID attribute for that mdWrap section will be MODS1. If there are more than one MDTYPE="MODS" sections, then they should be numbered accordingly in the ID attribute (MODS1, MODS2, MODS3, etc.). The MIMETYPE attribute should conform to the controlled vocabulary contained within this profile and will in almost every circumstance be text/xml.
Conforming METS documents must contain only one <amdSec> element. This section must contain one or more of each of the following elements: <techMD>, <rightsMD>, and <sourceMD<.
Conforming METS documents for manuscripts must contain two <techMD> elements. One element provides technical metadata for the TEI transcription and the other for images. Each <techMD> element must contain a unique ID attribute value (tmd1, tmd2, etc).
Each <techMD> element must contain an <mdWrap> element and corresponding MDTYPE/OTHERMDTYPE attribute. The MDTYPE/OTHERMDTYPE attributes must conform to the controlled vocabulary contained within this profile. MDTYPE/OTHERMDTYPE attributes must describe the type of file as either text based (textMD) or image based (NISO MIX).
<techMD> elements pertaining to image content files must contain <xmlData> conforming to the MIX schema.
<techMD> elements pertaining to text content files must contain <xmlData> conforming to the textMD schema.
One <rightsMD< element must specify those rights declared for the thematic research collection. Additional <rightsMD< elements must specify those rights retained by the holding institution(s). Each must have a unique ID attribute value (rights1, rights2, and etc.).
<rightsMD> elements must contain <xmlData> conforming to the METS Rights schema.
Each <sourceMD< element must identify the repository location information for the original material represented by the digital object. A separate <sourceMD< element must identify the Whitman Archive as the repository location for the digital object. Each <sourceMD< element must include a unique ID attribute value (smd1, smd2, etc).
The <sourceMD< must include an <mdRef< element with the following attributes: LOCTYPE="URL", MDTYPE="EAD", xlink:href, and XPTR. These attributes point to the location of the corresponding descriptive metadata within the Whitman Archive and Holding Repository EAD files.
Conforming METS documents for this profile must contain a <fileSec>. The <fileSec> of a conforming METS document must contain a parent <fileGrp> for each file format/use represented by the content files. For example, the <fileSec> of a typical METS document implementing this profile will contain one <fileGrp> representing TEI Transcriptions and one <fileGrp> representing images. This profile does not support nested <fileGrp> elements.
Each <file> represented in the <fileSec> must have an associated USE attribute. The USE attribute can be expressed directly at the <file> element level. Alternately, the USE attribute may be expressed in conjunction with the <fileGrp> that is the immediate parent of a <file> element; in this case it is taken to pertain to all <file> elements in the <fileGrp>. The <file>/<fileGrp> USE attribute values must be drawn from the controlled vocaulary for <file>/<fileGrp> USE Attribute Values contained within this profile.
The <file> elements in a conforming METS document must contain ID and SIZE attribute values. They must also contain CREATED attribute values when available.
Each <file> represented in the <fileSec> must have an associated MIMETYPE attribute. This attribute must contain the official Internet Standard MIME type value for the content file represented
Each file must be associated with a <techMD> and a <rightsMD> element, either via reference from the parent <fileGrp> element ADMID attribute value or via reference from the <file> element ADMID attribute value.
Each <file> element must contain an <FLocat> element which specifies the external location of the content file in an xlink:href attribute.The <FLocat> element must contain an xlink:href attribute, as well as a LOCTYPE attribute indicating the type of href being provided. In most cases, the LOCTYPE for manuscript objects will be URL.
This profile supports the use of one and only one <FLocat> element in conjunction with each <file> element.
A conforming METS document must contain one and only one <structMap>. This <structMap> must not be empty.
A conforming <structMap> must contain a TYPE attribute. METS documents conforming to this profile will report the value MIXED for the type attribute.
Each <div> at the highest level must include a LABEL attribute value and a TYPE attribute value.The LABEL attribute should identify the content of the material for presentation to the end user. For example, for the highest level <div> the LABEL attribute value will be the title of the poem. The TYPE attribute value must conform with the controlled TYPE attribute vocabulary included in this profile.
A <div> element at the highest level must point to one or more pertinent <dmdSec> elements via its DMDID attribute value. However, the DMDID attribute should only reference ID values declared at the <dmdSec> element level, and not IDs at lower levels. For example, a <div> DMDID attribute should not reference the ID value of an element within the <xmlData> section of a <dmdSec>.
A <div> element at the highest level must include an ADMID attribute to point to corresponding sourceMD IDs pertinent to the content the <div> element represents (smd1, smd2, etc.). These sourceMD sections point to the external metadata describing that object.
A <div> element at the highest level must contain at least one or more <div> elements and one or more <fptr> elements. A <div> element at any level may contain one or more <div> and/or <fptr> elements. The <div> and <fptr> elements must be nested and labeled to represent the relationship between individual pieces that constitute the object. After the highest level <div> each subsequent <div> element must contain both TYPE and LABEL values. The TYPE value is always "page." The LABEL value indicates the order of pages (ie: "leaf 1 recto" and "leaf 1 verso").
Each <area> element must include the following attribute values to describe order and relationship between referenced IDs: BEGIN, END, and BETYPE.
All "tei" files must be encoded according to version 1 of the "TEI Text Encoding in Libraries: Guidelines for Best Encoding Practices" maintained by the Digital Library Federation (http://www.diglib.org/standards/tei.htm).
All files adhere to ISO-8859-1 character encoding standards maintained by the Internet Assigned Numbers Authority (http://www.iana.org/).
All files reference stylesheet "Whitman.xsl"
All files reference DTD "whitman.dtd"
All files adhere to current MODS schema maintained by the Library of Congress (http://www.loc.gov/standards/mods/v3/mods-3-1.xsd).
All files adhere to current NISO MIX standards maintained by the Library of Congress (http://www.loc.gov/standards/mix/mix.xsd).
All files adhere to current textMD standards maintained by New York University (http://dlib.nyu.edu/METS/text.xsd).
All files adhere to METSRights schema maintained by Stanford Univeristy (http://cosimo.stanford.edu/sdr/metsrights.xsd).