Skip Navigation Links The Library of Congress >> Standards
Metadata Encoding and Transmission Standard (METS) Official Web Site
METS_Profile: @xsi:schemaLocation="http://www.loc.gov/METS_Profile/ http://www.loc.gov/standards/mets/profile_docs/mets.profile.v1-2.xsd"
title:
UCB General METS Profile Version 1
abstract:
The UC Berkeley Library uses this profile to govern METS instance documents intended for submission to the California Digital Library as well as METS documents intended for reference use and dissemination to end users through UCB's own digital library repository. The digital content governed by the METS documents conforming to this profile may be of any type or combination of types including, but not limited to: images, tei-based structured text, ocr-based unstructured text, pdf documents, ps documents, quicktime video, and Real audio. Source materials whose METS encoded digital versions would be covered by this profile could include manuscripts (such as letters and diaries), printed materials (such as books, pamphlets, and technical reports), mixed content materials (such as scrapbooks, photoalbums and oral histories that include photographs and/or sound recordings), individual photographs, paintings, sculptures, etc. This profile also covers born-digital materials intended for general reference use. It at once extends, and for UC Berkeley Library purposes, completely supersedes the UCB Paged Text Object Profile and the UCB Imaged Object Profile. However, it is not in all respects backwards compatible with these profiles.
date:
2006-08-29T00:00:00
contact:
name:
Rick Beaubien
address:
88 Herrada Rd., Santa Fe, NM, 87508-8890
phone:
(505) 466-6630
email:
rbeaubie@library.berkeley.edu
related_profile: @RELATIONSHIP="supersedes" @URI="http://www.loc.gov/mets/profiles/00000003.xml"
UCB Paged Text Object Profile
related_profile: @RELATIONSHIP="supersedes" @URI="http://www.loc.gov/mets/profiles/00000002.xml"
UCB Imaged Object Profile
extension_schema: @ID="ext1"
name:
MODS
context:
mets/dmdSec/mdWrap/xmlData
note:
While the schema referenced above represents v.3.1 of MODS, all v.3.x MODS schemas are largely backwards compatible with previous incremental releases of version 3. METS documents using any version 3 MODS schema are accommodated by this profile.
extension_schema: @ID="ext2"
name:
NISOIMG
context:
mets/amdSec/techMD/mdWrap/xmlData
note:
Used for technical metadata about image content files.This profile supports both the existing version 1 of the schema as well as version 2 as soon as this becomes available.
extension_schema: @ID="ext3"
name:
textmd
context:
mets/amdSec/techMD/mdWrap/xmlData
note:
Used for technical metadata about text content files.
extension_schema: @ID="ext4"
name:
METSRights
context:
mets/amdSec/rightsMD/mdWrap/xmlData
note:
The CopyrightMD schema (see below) is the preferred schema for rights once this schema has been finalized. But the METSRights schema is included to accommodate METS documents prepared before the CopyrightMD schema and associated implementation support is complete.
extension_schema: @ID="ext5"
name:
CopyrightMD
context:
mets/amdSec/rightsMD/mdWrap/xmlData
note:
This will be the preferred schema for rights metadata in UCB METS documents as soon as it has been finalized.
extension_schema: @ID="ext6"
name:
PREMIS
context:
This schema may be used in either or both of the following contexts: mets/amdSec/sourceMD/mdWrap/xmlData and/or mets/amdSec/digiprovMD/mdWrap/xmlData
note:
This profile neither requires nor constrains the use of the PREMIS schemas in the METS documents that implement it. It is, however, supported in particular for the PREMIS object schema's ability to the track complex relationships between source and target content files. For example, PREMIS could be used to record the derivation of a Quicktime video from multiple still images files.
description_rules:

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). In addition, all conforming objects destined for the California Digital Library should follow the provisions for descriptive metadata set forth in CDL's Guidelines for Digital Objects: http://www.cdlib.org/inside/diglib/guidelines/

