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/version16/mets.v1-6.xsd"
title:
Ex Libris - DigiTool multi-page entity
abstract:
DigiTool uses the METS standard to describe a group of files/objects with parent child relationships that comprise one intellectual entity. The METS structure map in DigiTool allows describing a multi-hierarchical level description of the object (for example, a logical table of contents of a book). 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 METS. The decision to require use of METS vs. complex object or collection management structure is influenced by the desired result and the nature of the material.
date:
2008-01-01T00:00:00
contact:
name:
Ex Libris LTD.
address:
Gan Technology 8, Malcha Jerusalem, Israel
phone:
972-2-6499100 or 972-2-6499106
email:
digitool.support@exlibris.co.il
related_profile:
There are no related profiles.
extension_schema:
name:
Simple DC XML Schema (dc:)
context:
Used for encoding descriptive metadata. (MDTYPE="DC")
extension_schema:
name:
Qualified DC XML Schema (dcterms:)
context:
Used for encoding descriptive metadata. (MDTYPE="DC")
extension_schema:
name:
MARC
context:
Used for encoding descriptive metadata. (MDTYPE="MARC")
extension_schema:
name:
MODS
context:
Used for encoding descriptive metadata. (MDTYPE="MODS")
extension_schema:
name:
Technical Video (LOC)
context:
Used for encoding administrative technical metadata, specifically related to video. (MDTYPE="OTHER" OTHERMDTYPE="LC-V")
extension_schema:
name:
Technical Audio (LOC)
context:
Used for encoding administrative technical metadata, specifically related to audio. (MDTYPE="OTHER" OTHERMDTYPE="LC-A")
extension_schema:
name:
Technical Image
context:
Used for encoding administrative technical metadata, specifically related to still images. (MDTYPE="NISOIMG")
extension_schema:
name:
Technical Text
context:
Used for encoding administrative technical metadata, specifically related to text. (MDTYPE="OTHER" OTHERMDTYPE="text_md")
extension_schema:
name:
Access Rights
context:
Used for encoding administrative intellectual property rights metadata, specifically for access rights. (MDTYPE="OTHER" OTHERMDTYPE="rights_md")
extension_schema:
name:
Copyrights Metadata
context:
Used for encoding administrative intellectual property rights metadata, specifically copyrights related material.(MDTYPE="OTHER" OTHERMDTYPE="copyrights_md")
extension_schema:
name:
Preservation Metadata
context:
Used for encoding administrative preservation metadata. (MDTYPE="OTHER" OTHERMDTYPE="preservation_md")
extension_schema:
name:
Change History Metadata
context:
Used for encoding administrative change history metadata. Based on the PREMIS event metadata: http://www.loc.gov/standards/premis/Event-v1-0.xsd. (MDTYPE="OTHER" OTHERMDTYPE="history_md")
description_rules:

Descriptive metadata contents should be encoded using MARC, Dublin Core, Dublin Core Terms, or MODS extension schemas, following both the appropriate guidelines recommended by the extension schemas' maintenance agencies and the Ex Libris Guidelines for descriptive metadata. The metadata should be embedded in the METS file as XML, using the mdWrap tag.

controlled_vocabularies:
vocabulary:
name:
USE attribute values are mandatory (see DigiTool-specific mets_configuration.xml to achieve preferred usage in DTL) The following are the out of the box values. Other values are supported as well but would need to be defined in the mets_configuration.xml mapping file.
maintenance_agency:
Ex Libris Systems Office
values:
value:
thumbnail
value:
index
value:
archive
value:
reference
value:
reference image
value:
reference video
value:
reference audio
value:
reference text
value:
alto
value:
Images
value:
Text
context: @ID="vc1" @RELATEDMAT="fileSec2"

mets/fileSec/fileGrp/@USE

description:
head:
These are the supported values for <fileGrp> USE attributes.

thumbnail - A low resolution image

index - A plain text or HTML file which can be used for full text search

archive - Master copy usually from tiff format for image resources

reference - Any type of delivery format - usually a Web transportable file size for image/text/video/audio etc.

reference image - Image manifestation of primary reference usage copy

reference video - Video manifestation of primary reference usage copy

reference audio - Audio manifestation of primary reference usage copy

reference text - Textual manifestation of primary reference usage copy

