A descriptive metadata section
<dmdSec> records descriptive metadata pertaining to the METS
object as a whole or one of its components. The <dmdSec> element
conforms to same generic datatype as the <techMD>,
<rightsMD>, <sourceMD> and <digiprovMD> elements, and
supports the same sub-elements and attributes. A descriptive metadata
element can either wrap the metadata (mdWrap) or reference it in an
external location (mdRef) or both. METS allows multiple <dmdSec>
elements; and descriptive metadata can be associated with any METS
element that supports a DMDID attribute. Descriptive metadata can be
expressed according to many current description standards (i.e., MARC,
MODS, Dublin Core, TEI Header, EAD, VRA, FGDC, DDI) or a locally
produced XML schema.
The administrative metadata section
<amdSec> contains the administrative metadata pertaining to the
digital object, its components and any original source material from
which the digital object is derived. The <amdSec> is separated
into four sub-sections that accommodate technical metadata (techMD),
intellectual property rights (rightsMD), analog/digital source metadata
(sourceMD), and digital provenance metadata (digiprovMD). Each of these
subsections can either wrap the metadata (mdWrap) or reference it in an
external location (mdRef) or both. Multiple instances of the
<amdSec> element can occur within a METS document and multiple
instances of its subsections can occur in one <amdSec> element.
This allows considerable flexibility in the structuring of the
administrative metadata. METS does not define a vocabulary or syntax for
encoding administrative metadata. Administrative metadata can be
expressed within the amdSec sub-elements according to many current
community defined standards, or locally produced XML schemas.
The structural map section
<structMap> is the heart of a METS document. It provides a means
for organizing the digital content represented by the <file>
elements in the <fileSec> of the METS document into a coherent
hierarchical structure. Such a hierarchical structure can be presented
to users to facilitate their comprehension and navigation of the digital
content. It can further be applied to any purpose requiring an
understanding of the structural relationship of the content files or
parts of the content files. The organization may be specified to any
level of granularity (intellectual and or physical) that is desired.
Since the <structMap> element is repeatable, more than one
organization can be applied to the digital content represented by the
METS document. The hierarchical structure specified by a
<structMap> is encoded as a tree of nested <div> elements. A
<div> element may directly point to content via child file pointer
<fptr> elements (if the content is represented in the
<fileSec<) or child METS pointer <mptr> elements (if the
content is represented by an external METS document). The <fptr>
element may point to a single whole <file> element that manifests
its parent <div<, or to part of a <file> that manifests its
<div<. It can also point to multiple files or parts of files that
must be played/displayed either in sequence or in parallel to reveal its
structural division. In addition to providing a means for organizing
content, the <structMap> provides a mechanism for linking content
at any hierarchical level with relevant descriptive and administrative
metadata.
mdSecType: Complex Type for Metadata Sections A generic
framework for pointing to/including metadata within a METS document, a la Warwick
Framework.
The metadata reference element <mdRef>
element is a generic element used throughout the METS schema to provide a
pointer to metadata which resides outside the METS document. NB:
<mdRef> is an empty element. The location of the metadata must be
recorded in the xlink:href attribute, supplemented by the XPTR attribute as
needed.
ID (ID/O): This attribute uniquely
identifies the element within the METS document, and would allow the
element to be referenced unambiguously from another element or
document via an IDREF or an XPTR. For more information on using ID
attributes for internal and external linking see Chapter 4 of the
METS Primer.
LABEL (string/O): Provides a label to
display to the viewer of the METS document that identifies the
associated metadata.
XPTR (string/O): Locates the point
within a file to which the <mdRef> element refers, if
applicable.
A metadata wrapper element <mdWrap>
provides a wrapper around metadata embedded within a METS document. The
element is repeatable. Such metadata can be in one of two forms: 1)
XML-encoded metadata, with the XML-encoding identifying itself as belonging
to a namespace other than the METS document namespace. 2) Any arbitrary
binary or textual form, PROVIDED that the metadata is Base64 encoded and
wrapped in a <binData> element within the internal descriptive
metadata element.
The binary data wrapper element
<binData> is used to contain Base64 encoded metadata.
The xml data wrapper element
<xmlData> is used to contain XML encoded metadata. The
content of an <xmlData> element can be in any namespace or
in no namespace. As permitted by the XML Schema Standard, the
processContents attribute value for the metadata in an
<xmlData> is set to “lax”. Therefore, if the source schema
and its location are identified by means of an XML
schemaLocation attribute, then an XML processor will validate
the elements for which it can find declarations. If a source
schema is not identified, or cannot be found at the specified
schemaLocation, then an XML validator will check for
well-formedness, but otherwise skip over the elements appearing
in the <xmlData> element.
ID (ID/O): This attribute uniquely
identifies the element within the METS document, and would allow the
element to be referenced unambiguously from another element or
document via an IDREF or an XPTR. For more information on using ID
attributes for internal and external linking see Chapter 4 of the
METS Primer.
LABEL: an optional string attribute
providing a label to display to the viewer of the METS document
identifying the metadata.
ID (ID/R): This attribute uniquely identifies the
element within the METS document, and would allow the element to be referenced
unambiguously from another element or document via an IDREF or an XPTR. The ID
attribute on the <dmdSec>, <techMD>, <sourceMD>,
<rightsMD> and <digiprovMD> elements (which are all of mdSecType) is
required, and its value should be referenced from one or more DMDID attributes
(when the ID identifies a <dmdSec> element) or ADMID attributes (when the
ID identifies a <techMD>, <sourceMD>, <rightsMD> or
<digiprovMD> element) that are associated with other elements in the METS
document. The following elements support references to a <dmdSec> via a
DMDID attribute: <file>, <stream>, <div>. The following
elements support references to <techMD>, <sourceMD>,
<rightsMD> and <digiprovMD> elements via an ADMID attribute:
<metsHdr>, <dmdSec>, <techMD>, <sourceMD>,
<rightsMD>, <digiprovMD>, <fileGrp>, <file>,
<stream>, <div>, <area>, <behavior>. For more
information on using ID attributes for internal and external linking see Chapter
4 of the METS Primer.
GROUPID (string/O): This identifier is used to
indicate that different metadata sections may be considered as part of a group.
Two metadata sections with the same GROUPID value are to be considered part of
the same group. For example this facility might be used to group changed
versions of the same metadata if previous versions are maintained in a file for
tracking purposes.
ADMID (IDREFS/O): Contains the ID attribute values
of the <digiprovMD>, <techMD>, <sourceMD> and/or
<rightsMD> elements within the <amdSec> of the METS document that
contain administrative metadata pertaining to the current mdSecType element.
Typically used in this context to reference preservation metadata (digiprovMD)
which applies to the current metadata. For more information on using METS IDREFS
and IDREF type attributes for internal linking, see Chapter 4 of the METS
Primer.
CREATED (dateTime/O): Specifies the date and time
of creation for the metadata.
STATUS (string/O): Indicates the status of this
metadata (e.g., superseded, current, etc.).
structMapType: Complex Type for Structural Maps The
structural map (structMap) outlines a hierarchical structure for the original object
being encoded, using a series of nested div elements.
The structural divisions of the hierarchical
organization provided by a <structMap> are represented by division
<div> elements, which can be nested to any depth. Each <div>
element can represent either an intellectual (logical) division or a
physical division. Every <div> node in the structural map hierarchy
may be connected (via subsidiary <mptr> or <fptr> elements) to
content files which represent that div's portion of the whole document.
ID (ID/O): This attribute uniquely identifies the
element within the METS document, and would allow the element to be referenced
unambiguously from another element or document via an IDREF or an XPTR. For more
information on using ID attributes for internal and external linking see Chapter
4 of the METS Primer.
TYPE (string/O): Identifies the type of structure
represented by the <structMap>. For example, a <structMap> that
represented a purely logical or intellectual structure could be assigned a TYPE
value of “logical” whereas a <structMap> that represented a purely
physical structure could be assigned a TYPE value of “physical”. However, the
METS schema neither defines nor requires a common vocabulary for this attribute.
A METS profile, however, may well constrain the values for the <structMap>
TYPE.
LABEL (string/O): Describes the <structMap>
to viewers of the METS document. This would be useful primarily where more than
one <structMap> is provided for a single object. A descriptive LABEL
value, in that case, could clarify to users the purpose of each of the available
structMaps.
divType: Complex Type for Divisions The METS standard
represents a document structurally as a series of nested div elements, that is, as a
hierarchy (e.g., a book, which is composed of chapters, which are composed of
subchapters, which are composed of text). Every div node in the structural map
hierarchy may be connected (via subsidiary mptr or fptr elements) to content files
which represent that div's portion of the whole document. SPECIAL NOTE REGARDING DIV
ATTRIBUTE VALUES: to clarify the differences between the ORDER, ORDERLABEL, and
LABEL attributes for the <div> element, imagine a text with 10 roman numbered
pages followed by 10 arabic numbered pages. Page iii would have an ORDER of "3", an
ORDERLABEL of "iii" and a LABEL of "Page iii", while page 3 would have an ORDER of
"13", an ORDERLABEL of "3" and a LABEL of "Page 3".
The <fptr> or file pointer element
represents digital content that manifests its parent <div> element.
The content represented by an <fptr> element must consist of integral
files or parts of files that are represented by <file> elements in the
<fileSec>. Via its FILEID attribute, an <fptr> may point
directly to a single integral <file> element that manifests a
structural division. However, an <fptr> element may also govern an
<area> element, a <par>, or a <seq> which in turn would
point to the relevant file or files. A child <area> element can point
to part of a <file> that manifests a division, while the <par>
and <seq> elements can point to multiple files or parts of files that
together manifest a division. More than one <fptr> element can be
associated with a <div> element. Typically sibling <fptr>
elements represent alternative versions, or manifestations, of the same
content
ID (ID/O): This attribute uniquely
identifies the element within the METS document, and would allow the
element to be referenced unambiguously from another element or
document via an IDREF or an XPTR. For more information on using ID
attributes for internal and external linking see Chapter 4 of the
METS Primer.
FILEID (IDREF/O): An optional attribute
that provides the XML ID identifying the <file> element that
links to and/or contains the digital content represented by the
<fptr>. A <fptr> element should only have a FILEID
attribute value if it does not have a child <area>,
<par> or <seq> element. If it has a child element, then
the responsibility for pointing to the relevant content falls to
this child element or its descendants.
CONTENTIDS (URI/O): Content IDs for the
content represented by the <fptr> (equivalent to DIDL DII or
Digital Item Identifier, a unique external ID).
ID (ID/O): This attribute uniquely identifies the
element within the METS document, and would allow the element to be referenced
unambiguously from another element or document via an IDREF or an XPTR. For more
information on using ID attributes for internal and external linking see Chapter
4 of the METS Primer.
ORDER (integer/O): A representation of the div's
order among its siblings (e.g., its absolute, numeric sequence). For an example,
and clarification of the distinction between ORDER and ORDERLABEL, see the
description of the ORDERLABEL attribute.
LABEL (string/O): An attribute used, for example,
to identify a <div> to an end user viewing the document. Thus a
hierarchical arrangement of the <div> LABEL values could provide a table
of contents to the digital content represented by a METS document and facilitate
the users’ navigation of the digital object. Note that a <div> LABEL
should be specific to its level in the structural map. In the case of a book
with chapters, the book <div> LABEL should have the book title and the
chapter <div>; LABELs should have the individual chapter titles, rather
than having the chapter <div> LABELs combine both book title and chapter
title . For further of the distinction between LABEL and ORDERLABEL see the
description of the ORDERLABEL attribute.
DMDID (IDREFS/O): Contains the ID attribute values
identifying the <dmdSec>, elements in the METS document that contain or
link to descriptive metadata pertaining to the structural division represented
by the current <div> element. For more information on using METS IDREFS
and IDREF type attributes for internal linking, see Chapter 4 of the METS
Primer.
TYPE (string/O): An attribute that specifies the
type of structural division that the <div> element represents. Possible
<div> TYPE attribute values include: chapter, article, page, track,
segment, section etc. METS places no constraints on the possible TYPE values.
Suggestions for controlled vocabularies for TYPE may be found on the METS
website.
TYPE : types d'entités importables défini dans
Lodel (types de la classe texte + types de la classe fichiers)
xlink:label - an xlink label to be referred to by
an smLink element
amdSecType: Complex Type for Administrative Metadata
Sections The administrative metadata section consists of four possible subsidiary
sections: techMD (technical metadata for text/image/audio/video files), rightsMD
(intellectual property rights metadata), sourceMD (analog/digital source metadata),
and digiprovMD (digital provenance metadata, that is, the history of
migrations/translations performed on a digital library object from it's original
digital capture/encoding).
A digital provenance metadata element
<digiprovMD> can be used to record any preservation-related actions
taken on the various files which comprise a digital object (e.g., those
subsequent to the initial digitization of the files such as transformation
or migrations) or, in the case of born digital materials, the files’
creation. In short, digital provenance should be used to record information
that allows both archival/library staff and scholars to understand what
modifications have been made to a digital object and/or its constituent
parts during its life cycle. This information can then be used to judge how
those processes might have altered or corrupted the object’s ability to
accurately represent the original item. One might, for example, record
master derivative relationships and the process by which those derivations
have been created. Or the <digiprovMD> element could contain
information regarding the migration/transformation of a file from its
original digitization (e.g., OCR, TEI, etc.,)to its current incarnation as a
digital object (e.g., JPEG2000). The <digiprovMD> element conforms to
same generic datatype as the <dmdSec>, <techMD>,
<rightsMD>, and <sourceMD> elements, and supports the same
sub-elements and attributes. A digital provenance metadata element can
either wrap the metadata (mdWrap) or reference it in an external location
(mdRef) or both. METS allows multiple <digiprovMD> elements; and
digital provenance metadata can be associated with any METS element that
supports an ADMID attribute. Digital provenance metadata can be expressed
according to current digital provenance description standards (such as
PREMIS) or a locally produced XML schema.
ID (ID/O): This attribute uniquely identifies the
element within the METS document, and would allow the element to be referenced
unambiguously from another element or document via an IDREF or an XPTR. For more
information on using ID attributes for internal and external linking see Chapter
4 of the METS Primer.
The file element <file> provides access
to the content files for the digital object being described by the METS
document. A <file> element may contain one or more <FLocat>
elements which provide pointers to a content file and/or a <FContent>
element which wraps an encoded version of the file. Embedding files using
<FContent> can be a valuable feature for exchanging digital objects
between repositories or for archiving versions of digital objects for
off-site storage. All <FLocat> and <FContent> elements should
identify and/or contain identical copies of a single file. The <file>
element is recursive, thus allowing sub-files or component files of a larger
file to be listed in the inventory. Alternatively, by using the
<stream> element, a smaller component of a file or of a related file
can be placed within a <file> element. Finally, by using the
<transformFile> element, it is possible to include within a
<file> element a different version of a file that has undergone a
transformation for some reason, such as format migration.
ID (ID/O): This attribute uniquely identifies the
element within the METS document, and would allow the element to be referenced
unambiguously from another element or document via an IDREF or an XPTR. For more
information on using ID attributes for internal and external linking see Chapter
4 of the METS Primer.
fileType: Complex Type for Files The file element
provides access to content files for a METS object. A file element may contain one
or more FLocat elements, which provide pointers to a content file, and/or an
FContent element, which wraps an encoded version of the file. Note that ALL FLocat
and FContent elements underneath a single file element should identify/contain
identical copies of a single file.
The file location element <FLocat>
provides a pointer to the location of a content file. It uses the XLink
reference syntax to provide linking information indicating the actual
location of the content file, along with other attributes specifying
additional linking information. NOTE: <FLocat> is an empty element.
The location of the resource pointed to MUST be stored in the xlink:href
attribute.
ID (ID/O): This attribute uniquely
identifies the element within the METS document, and would allow the
element to be referenced unambiguously from another element or
document via an IDREF or an XPTR. For more information on using ID
attributes for internal and external linking see Chapter 4 of the
METS Primer.
USE (string/O): A tagging attribute to
indicate the intended use of the specific copy of the file
represented by the <FLocat> element (e.g., service master,
archive master). A USE attribute can be expressed at
the<fileGrp> level, the <file> level, the <FLocat>
level and/or the <FContent> level. A USE attribute value at
the <fileGrp> level should pertain to all of the files in the
<fileGrp>. A USE attribute at the <file> level should
pertain to all copies of the file as represented by subsidiary
<FLocat> and/or <FContent> elements. A USE attribute at
the <FLocat> or <FContent> level pertains to the
particular copy of the file that is either referenced
(<FLocat>) or wrapped (<FContent>).
ID (ID/R): This attribute uniquely identifies the
element within the METS document, and would allow the element to be referenced
unambiguously from another element or document via an IDREF or an XPTR.
Typically, the ID attribute value on a <file> element would be referenced
from one or more FILEID attributes (which are of type IDREF) on
<fptr>and/or <area> elements within the <structMap>. Such
references establish links between structural divisions (<div> elements)
and the specific content files or parts of content files that manifest them. For
more information on using ID attributes for internal and external linking see
Chapter 4 of the METS Primer.
SEQ (integer/O): Indicates the sequence of this
<file> relative to the others in its <fileGrp>.
DMDID (IDREFS/O): Contains the ID attribute values
identifying the <dmdSec>, elements in the METS document that contain or
link to descriptive metadata pertaining to the content file represented by the
current <file> element. For more information on using METS IDREFS and
IDREF type attributes for internal linking, see Chapter 4 of the METS Primer.
GROUPID (string/O): An identifier that establishes
a correspondence between this file and files in other file groups. Typically,
this will be used to associate a master file in one file group with the
derivative files made from it in other file groups.
MDTYPE (string/R): Is used to indicate the type of
the associated metadata. It must have one of the following values: MARC: any
form of MARC record MODS: metadata in the Library of Congress MODS format EAD:
Encoded Archival Description finding aid DC: Dublin Core NISOIMG: NISO Technical
Metadata for Digital Still Images LC-AV: technical metadata specified in the
Library of Congress A/V prototyping project VRA: Visual Resources Association
Core TEIHDR: Text Encoding Initiative Header DDI: Data Documentation Initiative
FGDC: Federal Geographic Data Committee metadata LOM: Learning Object Model
PREMIS: PREservation Metadata: Implementation Strategies PREMIS:OBJECT: PREMIS
Object entiry PREMIS:AGENT: PREMIS Agent entity PREMIS:RIGHTS: PREMIS Rights
entity PREMIS:EVENT: PREMIS Event entity TEXTMD: textMD Technical metadata for
text METSRIGHTS: Rights Declaration Schema ISO 19115:2003 NAP: North American
Profile of ISO 19115:2003 descriptive metadata EAC-CPF: Encoded Archival Context
- Corporate Bodies, Persons, and Families OTHER: metadata in a format not
specified above
OTHERMDTYPE (string/O): Specifies the form of
metadata in use when the value OTHER is indicated in the MDTYPE attribute.
MDTYPEVERSION(string/O): Provides a means for
recording the version of the type of metadata (as recorded in the MDTYPE or
OTHERMDTYPE attribute) that is being used. This may represent the version of the
underlying data dictionary or metadata model rather than a schema version.
MIMETYPE (string/O): The IANA MIME media type for
the associated file or wrapped content. Some values for this attribute can be
found on the IANA website.
SIZE (long/O): Specifies the size in bytes of the
associated file or wrapped content.
CREATED (dateTime/O): Specifies the date and time
of creation for the associated file or wrapped content.
CHECKSUM (string/O): Provides a checksum value for
the associated file or wrapped content.
CHECKSUMTYPE (enumerated string/O): Specifies the
checksum algorithm used to produce the value contained in the CHECKSUM
attribute. CHECKSUMTYPE must contain one of the following values: Adler-32 CRC32
HAVAL MD5 MNP SHA-1 SHA-256 SHA-384 SHA-512 TIGER WHIRLPOOL
LOCTYPE (string/R): Specifies the locator type used
in the xlink:href attribute. Valid values for LOCTYPE are: ARK URN URL PURL
HANDLE DOI OTHER
OTHERLOCTYPE (string/O): Specifies the locator type
when the value OTHER is used in the LOCTYPE attribute. Although optional, it is
strongly recommended when OTHER is used.