controlled_vocabularies:
vocabulary: @ID="vc1"
name:
CDL <mets> TYPE attribute values
maintenance_agency:
California Digital Library, Office of the President, University of Califorina
context:

mets/@TYPE

description:

This profile specifies no required vocabulary for the TYPE attribute value on the root <mets> element, nor does it require that this attribute appear. However, the California Digital Library maintains a list of values used by its presentation programs to control the default display format for the objects it ingests into the CDL repository. METS documents destined for the California Digital Library, and conforming to this profile, may specify one of these TYPE values to insure desired treatment in the CDL repository.

vocabulary: @ID="vc2"
name:
UC Berkeley Library METS <file>/<fileGrp> USE Attribute Values
maintenance_agency:
Library Systems Office, The General Library, University of California, Berkeley
values:
value:
image/master
value:
image/reference
value:
image/thumbnail
value:
image/dynamic
value:
text/tei
value:
text/tei element
value:
text/ocr
value:
text/reference
value:
application
value:
video/master
value:
video/reference
value:
audio/master
value:
audio/reference
context:

mets/fileSec/fileGrp/@USE

mets/fileSec/fileGrp/file/@USE

description:

These are the supported values for <file> and <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 intended for reference use and those that served as masters, but which are not intended for reference purposes. 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. They allow presentation programs to recognize files with a MIME type of "text/plain" which represent "dirty" OCR. The individual USE attribute values are defined below

"image/master", "image/reference", "image/thumbnail" and "image/dynamic" are appropriate values to describe the intended use of image content files from a presentation program's standpoint. The value "image/master" designates image master files (ultimate or intermediate) not intended for reference use. The appropriate USE values for any image that is intended for reference use, even if it also serves master image for other derivatives, would be "image/reference", "image/thumbnail" or "image/dynamic". The value "image/thumbnail" designates images intended for thumbnail applications; the value "image/dynamic"designates still images such as mrsid and jpeg2000 images which allow for zooming and other dynamic capabilities; and the more general value "image/reference" designates all other types of still image content files which are intended for general reference use

"text/tei" and "text/tei element" are the appropriate values to describe associated structured text files encoded according to TEI rules. "text/tei element" applies when a <file> element represents just an element within an integral TEI content file. In this case, the xlink:href value in the <FLocat> element would use XPointer syntax to qualify the file URL and specify the ID attribute value of the relevant element in the TEI file. "text/tei" applies to all <file> elements that represent integral TEI content files.

"text/ocr" designates versions of the text produced by ocr technologies, but which have not been cleaned, and hence may not be appropriate for some purposes. "text/reference" designates unstructured text, including clean ocr, which is appropriate for reference and presentation purposes.

"application" designates all types of non-video and non-audio content files encoded in a proprietary format requiring special browser plugins or players for presentation to the user. This is the appropriate USE attribute value for "pdf" and "ps" content files .

Audio content files are represented by two USE values: "audio/master" for audio master or archive files not intended for general reference use; and "audio/reference" for audio files suitable for general reference use.

Video content files are also represented by two USE values: "video/master"; for video master or archive files not intended for general reference use; and "video/reference" for video files suitable for general reference use

structural_requirements:
metsRootElement:
requirement: @ID="metsRoot1"

The root <mets>element must include a LABEL attribute value.

requirement: @ID="metsRoot2"

The root <mets> element must include an OBJID attribute value containing a valid ark and uniquely identifying the object represented by the METS document in its owning repository.

requirement: @ID="metsRoot3" @RELATEDMAT="vc1"

The root <mets> element may, but need not include a TYPE attribute. This profile does not specify a vocabulary for the TYPE attribute. However METS documents conforming to this profile that are destined for CDL should use the CDL <mets> TYPE attribute value vocabulary if they do include a TYPE attribute value at the <mets> level. If they do not include a <mets> TYPE attribute value, then the CDL ingest programs will assign one by default.

