Users of descriptive metadata extension schemas should follow the appropriate guidelines recommended by the extension schemas' maintenance agencies. For example, users of the MODS schema should follow the MODS Users Guidelines published by the Library of Congress' Network Development and MARC Standards Office.
mets/fileSec/fileGrp/@USE
mets/fileSec/fileGrp/file/@USE
These are the supported values for <file> and <fileGrp> USE attributes in paged text objects conforming to this profile.
"archive image", "reference image" and "thumbnail image" are appropriate values to describe the USE of image content files. "archive image" should designate the image master; "thumbnail image" the image thumbnail; and "reference image" any intermediate resolutions intended for reference purposes.
"tei transcription" and "tei translation" are appropriate values to describe associated structured text files encoded according to TEI rules. "tei transcription" designates a direct TEI transcription of text based materials. "tei translation" designates a TEI translation of these materials from their original language.
"ocr" and "ocr dirty" should be used to designate versions of the text produced by ocr technologies. "ocr dirty" would be used to distinguish ocr text that is not suitable for presentation to the user from clean "ocr".
A given segment of the source material could be represented by more than one content file of a particular USE. For example, the page of a manuscript that has been digitized could be represented by an image master (USE="archive image"), a thumbnail image (USE="thumbnail image"), but two jpeg reference images of different resolutions (USE="reference image")
mets/structMap/@TYPE
These are the supported values for the <structMap> TYPE attribute in METS documents conforming to this profile.
"physical" designates a purely physical structure. For example, a book divided into page views.
"logical" designates a purely logical structure. For example, a book divided into chapters; or a diary divided into diary entries.
"mixed" designates a mixed structure. For example, a book divided into chapters, divided into page views.
The root <mets>element must include a LABEL attribute value.
The root <mets> element must include an OBJID attribute value that uniquely identifies the object in its owning repository.
Conforming METS documents may, but need not, contain a <metsHdr> element.
Conforming METS documents may, but need not, contain a one or more <dmdSec> elements. Each <dmdSec> may in turn contain a <dmdRef> or a <dmdWrap>
This profile establishes no requirements as to extension schemas that may be used to express descriptive metadata in the context of the dmdSec/mdWrap/xmlData element in conforming METS documents.
Conforming METS documents may or may not contain administrative metadata. Any of the supported <amdSec> child elements may appear: <techMD>, <sourceMD>,< rightsMD> and/or <digiprovMD>.
This profile establishes no requirements as to extension schemas that may be used to express administrative metadata in the context of any techMD/mdWrap/xmlData, sourceMD/mdWrap/xmlData, rightsMD/mdWrap/xmlData, or digiprovMD/mdWrap/xmlData elements appearing in an <amdSec> in a conforming METS documents.
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 might contain one <fileGrp> representing TIFF master images, one <fileGrp> representing high resolution JPEG reference images , one <fileGrp> representing medium resolution JPEG reference images, one <fileGrp> representing GIF thumbnail images, and one <fileGrp> representing TEI transcriptions. Each of these <fileGrp> elements may or may not contain subsidiary <fileGrp> elements representing subgroups of the content files.
Each <file> represented in the <fileSec> must have an associated USE attribute. The USE attribute may, however, be expressed at the <fileGrp> level, in which case it is taken to pertain to all <file> elements in the <fileGrp>. It may also, of course, be expressed at the <file> element level. Supported <file>/<fileGrp> USE attribute values appear in the <controlled_vocabularies> section of this document.
A conforming METS document must contain at least one <structMap>; it may, however, contain more than one <structMap>. There is no requirement as to <structMap> TYPE ("logical","physical", or "mixed").
A conforming <structMap> must contain a TYPE attribute. Supported TYPE values appear in the <controlled_vocabularies> section of this document ("logical","physical", or "mixed").
Each <div> must include a LABEL attribute value.
A <div> element may or may not directly contain <fptr> elements. (In other words, a <div> of the <structMap> may or may not have content files directly associated with it).
An <fptr> element must either 1) directly point to a <file> element via its FILEID attribute; or 2) contain an <area> element that points to a <file> element; or 3) contain a <seq> element comprising multiple <area> elements that point to the relevant <file> elements. METS documents implementing this profile must not use the <par> element. <structMap>s of "physical" and "mixed" TYPEs must not use either the <par> or <seq> elements.
An <fptr> element could directly contain an <area> element if only a portion of an integral file manifests the parent <div>. This is likely to occur in either of two cases. 1) This would typically be the case when the parent <div> element represented just a segment of the entire document and the <fptr> represented a tei transcription or a tei translation. In this case, the <area> element under the <fptr> would point to the <file> element representing the tei document (via its FILEID attribute) and must at least indicate the starting point of the the relevant section of the referenced tei file via the <area> BEGIN attribute. The BEGIN attribute, in this case, would have a BETYPE of "IDREF". The <area> element might also express the end point of the relevant section of the referenced file via its END attribute, but it need not do so. 2) When a <structMap> represents a logical structure, its individual <div> elements may each be manifested by only a portion of the associated image content files represented by its child <fptr> elements. In this case, an <fptr> element representing an image content file could, but need not, contain a <area> element which specified the shape and coordinates of the relevant section of the image via the <area> element's SHAPE and COORDS attribute values.
An <fptr> element would contain a <seq> element if multiple files needed to be"played" in sequence to manifest a division. This might be the case if the <structMap> expressed a logical structure and a <div> in that structure required several files to manifest it. For example, the <div> elements in the <structMap> for a diary might represent diary entries; and some of these entries might span multiple physical pages, and hence require multiple image content files to manifest them. In this case, the <div> representing the spanned diary entry would contain at least one <fptr>element; this <fptr> element would contain a <seq> element which in turn contained a separate <area> element pointing to each <file> element representing a page the diary entry spans. The <area> elements may include SHAPE and COORDS attribute values to identify the relevant sections of the associated image files, but they need not do so.
Each <fptr> element that does not contain subsidiary <area> or <seq> elements must point directly to a <file> element in the <fileSec> via its FILEID attributes. Similarly, each <area> element appearing under an <fptr> element or a <seq> element must point to directly to a <file> element via its FILEID attribute.
A conforming METS document may contain a <structLink> element. This profile, however, establishes no guidelines or expectations for its use.
A conforming METS document may contain a <behaviorSec> element. This profile, however, establishes no guidelines or expectations for its use.
This profile supports only image and text content files.
If there is image content, the image master (archive) files must be of TIFF format.
All "tei translation" and "tei transcription" 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).