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:
UCSD Complex Object Profile
abstract:
The UCSD Libraries uses the UCSD Complex Object profile for composing METS instances for digital objects in which the primary content of the digital object is contained in two or more digital files. The content files may be of any format type, e.g., audio, image, text, or video, and there can be any combination of formats within a single complex object. There are no restrictions placed on the type of logical structure represented in the complex object. The decision to require a complex object’s structure to be represented by both physical and logical <structMap>s, as described in the profile, is influenced by the current requirements of the METS Navigator application.
date:
2007-07-30T10:53:31
contact:
name:
Digital Library Office
address:
Geisel Library, UC, San Diego
email:
dlo@ucsd.edu
related_profile: @RELATIONSHIP="Extends" @URI="http://www.loc.gov/standards/mets/profiles/00000012.xml"
UCSD Simple Object Profile
extension_schema:
name:
MODS
context:
mets/dmdSec/mdWrap/xmlData
note:
Used for descriptive metadata representing the intellectual object.
extension_schema:
name:
PREMIS
context:
mets/amdSec/techMD/mdWrap/xmlData
note:
Used for technical metadata about content files.
extension_schema:
name:
METSRights
context:
mets/amdSec/rightsMD/mdWrap/xmlData
note:
Used for recording intellectual property rights.
description_rules:

All applications of MODS in UCSD METS records adhere to the MODS User Guidelines published by the Library of Congress's Network Development and MARC Standards Office.

MODS usage in UCSD METS records is also informed by The Digital Library Federation / Aquifer Implementation Guidelines for Shareable MODS Records.

controlled_vocabularies:
vocabulary:
name:
UCSD file USE attribute values
maintenance_agency:
University of California, San Diego
values:
value:
Application-PDF
value:
Application-PS
value:
Audio-Master
value:
Audio-Master-Edited
value:
Audio-Service
value:
Audio-Streaming
value:
Audio-Clip
value:
Image-Master
value:
Image-Master-Edited
value:
Image-Service
value:
Image-Service-LowRes
value:
Image-Service-MedRes
value:
Image-Service-HighRes
value:
Image-Service-Edited
value:
Image-Thumbnail
value:
Text-OCR-Edited
value:
Text-OCR-Unedited
value:
Text-TEI-Translated
value:
Text-TEI-Transcripted
value:
Text-Georeference
value:
Text-Data
value:
Text-Data Definition
value:
Text-Codebook
value:
Video-Master
value:
Video-Master-Edited
value:
Video-Service
value:
Video-Streaming
value:
Video-Clip
context: @ID="vc1" @RELATEDMAT="fileSec2"

mets/fileSec/fileGrp/@USE

mets/fileSec/fileGrp/file/@USE

Each <fileGrp> must include a file USE attribute, with a value taken from the controlled vocabulary listed above, representing the intended use of the referenced file(s).
description:

These are the values supported for <file> and <fileGrp> USE attributes for digital objects conforming to this profile.

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 a PROFILE attribute value.

requirement: @ID="metsRoot3"

The root <mets> element must include an OBJID attribute value that uniquely identifies the METS instance in the UCSD digital repository. The value must be an ARK. .

metsHdr:
requirement: @ID="metsHdr1"

A METS record conforming to this profile must contain a <metsHdr> element.

requirement: @ID="metsHdr2"

The <metsHdr> element must contain the CREATEDATE attribute.

requirement: @ID="metsHdr3"

The <metsHdr> element must contain an <agent> with the ROLE attribute value "CREATOR" and a TYPE attribute value "ORGANIZATION".

requirement: @ID="metsHdr4"

The <agent> element must contain the <name> element with the value "Digital Library Office, Geisel Library, University of California, San Diego", and a <note> element with the value "mailto:dlo@ucsd.edu".

requirement: @ID="metsHdr5"

The <metsHdr> element should, but is not required to, contain a LASTMODDATE attribute reflecting the date of the last modification to the METS record.