CDL <mets> TYPE attribute values California Digital Library, Office of the President, University of Califorina http://www.cdlib.org/inside/diglib/guidelines/ mets/@TYPE This profile specifies no required vocabulary for the TYPE attribute value on the root <mets> element, nor does it require that this attribute appear. However, the California Digital Library maintains a list of values used by its presentation programs to control the default display format for the objects it ingests into the CDL repository. METS documents destined for the California Digital Library, and conforming to this profile, may specify one of these TYPE values to insure desired treatment in the CDL repository.
metsHdr:
requirement: @ID="metsHdr1"

Conforming METS documents must contain a metsHdr element.

requirement: @ID="metsHdr2"

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.

requirement:

The <metsHdr> element must include a child <agent> element identifying the person or institution responsible for creating the METS object.

dmdSec:
requirement: @ID="dmdSec1"

Conforming METS documents may, but need not, contain a one or more <dmdSec> elements. Each <dmdSec> may in turn contain a <mdRef> or a <mdWrap>

requirement: @ID="dmdSec2" @RELATEDMAT="ext1"

At least one version of any descriptive metadata appearing in <mdWrap> elements in a compliant document must conform to the MODS schema. Secondary versions of descriptive metadata analogous to a primary MODS version may appear, but must conform to a descriptive metadata schema endorsed by the METS Editorial Board.

MODS http://www.loc.gov/standards/mods/v3/mods-3-1.xsd mets/dmdSec/mdWrap/xmlData While the schema referenced above represents v.3.1 of MODS, all v.3.x MODS schemas are largely backwards compatible with previous incremental releases of version 3. METS documents using any version 3 MODS schema are accommodated by this profile.
amdSec:
requirement: @ID="amdSec1"

Conforming METS documents may, but need not, contain an <amdSec> element. This may but need not contain one or more <techMD> elements, <sourceMD> elements, <digiprovMD> elements and/or <rightsMD> elements. METS documents conforming to this profile that are destined for CDL should conform to the GDO requirements with respect to administrative metadata.

requirement: @ID="amdSec2"

A conforming METS document will contain no more than one <amdSec> element. All <techMD>, <sourceMD>, <rightsMD> and <digiprovMD> elements must appear in this single <amdSec> element.

requirement: @ID="amdSec3" @RELATEDMAT="ext2"

If one or more <techMD> elements pertaining to image content files are present, they must contain <xmlData> of NISOIMG type conforming to the MIX schema.

NISOIMG http://www.loc.gov/standards/mix/mix.xsd mets/amdSec/techMD/mdWrap/xmlData Used for technical metadata about image content files.This profile supports both the existing version 1 of the schema as well as version 2 as soon as this becomes available.
requirement: @ID="amdSec4" @RELATEDMAT="ext3"

If one or more <techMD> elements pertaining to text content files are present, they must contain <xmlData> conforming to the textmd schema.

textmd http://dlib.nyu.edu/METS/textmd.xsd mets/amdSec/techMD/mdWrap/xmlData Used for technical metadata about text content files.
requirement: @ID="amdSec5"

If one or more <techMD> elements pertaining to application content files are present, they should contain <xmlData> conforming to METS Editorial Board endorsed schemas, once such schemas exist.

requirement: @ID="amdSec6" @RELATEDMAT="ext4 ext5"

If one or more <rightsMD> elements are present they must contain <xmlData> conforming to the CopyrightMD schema, once this schema has been finalized. Any <rightsMD> elements in objects produced prior to the completion of the CopyrightMD schema must contain <xmlData> conforming to the RightsDeclarationMD (METSRights) schema.

requirement: @ID="amdSec7" @RELATEDMAT="ext6"

Any <sourceMD> or <digiprovMD> elements must contain <xmlData> conforming to PREMIS or another METS Editorial Board endorsed schema whenever such a schema exists and covers the requisite concepts.

PREMIS http://www.loc.gov/standards/premis/v1/PREMIS-v1-1.xsd This schema may be used in either or both of the following contexts: mets/amdSec/sourceMD/mdWrap/xmlData and/or mets/amdSec/digiprovMD/mdWrap/xmlData This profile neither requires nor constrains the use of the PREMIS schemas in the METS documents that implement it. It is, however, supported in particular for the PREMIS object schema's ability to the track complex relationships between source and target content files. For example, PREMIS could be used to record the derivation of a Quicktime video from multiple still images files.
requirement: @ID="amdSec8" @RELATEDMAT="ext2"

