@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/ http://www.loc.gov/standards/mods/v3/mods-3-0.xsd"
Oxford Digital Library METS Profile
This profile documents the use of METS for standard image or image+text digital
objects within the Oxford Digital Library (ODL).
ODL Administrative Metadata Schema
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.
ODL extensions to MODS
Extensions to the MODS schema specific to the ODL: these cover any facets of
descriptive metadata not adequately handled by MODS itself
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
Library of Congress Subject Headings
At least one LCSH heading is compulsory for each record - other taxonomies
specific to each project may be used in addition to this
MARC21 relator codes
Used for encoding the relationship of any person or entity named in descriptive
metadata to the item itself.
The OBJID attribute in the mets element must be present: this contains the system
id for the item (eg. munahi010-aaa).
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.
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.
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.
Each amdSec is given an identifier in the form "objectid-amd-0001" etc, numbered sequentially.
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.
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".
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.
Each fileGrp is given an identifier in the form "objectid-fgrp-001" etc, numbered sequentially.
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.
An fLocat element within each file element references the file itself by the
An ADMID attribute on each file attribute points to the technical metadata for
that file held within the admSec.
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.
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)
Each lowest level div element contains a fptr element, whose FILEID attribute
points to the fileGrp of the referenced item in the fileSec.
A LABEL attribute must be provided for each div element.
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.
Medium-sized delivery images, identified by GROUPID=3, are stored in JPEG format
at a maximum resolution of 1000x1000 pixels.
Thumbnail images, identified by GROUPID=6, are stored in JPEG format at a maximum
resolution of 96x96 pixels.
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
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.