dmdSec:
requirement: @ID="dmdSec1"

A METS record conforming to this profile must contain at least one <dmdSec> containing a <mdWrap> with <xmlData>.

requirement: @ID="dmdSec2"

All <dmdSec> elements must contain an ID attribute.

requirement: @ID="dmdSec3"

The required dmdSec/mdWrap/xmlData must contain elements from the Metadata Object Description Schema (MODS) and describe the digital object as a whole.

requirement: @ID="dmdSec4"

A conforming METS record must contain a mods/titleInfo/title element.

requirement: @ID="dmdSec5"

A conforming METS record must contain a mods/typeOfResource element for which the value must be taken from the MODS typeOfResource values. Type of resource values should be determined by the materials content not the file format. For example an image of a page of text should have the value "text".

requirement: @ID="dmdSec6"

A conforming METS record must contain a mods/identifier element, with the attribute TYPE="ARK". The element should contain the actionable URL ARK for the digital object as a whole, not a constituent file.

requirement: @ID="dmdSec7"

A conforming METS record must contain a mods/note element, with the attribute displayLabel="Digital object made available by". The element should name the UCSD Libraries' data provider that is primarily responsible for making the resource available digitally with the URL for the provider's main webpage, e.g. Mandeville Special Collections Library, University of California, San Diego, La Jolla, CA 92093-0175 (http://orpheus.ucsd.edu/speccoll/)

requirement: @ID="dmdSec8"

A conforming METS record should, but is not required to, contain the following descriptive metadata elements when they are applicable: creator (mods/name/namePart), date of creation (mods/originInfo/dateCreated), genre (mods/genre), description (mods/abstract), subject (mods/subject/...), language of the object (mods/language), publisher (mods/originInfo/publisher), place of publication (mods/originInfo/place) and the name of the project or collection to which the object belongs (mods/relatedItem/titleInfo/title).

requirement: @ID="dmdSec9"

If present, descriptive metadata for each component part of the digital object must be placed in a separate <dmdSec> element and expressed with the MODS metadata schema.

requirement: @ID="dmdSec10"

If parallel description, in a schema other than MODS (e.g., Dublin Core, VRA, FGDC, etc.), is provided for the object or its components, each parallel description must be placed in a separate <dmdSec> element. When adding elements from metadata schemas these should conform to standardized guidelines for the schema.

amdSec:
requirement: @ID="amdSec1"

A METS record conforming to this profile must have an <amdSec> section. The <amdSec> section must contain at least one techMD/mdWrap/xmlData section for each master file and at least one rightsMD/mdWrap/xmlData section pertaining to the digital object as a whole.

requirement: @ID="amdSec2"

All <techMD> and <rightsMD> elements must contain an ID attribute.

requirement: @ID="techMD1"

The required <techMD> sections must contain elements from the PREMIS schema.

requirement: @ID="techMD2"

The required <techMD> sections should describe the digital files of the greatest archival quality.

requirement: @ID="techMD3"

A conforming METS record must contain a pre/object/objectIdentifier/objectIdentifierType element with the value "ARK", and a pre/object/objectIdentifier/objectIdentifierValue element with the unique ID.

requirement: @ID="techMD4"

A conforming METS record must contain a pre/object/preservationLevel element. The value should be either "Full" or "Bit-level".

requirement: @ID="techMD5"

A conforming METS record must contain a pre/object/objectCategory element. The value should be "File".

requirement: @ID="techMD6"

A conforming METS record must contain a pre/object/objectCharacteristics/compositionLevel element. The value should be "0" for uncompressed files.

requirement: @ID="techMD7"

A conforming METS record must contain a pre/object/objectCharacteristics/fixity/messageDigestAlgorithm element and a pre/object/objectCharacteristics/fixity/messageDigest element.

requirement: @ID="techMD8"

A conforming METS record must contain a pre/object/objectCharacteristics/size element.

requirement: @ID="techMD9"

A conforming METS record must contain a pre/object/objectCharacteristics/format/formatName element.

requirement: @ID="techMD10"

A conforming METS record must contain a pre/object/creatingApplication/dateCreatedByApplication element.

requirement: @ID="techMD11"

A conforming METS record should, but is not required to, include the following PREMIS elements: medium on which the object is stored (pre/object/storage/storageMedium), file format version (pre/object/objectCharacteristics/formatDesignation/formatVersion), name of the application that created the file (pre/object/creatingApplication/creatingApplicationName), and the original file name (pre/object/originalName)

requirement: @ID="techMD12"

Additional <techMD> sections may, but are not required to, be used for the description of files other than the master file, or for inclusion of format specific metadata for any file.

requirement: @ID="techMD13"

Additional format specific <techMD> sections for the description of images must be expressed with the MIX schema.

requirement: @ID="techMD14"

Additional format specific <techMD> sections for the description of text must be expressed with the TextMD schema.

requirement: @ID="techMD15"

Additional format specific <techMD> sections for the description of audio or video, should conform to an extension schema endorsed by the METS Editorial Board (although at this date of publication extension schemas have not yet been endorsed for audio or video).

requirement: @ID="techMD16"

Source or provenance metadata expressed as MIX pertaining to image content files, can be included in a <techMD> section instead of a separate <sourceMD> section.

requirement: @ID="rightsMD1"

The required <rightsMD> must contain elements from the METSRights schema. The <rightsMD> for the digital object as a whole will be taken to apply to all component parts unless different rights are specified for components in additional <rightsMD> sections.

requirement: @ID="rightsMD2"

A conforming METS record must include a rts/RightsDeclarationMD element with the RIGHTSCATEGORY attribute encoded as either "COPYRIGHTED", "PUBLIC DOMAIN" or "OTHER".

requirement: @ID="rightsMD3"

A conforming METS record must include a rts/RightsDeclarationMD/RightsDeclaration from the METSRights Schema with the value expressed as either "Copyright is held by unnamed third party" for works for which the copyright holder(s) can not be identified, "Copyright is held by named third party but not the UC Regents" for works for which the copyright holder(s) is not the UC Regents and can be identified, "Copyright held by the UC Regents" for materials under copyright to the University of California Regents, "The work is in the public domain" for works known to have entered the public domain, or "Copyright status has not been determined by the UCSD Libraries" for works for which the copyright holder(s) cannot be identified and the work cannot be said to have entered the public domain.

requirement: @ID="rightsMD4"

If necessary, a justification of the rights declaration can be included in rts/RightsDeclarationMD/RightsDeclaration/ element to explain the copyright assertion. This is not necessary if the basis for the assertion is evident in the descriptive metadata for the object. In cases where this is not evident, a justification statement may be very useful. Examples of such cases include 1) when the copyright holder is different than the creator and 2) when an item has been gifted to the public domain prior to the copyright expiring.