Source metadata pertaining to image content files may be expressed as part of any MIX encoded technical metadata in <techMD> elements rather than in separate <sourceMD> elements. This might occur whenever the available source metadata is minimal and covered by the MIX schema.

NISOIMG http://www.loc.gov/standards/mix/mix.xsd mets/amdSec/techMD/mdWrap/xmlData Used for technical metadata about image content files.This profile supports both the existing version 1 of the schema as well as version 2 as soon as this becomes available.
requirement: @ID="amdSec9" @RELATEDMAT="ext6"

Complex relationships between source and content files, such as those between the rotational still images comprising a Quicktime video and the Quicktime video itself may be expressed via the PREMIS Object schema. Complex source relationships such as these should be recorded in a <sourceMD> element.

PREMIS http://www.loc.gov/standards/premis/v1/PREMIS-v1-1.xsd This schema may be used in either or both of the following contexts: mets/amdSec/sourceMD/mdWrap/xmlData and/or mets/amdSec/digiprovMD/mdWrap/xmlData This profile neither requires nor constrains the use of the PREMIS schemas in the METS documents that implement it. It is, however, supported in particular for the PREMIS object schema's ability to the track complex relationships between source and target content files. For example, PREMIS could be used to record the derivation of a Quicktime video from multiple still images files.
fileSec:
requirement: @ID="fileSec1"

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. This profile does not support nested <fileGrp> elements.

requirement: @ID="fileSec2" @RELATEDMAT="vc2"

Each <file> represented in the <fileSec> must have an associated USE attribute. The USE attribute may be expressed directly at the <file> element level. Alternately, however, 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 UC Berkeley Library METS <file>/<fileGrp> USE Attribute Values

UC Berkeley Library METS <file>/<fileGrp> USE Attribute Values Library Systems Office, The General Library, University of California, Berkeley image/master image/reference image/thumbnail image/dynamic text/tei text/tei element text/ocr text/reference application video/master video/reference audio/master audio/reference mets/fileSec/fileGrp/@USE mets/fileSec/fileGrp/file/@USE These are the supported values for <file> and <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 intended for reference use and those that served as masters, but which are not intended for reference purposes. 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. They allow presentation programs to recognize files with a MIME type of "text/plain" which represent "dirty" OCR. The individual USE attribute values are defined below "image/master", "image/reference", "image/thumbnail" and "image/dynamic" are appropriate values to describe the intended use of image content files from a presentation program's standpoint. The value "image/master" designates image master files (ultimate or intermediate) not intended for reference use. The appropriate USE values for any image that is intended for reference use, even if it also serves master image for other derivatives, would be "image/reference", "image/thumbnail" or "image/dynamic". The value "image/thumbnail" designates images intended for thumbnail applications; the value "image/dynamic"designates still images such as mrsid and jpeg2000 images which allow for zooming and other dynamic capabilities; and the more general value "image/reference" designates all other types of still image content files which are intended for general reference use "text/tei" and "text/tei element" are the appropriate values to describe associated structured text files encoded according to TEI rules. "text/tei element" applies when a <file> element represents just an element within an integral TEI content file. In this case, the xlink:href value in the <FLocat> element would use XPointer syntax to qualify the file URL and specify the ID attribute value of the relevant element in the TEI file. "text/tei" applies to all <file> elements that represent integral TEI content files. "text/ocr" designates versions of the text produced by ocr technologies, but which have not been cleaned, and hence may not be appropriate for some purposes. "text/reference" designates unstructured text, including clean ocr, which is appropriate for reference and presentation purposes. "application" designates all types of non-video and non-audio content files encoded in a proprietary format requiring special browser plugins or players for presentation to the user. This is the appropriate USE attribute value for "pdf" and "ps" content files . Audio content files are represented by two USE values: "audio/master" for audio master or archive files not intended for general reference use; and "audio/reference" for audio files suitable for general reference use. Video content files are also represented by two USE values: "video/master"; for video master or archive files not intended for general reference use; and "video/reference" for video files suitable for general reference use
requirement: @ID="fileSec3"

