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 http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-0.xsd http://www.loc.gov/mix/ http://www.loc.gov/standards/mix/mix.xsd http://cosimo.stanford.edu/sdr/metsrights/ http://cosimo.stanford.edu/sdr/metsrights.xsd"
title:
UCB Imaged Object Profile
abstract:
This profile represents a specific subset of the Model Imaged Object Profile. UC Berkeley Library METS objects which have only associated image content files directly implement this profile. UC Berkeley METS objects which have both associated image and text content files implement the closely related UCB Paged Text Object Profile.
date:
2004-04-27T08:00:00
contact:
name:
Rick Beaubien
address:
Library Systems Office, Rm. 386 Doe Library, University of California, Berkeley, CA 94720-6000
phone:
(510) 643-9776
email:
rbeaubie@library.berkeley.edu
related_profile: @RELATIONSHIP="subset of" @URI="http://www.loc.gov/mets/profiles/00000004.xml"
Model Imaged Object Profile
related_profile: @RELATIONSHIP="extended by" @URI="http://www.loc.gov/mets/profiles/00000003.xml"
UCB Paged Text Object Profile
extension_schema:
name:
NISOIMG
context:
mets/amdSec/techMD/mdWrap/xmlData
note:
Used for technical metadata about image content files.
description_rules:

All applications of the MODS schema in conforming METS documents follow the MODS User Guidelines published by Library of Congress' Network Development and MARC Standards Office.

controlled_vocabularies:
vocabulary:
name:
Model Imaged Object Profile file USE attribute values
maintenance_agency:
Library Systems Office, The General Library, University of California, Berkeley
values:
value:
archive image
value:
reference image
value:
thumbnail image
context: @ID="vc1" @RELATEDMAT="fileSec2"

mets/fileSec/fileGrp/@USE

mets/fileSec/fileGrp/file/@USE

description:

These are the supported values for <file> and <fileGrp> USE attributes in objects conforming to this profile. "archive image" designates image masters; "thumbnail image" image thumbnails; and "reference image" any intermediate resolutions intended for reference purposes

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

vocabulary:
name:
Model Imaged Object structMap TYPE attribute values
maintenance_agency:
Library Systems Office, The General Library, University of California, Berkeley
values:
value:
physical
value:
mixed
context: @ID="vc2" @RELATEDMAT="structMap2"

mets/structMap/@TYPE

description:

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 single image without subdivisions; an image divided into recto and verso views; a photo album divided into page views divided into views of the individual photographs on the page; a pamphlet divided into page views

"mixed" designates a mixed structure. For example, a book divided into chapters, divided into page views.

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 that contains a valid ark and uniquely identifies the object in its owning repository.

metsHdr:
requirement: @ID="metsHdr1"

Conforming METS documents must contain a metsHdr element.

requirement: @ID="metsHdr2"

<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:

<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 <dmdRef> or a <dmdWrap>

requirement: @ID="dmdSec2"

If a <dmdSec> of a conforming document contains a <dmdWrap> with <xmlData>, the <xmlData> elements must conform to the MODS schema.

amdSec:
requirement: @ID="amdSec1"

Conforming METS documents may but need not contain an <amdSec> element. This <amdSec> may but need not contain one or more <techMD> elements, <sourceMD> elements, <rightsMD> elements and/or <digiprovMD> elements.

requirement: @ID="amdSec2"

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

requirement: @ID="amdSec3"

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.

requirement: @ID="amdSec4"

If one or more <rightsMD> elements are present, they must contain <xmlData> conforming to the METSRights schema.

requirement: @ID="amdSec5"

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

requirement: @ID="amdSec6"

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.

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, and one <fileGrp> representing GIF thumbnail images. Each of these <fileGrp> elements may or may not contain subsidiary <fileGrp> elements representing subgroups of the content files.

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

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>. Supported <file>/<fileGrp> USE attribute values appear in the <controlled_vocabularies> section of this document.

requirement: @ID="fileSec3"

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

structMap:
requirement: @ID="structMap1"

A conforming METS document must contain only one <structMap>.

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

A conforming <structMap> must contain a TYPE attribute with the value "physical" or "mixed"

requirement: @ID="structMap3"

Each <div> must include a LABEL attribute value.

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 IDs specified at the <dmdSec> element level, and not IDs at lower levels. For example, a <div> DMDID attribute should not reference an ID value of an element within the <xmlData> section of a <dmdSec>

requirement: @ID="structMap5"

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

requirement: @ID="structMap6"

The <div> elements of documents conforming to this profile must not contain <mptr> elements. The <mptr> element is not supported.

requirement: @ID="structMap7"

An <fptr> element must directly point to a <file> element via its FILEID attribute. METS documents implementing this profile must not use the <area> or <par> elements.

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> <rightsMD> and/or <digiprovMD> elements. In other words, documents implementing this profile will express administrative metadata in conjunction with content files only, and not in conjunction with <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).

technical_requirements:
content_files:
requirement:

This profile supports only image content files.

requirement:

The master (archive) images must be represented and of TIFF format.

requirement:

At least one version of the image content must be of JPEG or GIF format. In other words, at least one content file format must be natively supported by typical internet browsers.

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

Legal | External Link Disclaimer

Contact Us