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/ http://www.loc.gov/standards/mods/v3/mods-3-0.xsd"
title:
Oxford Digital Library METS Profile
abstract:
This profile documents the use of METS for standard image or image+text digital objects within the Oxford Digital Library (ODL).
date:
2003-12-12T15:15:00
contact:
name:
Richard Gartner
address:
SERS Building, Osney Mead, Oxford OX2 0EZ, UK
phone:
+44 1865 280029
email:
richard.gartner@sers.ox.ac.uk
related_profile:
There are no related profiles.
extension_schema:
name:
MODS (Metadata Object Description Schema) schema, version 3
context:
Used for encoding descriptive metadata
extension_schema:
name:
ODL Administrative Metadata Schema
context:
Used to encode administrative metadata for image files. This DTD is used only for external metadata records, and should only be used for records linked from a techMD element.
extension_schema:
name:
ODL extensions to MODS
note:
Extensions to the MODS schema specific to the ODL: these cover any facets of descriptive metadata not adequately handled by MODS itself
description_rules:

Descriptive metadata should follow the ODL Guidelines for descriptive metadata (http://www2.odl.ox.ac.uk/guidelines/), including the ODL's name authority rules enumerated within these (essentially conformance to the Anglo-American Name Authority file with supplementary lists specific to the ODL for names absent from this). The metadata is input into the ODL's webform-based metadata system using qualified Dublin Core fields (described in the above guidelines), but converted to the MODS schema when the METS file is generated.

Any names or titles not taken from an authority list should be formatted according to AACR2 conventions.

controlled_vocabularies:
vocabulary:
name:
Library of Congress Subject Headings
maintenance_agency:
Library of Congress Network Development & MARC Standards Office
context:

At least one LCSH heading is compulsory for each record - other taxonomies specific to each project may be used in addition to this

vocabulary:
name:
MARC21 relator codes
maintenance_agency:
Library of Congress Network Development & MARC Standards Office
context:

Used for encoding the relationship of any person or entity named in descriptive metadata to the item itself.

vocabulary:
name:
ODL List of Types
maintenance_agency:
Oxford Digital Library
context:

Used to encode the genre of the item

vocabulary:
name:
ISO 639-2
maintenance_agency:
International Standard Organization
context:

Encodes the languages used in the content of the item

structural_requirements:
metsHdr:
requirement:

The OBJID attribute in the mets element must be present: this contains the system id for the item (eg. munahi010-aaa).

dmdSec:
requirement:

One dmdSec, identified by an ID attribute in the form "objectid-dmd-0001" will contain a MODS record detailing the descriptive metadata for the item as a whole: this is embedded in a mdWrap element.

requirement:

Other dmdSecs may contain descriptive metadata in other schemas for all or part of the item: these are referenced by DMDID attributes within the structMap.

amdSec:
requirement:

Files are grouped according to their referent into amdSec elements, one for each object referenced: thus, all adminstrative metadata for manifestations of the same scanned object (eg page of a volume) are grouped into the same amdSec.

requirement:

Each amdSec is given an identifier in the form "objectid-amd-0001" etc, numbered sequentially.

requirement:

Each amdSec contains one techMD element for each file associated with the object referenced by it: these techMD elements are given identifiers in the form "objectid-tmd-0001-0" numbered sequentially - the final digit refers to the version of the referent instantiated by the file, according to the same schema as that followed by the file's GROUPID attribute in the fileSec.

requirement:

Each techMD element contains an mdRef element referencing the location of the XML file containing the administrative metadata itself. The MDTYPE attribute is set to "OTHER" and the OTHERMDTYPE attribyte to "ODL Admin Metadata Scheme".

fileSec:
requirement:

Files are grouped according to their referent into fileGrp elements: thus, all manifestations of the same scanned object (eg page of a volume) are grouped into the same fileGrp.

requirement:

Each fileGrp is given an identifier in the form "objectid-fgrp-001" etc, numbered sequentially.

requirement:

The GROUPID attribute for each file element refers to which instantiation of the referent is represented by the given file - eg thumbnail, delivery version. The following scheme is used for these codes: 0 = archival master, 1 = archival production, 2 = delivery, large, 3 = delivery, medium, 4 = delivery, small, 5 = thumbnail, 6 = small thumbnail, 7 = other. Non-image files may be identified by an suitable code, eg TEI.

requirement:

An fLocat element within each file element references the file itself by the xlink:href attribute.

requirement:

An ADMID attribute on each file attribute points to the technical metadata for that file held within the admSec.

structMap:
requirement:

Only one structMap is present in the METS document: this contains both the logical and physical structures of the item within a single hierarchy. This hierarchy is bounded by a div element, the DMDID attribute of which is set to the ID "objectid-dmd-0001" - ie. the ID of the MODS record describing the item as a whole.

requirement:

The div elements within the structural map each have an ID attribute in the form "objectid-div.x.x.x." where "x.x.x" represents a hierarchical numbering system which mirrors the hierarchical arrangement of the divs themselves (eg munahi010-aaa-div.1.2.1)

requirement:

No type attributes are used for div elements

requirement:

Each lowest level div element contains a fptr element, whose FILEID attribute points to the fileGrp of the referenced item in the fileSec.

requirement:

A LABEL attribute must be provided for each div element.

technical_requirements:
content_files:
requirement:

Archival quality images, identified by GROUPID=0 in the file element, are scanned in TIFF format, in bit-depths of either 1,8 or 24 bits per pixel depending on the requirements of the source material. 1 bit images are compressed using G4(2D) compression, otherwise the images are uncompressed.

requirement:

Medium-sized delivery images, identified by GROUPID=3, are stored in JPEG format at a maximum resolution of 1000x1000 pixels.

requirement:

Thumbnail images, identified by GROUPID=6, are stored in JPEG format at a maximum resolution of 96x96 pixels.

requirement:

All text files referenced by the METS object must conform to the TEI P4 DTD (http://www.tei-c.org/P4X/) and to one of levels 1-4 of the TEI Text Encoding in Libraries Guidelines for Best Encoding Practices (http://www.indiana.edu/~letrs/tei/).

tool:
agency:
Oxford Digital Library
description:

METS files for the Oxford Digital Library are created by an in-house web-form input mechanism, based on mySql and PHP. It is not available for general access at present.

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

Legal | External Link Disclaimer

Contact Us