Each <file> represented in the <fileSec> must have an associated MIMETYPE attribute. This attribute must contain the official MIME type value for the content file represented

requirement: @ID="fileSec4"

The <file> elements in a conforming METS document may, but need not contain ADMID, SEQ, SIZE, CREATED, CHECKSUM, CHECKSUMTYPE, OWNERID or GROUPID attribute values.

requirement: @ID="fileSec5"

Any <file> element may reference any number of pertinent <techMD>, <sourceMD> and <digiprovMD> metadata elements within the <amdSec> via its AMDID attribute value. It should only reference ID values at the <techMD>, <sourceMD> and/or <digiprovMD> levels of the <amdSec>.

requirement: @ID="fileSec6" @RELATEDMAT="structMap5"

<file> elements should not reference the IDs of <rightsMD> elements in their ADMID attributes. Under this profile it is the responsibility of the <div> elements in the <structMap> to reference the <rightsMD> elements that pertain the content the <div> elements represent.

A <div> element at any level may use its ADMID attribute to point to a <rightsMD> element that contains the rights metadata pertinent to the content the <div> element represents. In this case, the indicated rights metadata applies to the <div> that references it as well as all of its descendant <div> elements which do not themselves contain an ADMID reference to a different <rightsMD> element.
requirement: @ID="fileSec7"

If the <file> element SEQ attribute is used, it should appear in every <file> element and express the ordinal number corresponding to the <file> element's sequence in its immediate <fileGrp>.

requirement: @ID="fileSec8"

If the <file> element GROUPID attribute is used, it should appear in every <file> element. The GROUPID of <file> elements that represent different manifestations of the same content should have the same GROUPID value.

requirement: @ID="fileSec9" @RELATEDMAT="structMap4"

This profile does not support the use of the DMDID attribute in <file> elements. Under this profile it is the responsibility of the <div> elements in the <structMap> to reference the <dmdSec> elements that pertain the content the <div> elements represent. Content file level descriptive metadata is not supported.

A <div> element at any level may 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>.
requirement: @ID="fileSec10"

Each <file> element must contain an <FLocat> element which specifies external location of the content file in its 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. It may, but need not contain, any of the other attributes defined in xlink:simpleLink as well as a CONTENTIDS attribute. No guidelines are provided, however, for the use of these attributes.

requirement: @ID="fileSec11" @RELATEDMAT="vc2"

In cases where the content represented by a <mets> document includes just a selected element or elements from an XML encoded structured text file conforming to the TEI schema, then the xlink:href attribute in the <FLocat> element may use XPointer syntax to isolate the relevant section (or element) of the integral TEI document. For example, the <FLocat> element for a TEI file might look like this in the case where "Part1" was the ID value associated with the relevant element of the TEI file represented by the <file> element: <mets:FLocat xlink:href="http://digitalassets.lib.berkeley.edu/ disabilityrights/text/kawauchi1.xml#Part1" LOCTYPE="URL" />. This handling is an alternative to the more standard practice of using the <area> element in conjunction with an <fptr> element in the <structMap> to isolate a portion of an integral file. This profile does not require this alternative handling; but METS documents conforming to this profile that are destined for the California Digital Library should follow the current GDO guidelines in this matter. Note that when a <file> element references just an element within a TEI file as described here, the file USE attribute must be "text/tei element"