alto - Index manifestation in the alto XML format (http://www.loc.gov/ndnp/alto_1-1-041.xsd) This index file can be used for full text search and highlighting functions

Images - This is a CCS compliant use type for image based objects

Text - This is a CCS compliant use type for alto objects

PDF - This is a CCS compliant use type for PDF objects

vocabulary:
name:
Ex Libris Digital Object <structMap> TYPE attribute values
maintenance_agency:
Ex Libris Systems Office
values:
value:
physical
value:
logical
value:
mixed
context: @ID="vc2" @RELATEDMAT="structMap2"

mets/structMap/@TYPE

description:
head:
These are the suggested values for the <structMap> TYPE attribute in METS documents conforming to this profile.

"physical" designates a purely physical structure. For example, a book divided into page views.

"logical" designates a purely logical structure. For example, a book divided into chapters or a diary divided into diary entries. This <structMap> will be the default view when viewing METS objects that contain it.

"mixed" designates a mixed structure. For example, a book divided into chapters and also divided into page views. This <structMap> will be the default view when viewing METS objects and no "logical" <structMap> exist.

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 TYPE attribute value.

metsHdr:
requirement: @ID="metsHdr1"

Conforming METS documents must contain a <metsHdr> element.

Conforming METS documents must contain a <metsHdr/agent/name> element.

dmdSec:
requirement:

Conforming METS documents may, but need not, contain one or more <dmdSec> elements.

requirement: @ID="dmdSec1"

Any metadata provided must be embedded in the METS file as XML using the mdWrap tag.

mdRef is not supported.

requirement: @ID="dmdSec2"

If a <dmdSec> of a conforming document contains a <mdWrap> with <xmlData>, the <xmlData> must conform to those listed in the extension schemas section above.

requirement: @ID="dmdSec3"

Any dmdSec ID may, but need not be, referenced by the DMDID value denoted in either the fileSec section or structMap div section sections.

When referenced using DMDID from the top-level structMap div, the assumption is that the metadata is relevant to the intellectual entity ONLY and not the specific files included in that intellectual entity.

When referenced using DMDID from the non top-level structMap divs, the assumption is that the metadata is relevant to the pages/files referenced from that div-level reference and inherited downward.

When not referenced using DMDID at all, the assumption is that the metadata is relevant to the intellectual entity ONLY and not the specific files included in that intellectual entity.

amdSec:
requirement: @ID="amdSec1"
head:
Conforming METS documents may or may not contain administrative metadata. Any of the supported <amdSec> child elements may appear: <history_md>, <rights_md>, <text_md>, <LC_A>, <LC_V>, <IMAGENISO> grouped by their most relevant category of administrative type i.e. <IMAGENISO> would fall under the classification of:

techMD (technical metadata) - Technical Video (LOC), Technical Audio (LOC), Technical Image, Technical Text.

rightsMD (intellectual property rights metadata) - Access Rights, Copyrights Metadata.

sourceMD (analog/digital source metadata) - Preservation Metadata.

digiprovMD (digital provenance metadata) - Change History Metadata.

requirement: @ID="amdSec2"

A conforming METS document will contain one <amdSec> element per file.

Any defined <history_md>, <rights_md>, <text_md>, <audio_md>, <video_md>, <IMAGENISO> element or elements for the same file will appear in this single <amdSec> element and be designated by the appropriate type (techMD, rightsMD, etc.). Note that if the amdSec includes more than 1 metadata per file the ID reference should be to the specific child element metadata ID and not to the amdSec ID

requirement: @ID="amdSec3"

If a <amdSec> of a conforming document contains a <amdWrap> with <xmlData>, the <xmlData> must conform to those listed in the extension schemas section above.

requirement: @ID="amdSec4"

Any amdSec or child element techMD, rightsMD, sourceMD or digiprovMD ID may, but need not be, referenced by the ADMID value denoted in either the fileSec section or structMap div section sections.

When referenced using ADMID from the fileSec level - the metadata will be associated specifically with that particular file.

When not referenced using ADMID at all, the assumption is that the metadata is relevant to the intellectual entity ONLY and not the specific files included in that intellectual entity.

fileSec:
requirement: @ID="fileSec1"

The <fileGrp> element must have a USE attribute.

Supported USE attribute values appear in the <controlled_vocabularies> section of this document.

requirement: @ID="fileSec2"

The USE attribute should be expressed at the <fileGrp> level and not on the <file> level.

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

The <fileSec> must contain a <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, one <fileGrp> representing GIF thumbnail images, and one <fileGrp> representing OCR full text files.

requirement: @ID="fileSec4"

Each <file> represented in the <fileSec> must have a GROUPID attribute.

This attribute will associate each file with his manifestations (representations) in other <fileSec> sections.

For example a <file> holding a TIFF image will have the same GROUPID as its provided thumbnail manifestation <file>

requirement: @ID="fileSec5"

Each <file> that has an ordered structure - i.e. physical pages and their thumbnails - should make use of the SEQ attribute to numerically indicate the order by which the physical order of pages should be displayed. The SEQ value should be consistent across the manifestation fileGrps for sibling file representations.

For example, the first master Tiff <file> image in a given <fileGrp> may have SEQ="1" and its analagous thumbnail in a different <fileGrp> should also have SEQ="1" within that respective <file> section.

requirement: @ID="fileSec6"

Any <file> element may reference any number of pertinent descriptive metadata elements within the <dmdSec> via its DMDID attribute value. (see dmdSec section above) Best practice dictates that this reference will be made at the structMap div level rather than at the fileSec level.

requirement: @ID="fileSec7"

Any <file> element may reference any number of pertinent adminstrative metadata elements within the <amdSec> via its ADMID attribute value. (see amdSec section above)

structMap:
requirement: @ID="structMap1"

A conforming METS document must contain at least one <structMap>; it may, however, contain more than one <structMap>.

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

A conforming <structMap> must contain a TYPE attribute. Supported TYPE values appear in the <controlled_vocabularies> section of this document ("logical" ,"physical", or "mixed").

requirement: @ID="structMap3"

Each <structMap> must include a LABEL attribute value.

requirement: @ID="structMap4"

Each <div> must include a LABEL attribute value.

requirement: @ID="structMap5"

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

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

requirement: @ID="structMap7"

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

An <fptr> element must either:

1) directly point to a <file> element via its FILEID attribute;

