Skip Navigation Links The Library of Congress >> Standards
Metadata Encoding and Transmission Standard (METS) Official Web Site
METS_Profile: @xsi:schemaLocation="//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:
Model Imaged Object Profile
abstract:
This profile is intended as a generic, base profile for METS documents representing imaged materials. It may be useful in itself for pictorial materials such as single images or photo albums, for text-based materials for which no tei transcription or translation is provided, or as a starting point for the derivation of more specific and complex profiles for imaged materials.
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:
[email protected]
related_profile: @RELATIONSHIP="extended by" @URI="//www.loc.gov/mets/profiles/00000005.xml"
Model Paged Text Object Profile
extension_schema:
note:
This profile does not require the use of any specific extension schemas in the context of METS <dmdSec> and <amdSec> elements.
description_rules:

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.

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"

[email protected]

[email protected]

description:

These are the supported values for <file> and <fileGrp> USE attributes in 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.

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"

[email protected]

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 uniquely identifies the object in its owning repository.

metsHdr:
requirement: @ID="metsHdr1"

Conforming METS documents may, but need not, contain a <metsHdr> element.

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"

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.

amdSec:
requirement: @ID="amdSec1"

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>

requirement: @ID="amdSec2"

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.

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

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 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="structMap5"

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

requirement: @ID="structMap6"

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.

technical_requirements:
content_files:
requirement:

This profile supports only image content files.

requirement:

Image master files must be represented and of TIFF format

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

Legal | External Link Disclaimer

Contact Us