UC Berkeley Library METS <file>/<fileGrp> USE Attribute Values Library Systems Office, The General Library, University of California, Berkeley image/master image/reference image/thumbnail image/dynamic text/tei text/tei element text/ocr text/reference application video/master video/reference audio/master audio/reference mets/fileSec/fileGrp/@USE mets/fileSec/fileGrp/file/@USE These are the supported values for <file> and <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 intended for reference use and those that served as masters, but which are not intended for reference purposes. 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. They allow presentation programs to recognize files with a MIME type of "text/plain" which represent "dirty" OCR. The individual USE attribute values are defined below "image/master", "image/reference", "image/thumbnail" and "image/dynamic" are appropriate values to describe the intended use of image content files from a presentation program's standpoint. The value "image/master" designates image master files (ultimate or intermediate) not intended for reference use. The appropriate USE values for any image that is intended for reference use, even if it also serves master image for other derivatives, would be "image/reference", "image/thumbnail" or "image/dynamic". The value "image/thumbnail" designates images intended for thumbnail applications; the value "image/dynamic"designates still images such as mrsid and jpeg2000 images which allow for zooming and other dynamic capabilities; and the more general value "image/reference" designates all other types of still image content files which are intended for general reference use "text/tei" and "text/tei element" are the appropriate values to describe associated structured text files encoded according to TEI rules. "text/tei element" applies when a <file> element represents just an element within an integral TEI content file. In this case, the xlink:href value in the <FLocat> element would use XPointer syntax to qualify the file URL and specify the ID attribute value of the relevant element in the TEI file. "text/tei" applies to all <file> elements that represent integral TEI content files. "text/ocr" designates versions of the text produced by ocr technologies, but which have not been cleaned, and hence may not be appropriate for some purposes. "text/reference" designates unstructured text, including clean ocr, which is appropriate for reference and presentation purposes. "application" designates all types of non-video and non-audio content files encoded in a proprietary format requiring special browser plugins or players for presentation to the user. This is the appropriate USE attribute value for "pdf" and "ps" content files . Audio content files are represented by two USE values: "audio/master" for audio master or archive files not intended for general reference use; and "audio/reference" for audio files suitable for general reference use. Video content files are also represented by two USE values: "video/master"; for video master or archive files not intended for general reference use; and "video/reference" for video files suitable for general reference use
requirement: @ID="fileSec12"

This profile supports the use of one and only one <FLocat> element in conjunction with each <file> element

requirement: @ID="fileSec13"

This profile does not support the use of the <FContent>, <stream>, or <transformFile> elements.

requirement: @ID="fileSec14"

In the case of Real audio content, only the actual Real audio content files (the .rm files) should be represented in the <fileSec> and referenced via <fptr> and <area> elements in the <structMap>. This profile assumes that any necessary launch file (e.g, an .ram file) will be generated dynamically by the presentation applications.

structMap:
requirement: @ID="structMap1"

A conforming METS document must contain only one <structMap>. This <structMap> must not be empty.

requirement: @ID="structMap2" @RELATEDMAT="vc2"

A conforming <structMap> may, but need not, contain a TYPE attribute. This profile does not specify a vocabulary for this attribute nor make any assumptions about its application.