requirement: @ID="rightsMD5"

A conforming METS record must include a rts/RightsDeclarationMD/Context/Constraints/ConstraintDescription containing an indication of how the digital asset can be used. See the UCSD Rights Metadata Strategy for boilerplate text.

requirement: @ID="rightsMD6"

A conforming METS record may, but is not required to, include a rts/RightsHolder/… from the METSRights Schema for those works for which the copyright holder(s) can be identified. Data can include the name of the copyright holder(s), their contact information and any notes relevant to the copyright holder.

requirement: @ID="sourceMD1"

If source metadata is recorded, elements in the <sourceMD> sections should be expressed using an extension schema endorsed by the METS Editorial Board designed for expressing source metadata (although at this date of publication an extension schema has not yet been endorsed for source metadata).

requirement: @ID="digiprovMD1"

If provenance metadata is recorded, elements in the <digiprovMD> sections should be expressed using an extension schema endorsed by the METS Editorial Board designed for expressing provenance metadata (although at this date of publication an extension schema has not yet been endorsed for provenance metadata).

fileSec:
requirement: @ID="fileSec1"

The <fileSec> for a compliant METS record must contain one, or more, <fileGrp> elements.

requirement: @ID="fileSec2"

Each <fileGrp> must include a file USE attribute, with a value taken from the controlled vocabulary listed above, representing the intended use of the referenced file(s).

