METS: Metadata Encoding and Transmission Standard. METS is intended to provide a standardized XML format for transmission of complex digital library objects between systems. As such, it can be seen as filling a role similar to that defined for the Submission Information Package (SIP), Archival Information Package (AIP) and Dissemination Information Package (DIP) in the Reference Model for an Open Archival Information System. mets Complex Type. A METS document consists of seven possible subsidiary sections: metsHdr (METS document header), dmdSec (descriptive metadata section), amdSec (administrative metadata section), fileGrp (file inventory group), structLink (structural map linking), structMap (structural map) and behaviorSec (behaviors section). metsHdr: METS Header. Like a TEI Header, the METS Header element records metadata about the METS document itself (not the digital library object that the METS document encodes). It has two possible subsidiary elements, agent (document agent) and altRecordID (alternative Record ID).. agent: METS agent. The agent element allows for various parties and their roles with respect to the METS document to be recorded. name:The full name of the METS document agent. note: Any additional information regarding the agent's activities with respect to the METS document. ID: an optional XML ID ROLE: a required attribute specifying the role played by the agent with respect to the METS object. ROLE must have one of the following seven values: CREATOR: an agent responsible for creating the METS document EDITOR: an agent responsible for editing the METS document ARCHIVIST: an agent with archival responsibility for the METS document and/or the original sources used to create the METS object PRESERVATION: an agent responsible for preserving the METS object and/or the original sources used to create the METS object DISSEMINATOR: an agent responsible for distributing or publishing the METS object CUSTODIAN: an agent with custodial responsibility for the METS object IPOWNER: an agent with intellectual property rights in the METS object or some of its components. OTHER: an agent with other rights/responsibilities with respect to the METS object not set forth above. OTHERROLE: an optional string attribute to specify the particular role an agent plays with respect to a METS object or its sources, to be used if the ROLE attribute has a value of OTHER. TYPE: an optional attribute to specify the nature of the agent acting with respect to the METS object. It can take one of three values: INDIVIDUAL: a single, human agent ORGANIZATION: a collective entity OTHER: some other form of agent (e.g., a software agent) OTHERTYPE: an optional string to indicate the particular type of agent, to be used if a value of OTHER is indicated in the agent's TYPE attribute. altRecordID: Alternative Record ID. This element allows for documentation of alternative ID values for the METS document in addition to the primary ID stored in the OBJID attribute in the root METS element. ID: an optional XML ID value TYPE: an optional string describing the type of identifier (e.g., OCLC #, LCCN, etc.). ID: an optional XML ID value ADMID: an optional attribute providing the XML ID values for the administrative metadata sections within this METS document applicable to this METS Document. CREATEDATE: an optional dateTime specifying when the METS document was created. LASTMODDATE: an optional dateTime specifying when the METS document was last modified; RECORDSTATUS: an optional string indicating the status of the METS document, to be used mainly for internal processing purposes. dmdSec: Description Metadata Section. This section records all of the descriptive metadata for all items in the METS object (including both structural map divs and descriptive metadata for data files). Metadata can be either included in the METS hub document (mdWrap) or referenced via an identifier/locator (mdRef), a la Warwick Framework. Multiple dmdSec elements are allowed so that descriptive metadata can be recorded for each separate item within the METS object. amdSec: Administrative Metadata Section. This section records all of the administrative metadata for all items in the METS object (including structural map divs, data files, descriptive metadata sections and adminstrative metadata sections themselves), and is divided into four subsections: techMD (technical metadata), rightsMD (intellectual property rights metadata), sourceMD (analog/digital source metadata), and digiprovMD (digital provenance metadata). Each of these subsections follows the mdSecType model, so that they can either include metadata within the METS hub document (mdWrap) or reference it via an identifier/locator (mdRef). Multiple techMD, rightsMD, sourceMD and digiprovMD elements are allowed so that administrative metadata can be recorded for each separate item within the METS object. fileSec: Content File Section. The content file section records information regarding all of the data files which comprise the digital library object. fileGrp: File Group This element allows for the grouping of content files into sets (all of the master images for a work, all of the images for a particular page, etc.). ID: an optional XML ID value structMap: Structural Map. The structural map is the heart of a METS document, defining the hierarchical arrangement of a primary source document which has been digitized. This hierarchy is encoded as a tree of 'div' elements. Any given 'div' can point to another METS document via the 'mptr' element, or to a single file, to a group of files, or to segments of individual files or groups of files through the 'fptr' and subsidiary elements. structLink: Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map. behaviorSec: Behavior Section. This section records executable behaviors that are associated with content in the METS object. ID: an optional XML ID value OBJID: an optional attribute recording a primary identifier assigned to the METS document. LABEL: an optional attribute providing a title/text string identifying the document for users. TYPE: an optional string attribute describing the type of object, e.g., book, journal, stereograph, etc. PROFILE: an optional attribute providing a URI or other identifier for a METS profile to which this METS document conforms. amdSecType: Complex Type for Administrative Metadata. 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). techMD: technical metadata. The techMD element provides a wrapper around a generic metadata section, which should contain technical metadata regarding a file or files. rightsMD: intellectual property rights metadata. The rightsMD element provides a wrapper around a generic metadata section, which should contain IP rights metadata. sourceMD: source metadata. The sourceMD element provides a wrapper around a generic metadata section which should contain descriptive or administrative metadata regarding the original source materials used to create the METS object. digiprovMD: digital provenance metadata. The digiprovMD element provides a wrapper around a generic metadata section, which should contain information regarding the ultimate origin of a digital object and the derivation of its current elements. This includes recording master/derivative relationships between various files which currently represent the object, as well recording any transformations or migrations undergone by files composing the digital object subsequent to the initial digitization of an item or, in the case of born digital materials, the files' creation. In short, digiprovMD should be used to record information to allow both archival/library staff and scholars to understand what modifications have been performed to a digital object during its life cycle in order to judge how those processes might have altered or corrupted the object's ability to accurately represent the original item. ID: an optional XML ID value fileGrp: File Group. The file group is used to cluster all of the digital files composing a digital library object in a hierarchical arrangement (fileGrp is recursively defined to enable the creation of the hierarchy). Any file group may contain zero or more file elements. File elements in turn can contain one or more FLocat elements (a pointer to a file containing content for this object) and/or a FContent element (the contents of the file, in either XML or Base64 encoding). ID: an optional XML ID value. VERSDATE: an optional dateTime attribute specifying the date this version/fileGrp of the digital object was created. ADMID: an optional attribute specifying the XML ID values for administrative metadata sections in the METS document that provide information applicable to all of the files in this particular file group. USE: an optional string attribute indicating the intended use of all the files within this file group (e.g., master, reference, thumbnails for image files). structMap Complex Type The structural map (structMap) outlines a hierarchical structure for the original object being encoded, using a series of nested div elements. div: Division. 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. ID: an optional XML ID value. TYPE: an optional string attribute specifying the type of structural map provided. Typical values will be "PHYSICAL" for a map which describes the physical composition of the original work (a series with individual monographs with pages) and "LOGICAL" for one which describes the intellectual structure of the work (a monograph with TOC, forward, chapters, index., etc.); LABEL: an optional string attribute which may be used to describe the structMap to users. This is primarily useful where more than one structMap is provided for a single object (e.g., both logical and physical structMap). Div Complex Type 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". mptr: METS Pointer. The mptr element allows a div to be associated with a separate METS document containing the content corresponding with that div, rather than pointing to an internal file or file group. A typical instance of this would be the case of a METS document for a journal run, with a div elements for each individual journal issue. The div elements for the issues might point to separate METS documents for each issue, rather than having files and file groups for every issue encoded in one document. NOTE: mptr is an empty element. The location of the resource pointed to MUST be stored in the xlink:href attribute. ID: an optional XML ID value. CONTENTIDS: Content IDs for this division (equivalent to DIDL DII) fptr: File Pointer. The fptr element associates a div element with content files that represent that div. It can either point to a file directly itself, via the FILEID attribute, or it can do more complex links to content via the subsidiary area, par and seq elements. par: Parallel files. The par element should used to link a div to a set of content files when those files should be played/displayed in unison to deliver the content to the user (e.g., displaying a text transcript simultaneously with playing an audio file). A par element has two possible subsidiary elements, which should be used in different cases. In cases where each bytestream to be played in parallel can fit in a single file, you should use subsidiary <area> elements within the par element to point to those files. However, in some cases, bytestreams which should be played in parallel are too large to fit in a single file (high quality multi-track audio, or video). In those cases, you should use subsidiary <seq> elements, where each <seq> contains the files comprising a particular bytestream in the order they should be played back. So, for example, in the case where you had an audio recording which had to be split into three different, sequential files, and a text transcription of the recording in a single file, you would use a par element containing two seq elements. The first seq element would contain three area elements, one for each audio file; the second seq element would contain a single area element, for the text transcription file. seq: Sequence of files. The seq element should be used to link a div to a set of content files when those files should be played/displayed sequentially to deliver content to a user. See the seqType documentation for more details. area: file area The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files. An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text screen, image line, audio/video clip), or a two-dimensional section of a file (e.g, subsection of an image, or a subsection of the video display of a video file. See the areaType documentation for more details. ID: an optional XML ID value. FILEID: an IDREF to the file element which corresponds with the div containing this ftpr. CONTENTIDS: Content IDs for this division (equivalent to DIDL DII) ID: an optional XML ID value. ORDER: an optional integer representation of this div's order among its siblings (e.g., its sequence). ORDERLABEL: an optional string representation of this div's order among its siblings (e.g., "xii"), or a non-integer native numbering system. It is presumed that this value will still be machine-actionable (e.g., supports a page 'go to' function), and is not a replacement/substitute for the LABEL attribute. LABEL: an optional string label to describe this div to an end user viewing the document, as per a table of contents entry (NB: 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). DMDID: an optional attribute providing the XML ID values for the descriptive metadata sections within this METS document applicable to this div. ADMID: an optional attribute providing the XML ID values for the administrative metadata sections within this METS document applicable to this div. TYPE: an optional string attribute for specifying a type of division (e.g., chapter, article, page, etc.). CONTENTIDS: Content IDs for this division (equivalent to DIDL DII) xlink:label - an xlink label to be referred to by an smLink element ID: an optional XML ID value. seq: Sequence of files. The seq element should be used to link a div to a set of content files when those files should be played/displayed sequentially to deliver content to a user. Individual <area> subelements within the seq element provide the links to the files or portions thereof. ID: an optional XML ID value. areaType: Complex Type for Area linking. The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files. An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text segment, image line, audio/video clip), or a two-dimensional section of a file (e.g, subsection of an image, or a subsection of the video display of a video file. The area element has no content; all information is recorded within its various attributes. ID: an optional XML ID value. FILEID: a mandatory IDREF to the file element being pointed to by the div. SHAPE: an optional string attribute defining the shape of a two-dimensional area being referenced within a linked content file. It must have one of the following values: RECT: rectangular area CIRCLE: a circular area POLY: an irregular polygon. The SHAPE attribute should be used as in HTML 4. COORDS: an optional string attribute listing a set of visual coordinates within an image (still image or video frame). The COORDS attribute should be used as in HTML 4. BEGIN: an optional string attribute specifying the beginning location for a subpart of the referenced file. Used with the END attribute. END: an optional string attribute specifying the ending location for a subpart of the referenced file. Used with the BEGIN attribute. BETYPE: Begin/End Type. An optional attribute specifying the syntax used in the values recorded in the BEGIN and END attributes. It must have one of the following values: BYTE: a byte offset IDREF: an XML ID value for an element in the content file SMIL: a SMIL time value MIDI: a MIDI time code SMPTE-25: SMPTE time code for 25 frame/second material SMPTE-24: SMPTE time code for 24 frame/second material SMPTE-DF30: SMPTE time code for 30 frame/second drop frame material SMPTE-NDF30: SMPTE time code for 30 frame/second non-drop frame material SMPTE-DF29.97: SMPTE time code for 29.97 frame/second drop frame material SMPTE-NDF29.97: SMPTE time code for 29.97 frame/second non-drop frame material TIME: a simple time code of the form HH:MM:SS TCF: a Time code Character Format value EXTENT: an optional string attribute specifying the duration of the segment pointed to by the area element. EXTTYPE: Extent Type an option attribute specifying the syntax used for the value in the EXTENT attribute. See the BETYPE attribute for the specific values which may be used in EXTTYPE. ADMID: an optional attribute listing the XML ID values for the administrative metadata sections within the METS document that provide information regarding this area. CONTENTIDS: Content IDs for this division (equivalent to DIDL DII) structLink: Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map. structLink contains a single, repeatable element, smLink. Each smLink element indicates a hyperlink between two nodes in the structMap. The structMap nodes recorded in smLink are identified using their XML ID attribute values. smLink: structural map Link An element linking two elements in the structural map, used to indicate that a hyperlink exists between the two METS components represented by the two structural map nodes. You would use smLink, for example, to record the existence of hypertext links between web pages, if you wish to record those links' existence inside of METS. ID: an optional XML ID value. xlink:arcrole - the role of the link, as per the xlink specification. See http://www.w3.org/TR/xlink/ xlink:title - a title for the link (if needed), as per the xlink specification. See http://www.w3.org/TR/xlink/ xlink:show - see the xlink specification at http://www.w3.org/TR/xlink/ xlink:actuate - see the xlink specification at http://www.w3.org/TR/xlink/ xlink:to - the value of the label for the element in the structMap you are linking to. xlink:from - the value of the label for the element in the structMap you are linking from. ID: an optional XML ID value behaviorSecType: Behaviors Section. Behaviors are executable code which can be associated with parts of a METS object. The behaviorSec element is used to group individual behaviors within a hierarchical structure. Such grouping can be useful to organize families of behaviors together or to indicate other relationships between particular behaviors. ID: an optional XML ID value. CREATED: an optional dateTime attribute specifying when the behaviorSec was created. LABEL: an optional string attribute providing a text description of the behaviorSec. behaviorType: Complex Type for Behaviors. A behavior can be used to associate executable behaviors with content in the METS object. A behavior element has an interface definition element that represents an abstract definition of the set of behaviors represented by a particular behavior. A behavior element also has an behavior mechanism which is a module of executable code that implements and runs the behavior defined abstractly by the interface definition. interfaceDef: interface definition object. The interface definition element contains a pointer an abstract definition of a set of related behaviors. These abstract behaviors can be associated with the content of a METS object. The interface definition element will be a pointer to another object (an interface definition object). An interface definition object could be another METS object, or some other entity (e.g., a WSDL file). Ideally, an interface definition object should contain metadata that describes a set of behaviors or methods. It may also contain files that describe the intended usage of the behaviors, and possibly files that represent different expressions of the interface definition. The interfaceDef element is optional to allow for cases where an interface definition can be obtained from a behavior mechanism object (see the mechanism element of the behaviorSec). mechanism: executable mechanism. A mechanism element contains a pointer to an executable code module that implements a set of behaviors defined by an interface definition. The mechanism element will be a pointer to another object (a mechanism object). A mechanism object could be another METS object, or some other entity (e.g., a WSDL file). A mechanism object should contain executable code, pointers to executable code, or specifications for binding to network services (e.g., web services). ID: a required XML ID value for the element STRUCTID: Structural Map IDS IDREFS to structMap sections or divs within a structMap in the METS document. The content that the STRUCTID attribute points to is considered "input" to the behavior mechanism (executable) defined for the behavior. BTYPE: Behavior Type an optional string attribute providing an identifier for a given set of related behaviors. CREATED: an optional dateTime attribute specifying a date this behavior was created. LABEL: an optional string attribute providing a description of the behavior. GROUPID: an optional string attribute providing an identifier that establishes a correspondence between this behavior and other behaviors. Typically, this will be used to facilitate versioning of behaviors. ADMID: an optional attribute listing the XML ID values of administrative metadata sections within the METS document pertaining to this behavior. ID: an optional XML ID value LABEL: an optional string attribute providing a description of the object that is being linked to. mdSec (metadata section) Complex Type A generic framework for pointing to/including metadata within a METS document, a la Warwick Framework. mdRef: metadata reference. The 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: an optional XML ID value LABEL: an optional string attribute providing a label to display to the viewer of the METS document identifying the metadata XPTR: an optional string attribute for providing an xptr to a location within the file pointed to by the mdRef element, if applicable. mdWrap: metadata wrapper. The mdWrap element is a generic element used throughout the METS schema to allow the encoder to place arbitrary metadata conforming to other standards/schema within a METS document. The included metadata can either be encoded in XML, in which case it may be placed directly within the mdWrap element, or it can be Base64 encoded, and placed within a subsidiary binData element. binData: A wrapper element to contain Base64 encoded metadata. xmlData: A wrapper element to contain XML encoded metadata. ID: an optional XML ID value. LABEL: an optional string attribute providing a label to display to the viewer of the METS document identifying the metadata. ID: a required XML ID value GROUPID: an optional string attribute providing an identifier that may be used to indicate that different metadata sections may be considered as part of a single group. Two metadata sections with the same GROUPID value are to be considered part of the same group. This facility might be used, for example, to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes; ADMID: an optional attribute providing the XML ID attribute values for administrative metadata elements which apply to the current descriptive or administrative metadata. Typically used to reference preservation metadata which applies to the current metadata. CREATED: an optional dateTime attribute specifying the date and time of creation for the metadata. STATUS: an optional string attribute indicating the status of this metadata (e.g., superceded, current, etc.). file: File element. 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. FLocat: File Location. The FLocat element provides a pointer to the location of a content file. It uses the XLink syntax to provide linking information indicating the actual location of the content file, along with a few additional 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 element. ID: an optional XML ID value USE: an optional string indicating the intended use of the referenced file. FContent: file content. The FContent element is used to deliver a content file for a METS document within the METS file itself. The content file must be either Base 64 encoded, and contained within the subsidiary binData wrapper element, or consist of XML information and be contained within the subsidiary xmlData wrapper element. binData: A wrapper element used to contain a Base64 encoded file. xmlData: A wrapper element used to contain an XML encoded file. ID: an optional XML ID value USE: an optional string indicating the intended use of the embedded file. Examples might include "master", "reference", and "thumbnail" for image files. stream: component byte stream A file may be composed of one or more subsidiary streams. An MPEG4 file, for example, might contain separate audio and video streams, each of which has its own technical metadata associated with it. ID: an optional XML ID value OWNERID: an optional string attribute which may be used to provide a unique identifier (including a URI) assigned to the file which may differ from the URI used to retrieve the file. ADMID: an optional attribute used to list the XML ID attribute values for administrative metadata sections in the METS document that provide information regarding this file. DMDID: an optional attribute used to list the XML ID attribute values for descriptive metadata sections in the METS document that provide information regarding this file. ID: an optional XML ID value TRANSFORMTYPE: a type of transformation needed to render content of a file accessible (including unpacking a file into subsidiary files/streams). TRANSFORMALGORITHM: a string describing the specific decompression or decryption routine used to access the contents of this file. TRANSFORMKEY: a key to be used with the transform algorithm for accessing the file's contents. TRANSFORMBEHAVIOR: an IDREF to a behavior element for this transformation ID: an XML ID value. SEQ: an optional integer indicating the sequence of this file relative to the others in its file group. OWNERID: an optional string attribute which may be used to provide a unique identifier (including a URI) assigned to the file which may differ from the URI used to retrieve the file. ADMID: an optional attribute used to list the XML ID attribute values for administrative metadata sections in the METS document that provide information regarding this file. DMDID: an optional attribute used to list the XML ID attribute values for descriptive metadata sections in the METS document that provide information regarding this file. GROUPID: an optional string attribute which may be used to record an identifier that establishes a correspondence between this file and files in other file groups. For example, a master image in one file group would share the same GROUPID value with a reference copy in a second file group and a thumbnail image in a third file group. USE: an optional string attribute indicating the intended use of this file (e.g., "master", "reference", "thumbnail" for image files). MDTYPE: a required attribute specifying the yype of metadata being pointed at (e.g., MARC, EAD, etc.). 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 OTHER: metadata in a format not specified above. OTHERMDTYPE: Other Metadata Type an optional string which may be used to record the particular form of metadata referenced by this element when the MDTYPE attribute has a value of "OTHER". LOCTYPE: Location Type the type of locator used to reference a file. It must have one of the following values: ARK: Archival Resource Key URN: Uniform Resource Name URL: Uniform Resource Locator PURL: Persistent URL HANDLE: a CNRI Handle DOI: A Digital Object Identifier OTHER: a form of locator not specified above. OTHERLOCTYPE: an optional string attribute used to indicate an alternative LOCTYPE if the LOCTYPE attribute itself has a value of "OTHER"; MIMETYPE: an optional string attribute providing the MIME type for the file. SIZE: an optional long integer specifying the size of the file in bytes. CREATED: an optional dateTime providing the date of creation for the file. CHECKSUM: an optional string attribute providing a checksum value for the included file. CHECKSUMTYPE: an optional attribute specifying the checksum algorithm used to produce the value contained in the CHECKSUM attribute. CHECKSUMTYPE must contain one of the following values: HAVAL MD5 SHA-1 SHA-256 SHA-384 SHA-512 TIGER WHIRLPOOL