UC Berkeley Library METS <file>/<fileGrp> USE Attribute Values Library Systems Office, The General Library, University of California, Berkeley image/master image/reference image/thumbnail image/dynamic text/tei text/tei element text/ocr text/reference application video/master video/reference audio/master audio/reference mets/fileSec/fileGrp/@USE mets/fileSec/fileGrp/file/@USE These are the supported values for <file> and <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 intended for reference use and those that served as masters, but which are not intended for reference purposes. 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. They allow presentation programs to recognize files with a MIME type of "text/plain" which represent "dirty" OCR. The individual USE attribute values are defined below "image/master", "image/reference", "image/thumbnail" and "image/dynamic" are appropriate values to describe the intended use of image content files from a presentation program's standpoint. The value "image/master" designates image master files (ultimate or intermediate) not intended for reference use. The appropriate USE values for any image that is intended for reference use, even if it also serves master image for other derivatives, would be "image/reference", "image/thumbnail" or "image/dynamic". The value "image/thumbnail" designates images intended for thumbnail applications; the value "image/dynamic"designates still images such as mrsid and jpeg2000 images which allow for zooming and other dynamic capabilities; and the more general value "image/reference" designates all other types of still image content files which are intended for general reference use "text/tei" and "text/tei element" are the appropriate values to describe associated structured text files encoded according to TEI rules. "text/tei element" applies when a <file> element represents just an element within an integral TEI content file. In this case, the xlink:href value in the <FLocat> element would use XPointer syntax to qualify the file URL and specify the ID attribute value of the relevant element in the TEI file. "text/tei" applies to all <file> elements that represent integral TEI content files. "text/ocr" designates versions of the text produced by ocr technologies, but which have not been cleaned, and hence may not be appropriate for some purposes. "text/reference" designates unstructured text, including clean ocr, which is appropriate for reference and presentation purposes. "application" designates all types of non-video and non-audio content files encoded in a proprietary format requiring special browser plugins or players for presentation to the user. This is the appropriate USE attribute value for "pdf" and "ps" content files . Audio content files are represented by two USE values: "audio/master" for audio master or archive files not intended for general reference use; and "audio/reference" for audio files suitable for general reference use. Video content files are also represented by two USE values: "video/master"; for video master or archive files not intended for general reference use; and "video/reference" for video files suitable for general reference use
requirement: @ID="structMap3"

Each <div> must include a LABEL attribute value and a TYPE attribute value.The LABEL attribute should identify the the division in a manner suitable for presentation to the end user in an associated "table of contents" and that will facilitate user navigation. While there is no controlled vocabulary list dictated for the TYPE attribute, the TYPE attributes for <div> elements representing the physical levels of the structure of the original source material should, whenever possible, contain a common generic designation for the physical level represented. For example, "page", "detail", "recto", "verso", etc.

requirement: @ID="structMap4"

A <div> element at any level may 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>.

requirement: @ID="structMap5"

A <div> element at any level may use its ADMID attribute to point to a <rightsMD> element that contains the rights metadata pertinent to the content the <div> element represents. In this case, the indicated rights metadata applies to the <div> that references it as well as all of its descendant <div> elements which do not themselves contain an ADMID reference to a different <rightsMD> element.

requirement: @ID="structMap6"

A <div> element may, but need not, include ORDER, ORDERLABEL, CONTENTIDS, and/or xlink:label attribute values. This profile dictates no guidelines or rules for the use of these <div> attributes.

requirement: @ID="structMap7"

A <div> element at any level may itself contain one or more <div> elements, one or more <fptr> elements, or a single <mptr> element. A <div> element may contain both <div> elements and <fptr> elements; the <mptr> element, however, may not occur in combination with any other elements including another <mptr> element under the parent <div>.

requirement: @ID="structMap8"

<fptr> elements that reference images representing different manifestions (resolutions) of the same content must appear consecutively under the <div> to which they pertain. Any <fptr> elements referencing <file> elements whose USE is "image/thumbnail" must be arranged together in order of increasing size; and any <fptr> elements referencing <file> elements whose USE is "image/reference" must also also be arranged together in order by size.

requirement: @ID="structMap9"

The <mptr> element, if it is used, must contain an xlink:href attribute, as well as a LOCTYPE attribute indicating the type of href being provided. It may, but need not contain, any of the other attributes defined in the xlink:simpleLink attribute group as well as a CONTENTIDS attribute. No guidelines are provided, however, for the use of these attributes.

requirement: @ID="structMap10" @RELATEDMAT="structMap11"

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. Typically the <seq> element would only be used under a <div> element that represented an intellectual (or logical) division, such as a diary entry. In this case, more than one content file, played in sequence, may be required to manifest the logical division.