requirement: @ID="fileSec3"

Each <file> element must contain ID and GROUPID attribute value pairs.

requirement: @ID="fileSec4"

Each <file> element must reference pertinent <techMD> sections by including the relevant ID values in the ADMID attribute. The ADMID attribute should also reference pertinent <sourceMD> and <provenanceMD> elements, if present. The <file> element should only reference ID values at the levels of <techMD>, <sourceMD>, and <digiprovMD>.

structMap:
requirement: @ID="structMap1"

A conforming METS record must contain two <structMap> elements, one with the TYPE attribute value encoded as "logical", a second with the value encoded as "physical".

requirement: @ID="structMap2"

The physical <structMap> represents a flattened structure and must only contain two levels of <div> elements with no further nesting. The top level <div> element required by the METS schema contains one level of child <div> elements to represent the linear sequence of the components of the digital object.

requirement: @ID="structMap3"

The logical structMap represents the full hierarchical structure of the digital object, and so can contain as many levels of nested <div> elements as required to express the objects full structure.

requirement: @ID="structMap4"

All <div> elements within the top level containing <div> must have an ORDER attribute.

requirement: @ID="structMap5"

When applicable, <div> elements must reference pertinent <dmdSec> sections by including the relevant ID values in the DMDID attributes.

requirement: @ID="structMap6"

When applicable, <div> elements should include a LABEL attribute with the value derived from, and identical, to the value encoded in the /mods/titleInfo/title element in the related <dmdSec>.

requirement: @ID="structMap7"

When applicable, <div> elements must reference pertinent <rightsMD> sections by including the relevant ID values in the ADMID attributes.

requirement: @ID="structMap8"

Each <fptr> element must reference an individual <file> element representing a version of the file.

requirement: @ID="structMap9"

The <fptr> element must use the FILEID attribute to point directly to a <file> element.

requirement: @ID="structMap10"

The <fptr> element may not contain an <area>, <par>, or <seq> element. These elements are not supported in objects conforming to this profile.

requirement: @ID="structMap11"

The <mptr> element is not supported in this profile.

structLink:
requirement: @ID="structLink1"

This profile stipulates no requirements for the <structLink> element.

behaviorSec:
requirement: @ID="behaviorSec1"

This profile stipulates no requirements for the <behaviorSec> element.

multiSection:
requirement: @ID="multi1"

Only <file> elements will reference elements in the <techMD>, <sourceMD>, and <digiprovMD> sections.

requirement: @ID="multi2"

Only the <div> element will reference metadata in the <dmdSec> and <rightsMD> sections. That is, descriptive metadata and rights metadata are always and only expressed in conjunction with division of the <structMap> and not in conjunction with the content file(s).

technical_requirements:
content_files:
requirement:

The profile does not prescribe a format for the file, but it is strongly recommended that the file format and resolution for at least one version of the image be of an archival quality.

behavior_files:
requirement:

The profile does not prescribe association to any behaviors.

metadata_files:
requirement:

This profile does not prescribe referencing of external metadata records. If an external metadata record is referenced, it is recommended that the file be valid for the schema in which it is written, i.e., that it be a valid MARC record.

tool:
description:

Some of the requirements of this profile, especially the requirement for two <structMap>s, are influenced by the METS Navigator application as it is currently available.

  Top of Page Top of Page
 
  The Library of Congress >> Standards
  December 5, 2013

Legal | External Link Disclaimer

Contact Us