2) contain an <area> element that points to a <file> element;

3) contain a <seq> element comprising multiple <area> elements that point to the relevant <file> elements.

requirement: @ID="structMap9"

The <par> element can only be used in the PHYSICAL strcutMap.

requirement: @ID="structMap10"

Any <div> element may reference any number of pertinent descriptive metadata elements within the <dmdSec> via its DMDID attribute value. (see dmdSec section above)

requirement: @ID="structMap11"

Any <div> element may reference any number of pertinent administrative metadata elements within the <amdSec> via its ADMID attribute value. (see amdSec section above)

requirement: @ID="structMap12"

Each <div> can contain only one child node <fptr> at that level. In other words, if more than one <fptr> reference is provided at a given div level, ONLY the first <fptr> will be used.

In case more than one node is required the <div> will have a <seq> which holds the required child nodes.

requirement: @ID="structMap13"

An <fptr> element could directly contain an <area> element if only a portion of an integral file manifests the parent <div>.

This is likely to occur in either of two cases.

1) This would typically be the case when the parent <div> element represented just a segment of the entire document and the <fptr> represented ALTO OCR text. In this case, the <area> element under the <fptr> would point to the <file> element representing the ALTO OCR text document (via its FILEID attribute) and must at least indicate the starting point of the the relevant section of the referenced ALTO OCR text file via the <area> BEGIN attribute. The BEGIN attribute, in this case, would have a BETYPE of "IDREF". The <area> element might also express the end point of the relevant section of the referenced file via its END attribute, but it need not do so.

2) When a <structMap> represents a logical structure, its individual <div> elements may each be manifested by only a portion of the associated image content files represented by its child <fptr> elements. In this case, an <fptr> element representing an image content file could, but need not, contain an <area> element which specified the shape and coordinates of the relevant section of the image via the <area> element's SHAPE and COORDS attribute values.

Note that this functionality is dependent on the support for the display of the area in the relevant viewer.

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, textual, audio and video content files.

tool:
name:
ALTO
description:
head:
Requirements of the ALTO file

No default namespace is allowed in order to extract the text on the article window.

Default measurement unit is mm10, but measurement unit of pixel is also supported

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

Legal | External Link Disclaimer

Contact Us