An <fptr> element could directly contain an <area> element if only a portion of an integral file manifested the parent <div>. This profile supports such use of the <area> element in conjunction with structured text, audio and video content only and as follows. 1) Structured text content. If an <fptr> element represents just a portion of an integral structured text file (such as a TEI file), an <area> element under the <fptr> would point to the <file> element representing the integral structured text document (via its FILEID attribute) and would at least indicate the starting point of the relevant section of the content 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) Audio and video content. If an <fptr> element represents just a segment of an integral audio or video content file, then the <area> element under the <fptr> should point to the <file> element representing the integral audio or video file (via its FILEID attribute) and must indicate the starting point and duration of the relevant section of the referenced audio or video file via the <area> BEGIN and EXTENT attributes. The BETYPE and EXTTYPE attributes in these cases must be "TIME" and the BEGIN and EXTENT attributes must contain a simple time value in the format HH:MM:SS. If the relevant extent from the specified BEGIN point is the remainder of the audio or video file, then the EXTENT and EXTTYPE atributes may be omitted.
requirement: @ID="structMap11"

An <fptr> element could directly contain an <area> element if only a portion of an integral file manifested the parent <div>. This profile supports such use of the <area> element in conjunction with structured text, audio and video content only and as follows. 1) Structured text content. If an <fptr> element represents just a portion of an integral structured text file (such as a TEI file), an <area> element under the <fptr> would point to the <file> element representing the integral structured text document (via its FILEID attribute) and would at least indicate the starting point of the relevant section of the content 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) Audio and video content. If an <fptr> element represents just a segment of an integral audio or video content file, then the <area> element under the <fptr> should point to the <file> element representing the integral audio or video file (via its FILEID attribute) and must indicate the starting point and duration of the relevant section of the referenced audio or video file via the <area> BEGIN and EXTENT attributes. The BETYPE and EXTTYPE attributes in these cases must be "TIME" and the BEGIN and EXTENT attributes must contain a simple time value in the format HH:MM:SS. If the relevant extent from the specified BEGIN point is the remainder of the audio or video file, then the EXTENT and EXTTYPE atributes may be omitted.

requirement: @ID="structMap12"

An <area> element in documents implementing this profile should not use the SHAPE, COORDS or ADMID attributes. It may, but need not, contain a CONTENTIDS attribute; however this profile provides no guidelines or rules for the use of this attribute

requirement: @ID="structMap13"

An <fptr>; element representing a content type other than structured text, audio or video in conforming documents can only reference integral content files. METS documents conforming to this profile must not use the <area> element with its associated BEGIN and END attributes to isolate internal segments of such content files. An <fptr> element could, however , under some circumstances, contain <area> elements, providing these <area> elements reference integral content files. For example, an <fptr> element would contain a <seq> element with multiple child <area> elements 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 page 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.

requirement: @ID="structMap14"

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.

structLink:
requirement: @ID="structLink1"

A conforming METS document may contain a <structLink> element. This profile, however, establishes no guidelines or expectations for its use.

behaviorSec:
requirement: @ID="behaviorSec1"

A conforming METS document may contain a <behaviorSec> element. This profile, however, establishes no guidelines or expectations for its use.

multiSection:
requirement: @ID="multi1"

Only <file> elements will reference <techMD>, <sourceMD> and/or <digiprovMD> elements. In other words, documents implementing this profile will express technical, source, and digital provenance administrative metadata in conjunction with content files only rather than in conjunction with <div> elements in the <structMap>. <rightsMD> elements, however, may be referenced only from <div> elements in the <structMap>.

requirement: @ID="multi2"

Only <div> elements will reference <dmdSec> elements. In other words, documents implementing this profile will express descriptive metadata in conjunction with divisions of the <structMap> and not in conjunction with individual content files (<file> elements).

requirement:

METS documents implementing this profile that are destined for CDL must also observe the structural requirements set forth in the CDL Guidelines for Digital Objects (http://www.cdlib.org/inside/diglib/guidelines/), which may be more specific or restrictive in some areas than this profile.

technical_requirements:
content_files:
requirement:

Image, application, video and audio content files referenced from conforming METS documents may be of any type supported by the CDL Guidlines for Digital Objects (http://www.cdlib.org/inside/diglib/guidelines/).

requirement:

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).

  Top of Page Top of Page
 
  The Library of Congress >> Standards
  July 1, 2011

Legal | External Link Disclaimer

Contact Us