Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Model
Properties
Source
Used by
Element metsType / metsHdr
Namespace http://www.loc.gov/METS/
Annotations
 
The mets header element <metsHdr> captures metadata about the METS document itself, not the digital object the METS document encodes. Although it records a more limited set of metadata, it is very similar in function and purpose to the headers employed in other schema such as the Text Encoding Initiative (TEI) or in the Encoded Archival Description (EAD).
Diagram
Properties
content complex
minOccurs 0
Model
Children agent, altRecordID, metsDocumentID
Instance
 
<metsHdr ADMID="" CREATEDATE="" ID="" LASTMODDATE="" RECORDSTATUS="" xmlns="http://www.loc.gov/METS/">
  <agent ID="" OTHERROLE="" OTHERTYPE="" ROLE="" TYPE="">{0,unbounded}</agent>
  <altRecordID ID="" TYPE="">{0,unbounded}</altRecordID>
  <metsDocumentID ID="" TYPE="">{0,1}</metsDocumentID>
</metsHdr>
Attributes
QName Type Use Annotation
ADMID xsd:IDREFS optional 
ADMID (IDREFS/O): Contains the ID attribute values of the <techMD>, <sourceMD>, <rightsMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain administrative metadata pertaining to the METS document itself.  For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer.
CREATEDATE xsd:dateTime optional 
CREATEDATE (dateTime/O): Records the date/time the METS document was created.
ID xsd:ID optional 
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.
LASTMODDATE xsd:dateTime optional 
LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.
RECORDSTATUS xsd:string optional 
RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="metsHdr" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The mets header element <metsHdr> captures metadata about the METS document itself, not the digital object the METS document encodes. Although it records a more limited set of metadata, it is very similar in function and purpose to the headers employed in other schema such as the Text Encoding Initiative (TEI) or in the Encoded Archival Description (EAD).</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="agent" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">agent: The agent element <agent> provides for various parties and their roles with respect to the METS record to be documented.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="name" type="xsd:string">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the document agent.</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:anyAttribute namespace="##other" processContents="lax"/>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
          <xsd:attribute name="ID" type="xsd:ID" use="optional">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">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.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="ROLE" use="required">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS record. The allowed values are: CREATOR: The person(s) or institution(s) responsible for the METS document. EDITOR: The person(s) or institution(s) that prepares the metadata for encoding. ARCHIVIST: The person(s) or institution(s) responsible for the document/collection. PRESERVATION: The person(s) or institution(s) responsible for preservation functions. DISSEMINATOR: The person(s) or institution(s) responsible for dissemination functions. CUSTODIAN: The person(s) or institution(s) charged with the oversight of a document/collection. IPOWNER: Intellectual Property Owner: The person(s) or institution holding copyright, trade or service marks or other intellectual property rights for the object. OTHER: Use OTHER if none of the preceding values pertains and clarify the type and location specifier being used in the OTHERROLE attribute (see below).</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:enumeration value="CREATOR"/>
                <xsd:enumeration value="EDITOR"/>
                <xsd:enumeration value="ARCHIVIST"/>
                <xsd:enumeration value="PRESERVATION"/>
                <xsd:enumeration value="DISSEMINATOR"/>
                <xsd:enumeration value="CUSTODIAN"/>
                <xsd:enumeration value="IPOWNER"/>
                <xsd:enumeration value="OTHER"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:attribute>
          <xsd:attribute name="OTHERROLE" type="xsd:string" use="optional">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">OTHERROLE (string/O): Denotes a role not contained in the allowed values set if OTHER is indicated in the ROLE attribute.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="TYPE" use="optional">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. It must be one of the following values: INDIVIDUAL: Use if an individual has served as the agent. ORGANIZATION: Use if an institution, corporate body, association, non-profit enterprise, government, religious body, etc. has served as the agent. OTHER: Use OTHER if none of the preceding values pertain and clarify the type of agent specifier being used in the OTHERTYPE attribute</xsd:documentation>
            </xsd:annotation>
            <xsd:simpleType>
              <xsd:restriction base="xsd:string">
                <xsd:enumeration value="INDIVIDUAL"/>
                <xsd:enumeration value="ORGANIZATION"/>
                <xsd:enumeration value="OTHER"/>
              </xsd:restriction>
            </xsd:simpleType>
          </xsd:attribute>
          <xsd:attribute name="OTHERTYPE" type="xsd:string" use="optional">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">OTHERTYPE (string/O): Specifies the type of agent when the value OTHER is indicated in the TYPE attribute.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="altRecordID" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">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.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type (e.g., OCLC record number, LCCN, etc.).</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="metsDocumentID" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself. This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="ID" type="xsd:ID" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">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.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">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.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="ADMID" type="xsd:IDREFS" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ADMID (IDREFS/O): Contains the ID attribute values of the <techMD>, <sourceMD>, <rightsMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain administrative metadata pertaining to the METS document itself. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="CREATEDATE" type="xsd:dateTime" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">CREATEDATE (dateTime/O): Records the date/time the METS document was created.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="LASTMODDATE" type="xsd:dateTime" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="RECORDSTATUS" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
  </xsd:complexType>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / metsHdr / agent
Namespace http://www.loc.gov/METS/
Annotations
 
agent: 
The agent element <agent> provides for various parties and their roles with respect to the METS record to be documented.
Diagram
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children name, note
Instance
 
<agent ID="" OTHERROLE="" OTHERTYPE="" ROLE="" TYPE="" xmlns="http://www.loc.gov/METS/">
  <name>{1,1}</name>
  <note>{0,unbounded}</note>
</agent>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
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.
OTHERROLE xsd:string optional 
OTHERROLE (string/O): Denotes a role not contained in the allowed values set if OTHER is indicated in the ROLE attribute.
OTHERTYPE xsd:string optional 
OTHERTYPE (string/O): Specifies the type of agent when the value OTHER is indicated in the TYPE attribute.
ROLE restriction of xsd:string required 
ROLE (string/R): Specifies the function of the agent with respect to the METS record. The allowed values are:
CREATOR: The person(s) or institution(s) responsible for the METS document.
EDITOR: The person(s) or institution(s) that prepares the metadata for encoding.
ARCHIVIST: The person(s) or institution(s) responsible for the document/collection.
PRESERVATION: The person(s) or institution(s) responsible for preservation functions.
DISSEMINATOR: The person(s) or institution(s) responsible for dissemination functions.
CUSTODIAN: The person(s) or institution(s) charged with the oversight of a document/collection.
IPOWNER: Intellectual Property Owner: The person(s) or institution holding copyright, trade or service marks or other intellectual property rights for the object.
OTHER: Use OTHER if none of the preceding values pertains and clarify the type and location specifier being used in the OTHERROLE attribute (see below).
TYPE restriction of xsd:string optional 
TYPE (string/O): is used to specify the type of AGENT. It must be one of the following values:
INDIVIDUAL: Use if an individual has served as the agent.
ORGANIZATION: Use if an institution, corporate body, association, non-profit enterprise, government, religious body, etc. has served as the agent.
OTHER: Use OTHER if none of the preceding values pertain and clarify the type of agent specifier being used in the OTHERTYPE attribute
Source
 
<xsd:element name="agent" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">agent: The agent element <agent> provides for various parties and their roles with respect to the METS record to be documented.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="name" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the document agent.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:anyAttribute namespace="##other" processContents="lax"/>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">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.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="ROLE" use="required">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS record. The allowed values are: CREATOR: The person(s) or institution(s) responsible for the METS document. EDITOR: The person(s) or institution(s) that prepares the metadata for encoding. ARCHIVIST: The person(s) or institution(s) responsible for the document/collection. PRESERVATION: The person(s) or institution(s) responsible for preservation functions. DISSEMINATOR: The person(s) or institution(s) responsible for dissemination functions. CUSTODIAN: The person(s) or institution(s) charged with the oversight of a document/collection. IPOWNER: Intellectual Property Owner: The person(s) or institution holding copyright, trade or service marks or other intellectual property rights for the object. OTHER: Use OTHER if none of the preceding values pertains and clarify the type and location specifier being used in the OTHERROLE attribute (see below).</xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:enumeration value="CREATOR"/>
          <xsd:enumeration value="EDITOR"/>
          <xsd:enumeration value="ARCHIVIST"/>
          <xsd:enumeration value="PRESERVATION"/>
          <xsd:enumeration value="DISSEMINATOR"/>
          <xsd:enumeration value="CUSTODIAN"/>
          <xsd:enumeration value="IPOWNER"/>
          <xsd:enumeration value="OTHER"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
    <xsd:attribute name="OTHERROLE" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">OTHERROLE (string/O): Denotes a role not contained in the allowed values set if OTHER is indicated in the ROLE attribute.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="TYPE" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. It must be one of the following values: INDIVIDUAL: Use if an individual has served as the agent. ORGANIZATION: Use if an institution, corporate body, association, non-profit enterprise, government, religious body, etc. has served as the agent. OTHER: Use OTHER if none of the preceding values pertain and clarify the type of agent specifier being used in the OTHERTYPE attribute</xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:enumeration value="INDIVIDUAL"/>
          <xsd:enumeration value="ORGANIZATION"/>
          <xsd:enumeration value="OTHER"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
    <xsd:attribute name="OTHERTYPE" type="xsd:string" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">OTHERTYPE (string/O): Specifies the type of agent when the value OTHER is indicated in the TYPE attribute.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / metsHdr / agent / name
Namespace http://www.loc.gov/METS/
Annotations
 
The element <name> can be used to record the full name of the document agent.
Diagram
Type xsd:string
Properties
content simple
Source
 
<xsd:element name="name" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the document agent.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / metsHdr / agent / note
Namespace http://www.loc.gov/METS/
Annotations
 
The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:anyAttribute namespace="##other" processContents="lax"/>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / metsHdr / altRecordID
Namespace http://www.loc.gov/METS/
Annotations
 
The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
ID xsd:ID optional 
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 xsd:string optional 
TYPE (string/O): A description of the identifier type (e.g., OCLC record number, LCCN, etc.).
Source
 
<xsd:element name="altRecordID" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">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.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TYPE" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type (e.g., OCLC record number, LCCN, etc.).</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / metsHdr / metsDocumentID
Namespace http://www.loc.gov/METS/
Annotations
 
The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself.  This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.
Diagram
Type extension of xsd:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use Annotation
ID xsd:ID optional 
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 xsd:string optional 
TYPE (string/O): A description of the identifier type.
Source
 
<xsd:element name="metsDocumentID" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself. This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">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.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="TYPE" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / dmdSec
Namespace http://www.loc.gov/METS/
Annotations
 
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.
Diagram
Type mdSecType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children mdRef, mdWrap
Instance
 
<dmdSec ADMID="" CREATED="" GROUPID="" ID="" STATUS="" xmlns="http://www.loc.gov/METS/">
  <mdRef xlink:actuate="" xlink:arcrole="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" xlink:href="" ID="" LABEL="" LOCTYPE="" MDTYPE="" MDTYPEVERSION="" MIMETYPE="" OTHERLOCTYPE="" OTHERMDTYPE="" xlink:role="" xlink:show="" SIZE="" xlink:title="" xlink:type="simple" XPTR="">{0,1}</mdRef>
  <mdWrap CHECKSUM="" CHECKSUMTYPE="" CREATED="" ID="" LABEL="" MDTYPE="" MDTYPEVERSION="" MIMETYPE="" OTHERMDTYPE="" SIZE="">{0,1}</mdWrap>
</dmdSec>
Attributes
QName Type Use Annotation
ADMID xsd:IDREFS optional 
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 xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the metadata.
GROUPID xsd:string optional 
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.
ID xsd:ID required 
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.
STATUS xsd:string optional 
STATUS (string/O): Indicates the status of this metadata (e.g., superseded, current, etc.).
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="dmdSec" type="mdSecType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / amdSec
Namespace http://www.loc.gov/METS/
Annotations
 
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.
Diagram
Type amdSecType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children digiprovMD, rightsMD, sourceMD, techMD
Instance
 
<amdSec ID="" xmlns="http://www.loc.gov/METS/">
  <techMD ADMID="" CREATED="" GROUPID="" ID="" STATUS="">{0,unbounded}</techMD>
  <rightsMD ADMID="" CREATED="" GROUPID="" ID="" STATUS="">{0,unbounded}</rightsMD>
  <sourceMD ADMID="" CREATED="" GROUPID="" ID="" STATUS="">{0,unbounded}</sourceMD>
  <digiprovMD ADMID="" CREATED="" GROUPID="" ID="" STATUS="">{0,unbounded}</digiprovMD>
</amdSec>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
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.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="amdSec" type="amdSecType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / fileSec
Namespace http://www.loc.gov/METS/
Annotations
 
The overall purpose of the content file section element <fileSec> is to provide an inventory of and the location for the content files that comprise the digital object being described in the METS document.
Diagram
Properties
content complex
minOccurs 0
Model
Children fileGrp
Instance
 
<fileSec ID="" xmlns="http://www.loc.gov/METS/">
  <fileGrp ADMID="" ID="" USE="" VERSDATE="">{1,unbounded}</fileGrp>
</fileSec>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
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.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="fileSec" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The overall purpose of the content file section element <fileSec> is to provide an inventory of and the location for the content files that comprise the digital object being described in the METS document.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="fileGrp" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A sequence of file group elements <fileGrp> can be used group the digital files comprising the content of a METS object either into a flat arrangement or, because each file group element can itself contain one or more file group elements, into a nested (hierarchical) arrangement. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as: -- one <fileGrp> for the thumbnails of the images -- one <fileGrp> for the higher resolution JPEGs of the image -- one <fileGrp> for the master archival TIFFs of the images For a text resource with a variety of content file types one might group the content files at the highest level by type, and then use the <fileGrp> element’s nesting capabilities to subdivide a <fileGrp> by format within the type, such as: -- one <fileGrp> for all of the page images with nested <fileGrp> elements for each image format/resolution (tiff, jpeg, gif) -- one <fileGrp> for a PDF version of all the pages of the document -- one <fileGrp> for a TEI encoded XML version of the entire document or each of its pages. A <fileGrp> may contain zero or more <fileGrp> elements and or <file> elements.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:complexContent>
            <xsd:extension base="fileGrpType"/>
          </xsd:complexContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="ID" type="xsd:ID" use="optional">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">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.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
  </xsd:complexType>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / fileSec / fileGrp
Namespace http://www.loc.gov/METS/
Annotations
 
A sequence of file group elements <fileGrp> can be used group the digital files comprising the content of a METS object either into a flat arrangement or, because each file group element can itself contain one or more  file group elements,  into a nested (hierarchical) arrangement. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as:
-- one <fileGrp> for the thumbnails of the images
-- one <fileGrp> for the higher resolution JPEGs of the image 
-- one <fileGrp> for the master archival TIFFs of the images 
For a text resource with a variety of content file types one might group the content files at the highest level by type,  and then use the <fileGrp> element’s nesting capabilities to subdivide a <fileGrp> by format within the type, such as:
-- one <fileGrp> for all of the page images with nested <fileGrp> elements for each image format/resolution (tiff, jpeg, gif)
-- one <fileGrp> for a PDF version of all the pages of the document 
-- one <fileGrp> for  a TEI encoded XML version of the entire document or each of its pages.
A <fileGrp> may contain zero or more <fileGrp> elements and or <file> elements.
Diagram
Type extension of fileGrpType
Type hierarchy
Properties
content complex
maxOccurs unbounded
Model
Children file, fileGrp
Instance
 
<fileGrp ADMID="" ID="" USE="" VERSDATE="" xmlns="http://www.loc.gov/METS/">
  <fileGrp ADMID="" ID="" USE="" VERSDATE="">{0,unbounded}</fileGrp>
  <file ADMID="" BEGIN="" BETYPE="" CHECKSUM="" CHECKSUMTYPE="" CREATED="" DMDID="" END="" GROUPID="" ID="" MIMETYPE="" OWNERID="" SEQ="" SIZE="" USE="">{0,unbounded}</file>
</fileGrp>
Attributes
QName Type Use Annotation
ADMID xsd:IDREFS optional 
ADMID (IDREF/O): Contains the ID attribute values of the <techMD>, <sourceMD>, <rightsMD> and/or <digiprovMD> elements within the <amdSec> of the METS document applicable to all of the files in a particular file group. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer.
ID xsd:ID optional 
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 xsd:string optional 
USE (string/O): A tagging attribute to indicate the intended use of files within this file group (e.g., master, reference, thumbnails for image files). 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>).
VERSDATE xsd:dateTime optional 
VERSDATE (dateTime/O): An optional dateTime attribute specifying the date this version/fileGrp of the digital object was created.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="fileGrp" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A sequence of file group elements <fileGrp> can be used group the digital files comprising the content of a METS object either into a flat arrangement or, because each file group element can itself contain one or more file group elements, into a nested (hierarchical) arrangement. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as: -- one <fileGrp> for the thumbnails of the images -- one <fileGrp> for the higher resolution JPEGs of the image -- one <fileGrp> for the master archival TIFFs of the images For a text resource with a variety of content file types one might group the content files at the highest level by type, and then use the <fileGrp> element’s nesting capabilities to subdivide a <fileGrp> by format within the type, such as: -- one <fileGrp> for all of the page images with nested <fileGrp> elements for each image format/resolution (tiff, jpeg, gif) -- one <fileGrp> for a PDF version of all the pages of the document -- one <fileGrp> for a TEI encoded XML version of the entire document or each of its pages. A <fileGrp> may contain zero or more <fileGrp> elements and or <file> elements.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:complexContent>
      <xsd:extension base="fileGrpType"/>
    </xsd:complexContent>
  </xsd:complexType>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / structMap
Namespace http://www.loc.gov/METS/
Annotations
 
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.
Diagram
Type structMapType
Properties
content complex
maxOccurs unbounded
Model
Children div
Instance
 
<structMap ID="" LABEL="" TYPE="" xmlns="http://www.loc.gov/METS/">
  <div ADMID="" CONTENTIDS="" DMDID="" ID="" xlink:label="" LABEL="" ORDER="" ORDERLABEL="" TYPE="">{1,1}</div>
</structMap>
Attributes
QName Type Use Annotation
ID xsd:ID optional 
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 xsd:string optional 
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.
TYPE xsd:string optional 
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.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="structMap" type="structMapType" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / structLink
Namespace http://www.loc.gov/METS/
Annotations
Diagram
Type extension of structLinkType
Type hierarchy
Properties
Model
Children smLink, smLinkGrp
Instance
Attributes
Source
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Element metsType / behaviorSec
Namespace http://www.loc.gov/METS/
Annotations
 
A behavior section element <behaviorSec> associates executable behaviors with content in the METS document by means of a repeatable behavior <behavior> element. This element has an interface definition <interfaceDef> element that represents an abstract definition of the set of behaviors represented by a particular behavior section. A <behavior> element also has a <mechanism> element which is used to point to a module of executable code that implements and runs the behavior defined by the interface definition. The <behaviorSec> element, which is repeatable as well as nestable, can be used to group individual behaviors within the structure of the METS document. Such grouping can be useful for organizing families of behaviors together or to indicate other relationships between particular behaviors.
Diagram
Type behaviorSecType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children behavior, behaviorSec
Instance
 
<behaviorSec CREATED="" ID="" LABEL="" xmlns="http://www.loc.gov/METS/">
  <behaviorSec CREATED="" ID="" LABEL="">{0,unbounded}</behaviorSec>
  <behavior ADMID="" BTYPE="" CREATED="" GROUPID="" ID="" LABEL="" STRUCTID="">{0,unbounded}</behavior>
</behaviorSec>
Attributes
QName Type Use Annotation
CREATED xsd:dateTime optional 
CREATED (dateTime/O): Specifies the date and time of creation for the <behaviorSec>
ID xsd:ID optional 
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 xsd:string optional 
LABEL (string/O): A text description of the behavior section.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:element name="behaviorSec" type="behaviorSecType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A behavior section element <behaviorSec> associates executable behaviors with content in the METS document by means of a repeatable behavior <behavior> element. This element has an interface definition <interfaceDef> element that represents an abstract definition of the set of behaviors represented by a particular behavior section. A <behavior> element also has a <mechanism> element which is used to point to a module of executable code that implements and runs the behavior defined by the interface definition. The <behaviorSec> element, which is repeatable as well as nestable, can be used to group individual behaviors within the structure of the METS document. Such grouping can be useful for organizing families of behaviors together or to indicate other relationships between particular behaviors.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Complex Type metsType
Namespace http://www.loc.gov/METS/
Annotations
 
metsType: Complex Type for METS Sections
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).
Diagram
Used by
Element mets
Model
Children amdSec, behaviorSec, dmdSec, fileSec, metsHdr, structLink, structMap
Attributes
QName Type Use Annotation
ID xsd:ID optional 
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 xsd:string optional 
LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.
OBJID xsd:string optional 
OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.
PROFILE xsd:string optional 
PROFILE (string/O): Indicates to which of the registered profile(s) the METS document conforms. For additional information about PROFILES see Chapter 5 of the METS Primer.
TYPE xsd:string optional 
TYPE (string/O): Specifies the class or type of the object, e.g.: book, journal, stereograph, dataset, video, etc.
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.loc.gov/METS/'
Source
 
<xsd:complexType name="metsType">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">metsType: Complex Type for METS Sections 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).</xsd:documentation>
  </xsd:annotation>
  <xsd:sequence>
    <xsd:element name="metsHdr" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The mets header element <metsHdr> captures metadata about the METS document itself, not the digital object the METS document encodes. Although it records a more limited set of metadata, it is very similar in function and purpose to the headers employed in other schema such as the Text Encoding Initiative (TEI) or in the Encoded Archival Description (EAD).</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="agent" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">agent: The agent element <agent> provides for various parties and their roles with respect to the METS record to be documented.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="name" type="xsd:string">
                  <xsd:annotation>
                    <xsd:documentation xml:lang="en">The element <name> can be used to record the full name of the document agent.</xsd:documentation>
                  </xsd:annotation>
                </xsd:element>
                <xsd:element name="note" minOccurs="0" maxOccurs="unbounded">
                  <xsd:annotation>
                    <xsd:documentation xml:lang="en">The <note> element can be used to record any additional information regarding the agent's activities with respect to the METS document.</xsd:documentation>
                  </xsd:annotation>
                  <xsd:complexType>
                    <xsd:simpleContent>
                      <xsd:extension base="xsd:string">
                        <xsd:anyAttribute namespace="##other" processContents="lax"/>
                      </xsd:extension>
                    </xsd:simpleContent>
                  </xsd:complexType>
                </xsd:element>
              </xsd:sequence>
              <xsd:attribute name="ID" type="xsd:ID" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">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.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="ROLE" use="required">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS record. The allowed values are: CREATOR: The person(s) or institution(s) responsible for the METS document. EDITOR: The person(s) or institution(s) that prepares the metadata for encoding. ARCHIVIST: The person(s) or institution(s) responsible for the document/collection. PRESERVATION: The person(s) or institution(s) responsible for preservation functions. DISSEMINATOR: The person(s) or institution(s) responsible for dissemination functions. CUSTODIAN: The person(s) or institution(s) charged with the oversight of a document/collection. IPOWNER: Intellectual Property Owner: The person(s) or institution holding copyright, trade or service marks or other intellectual property rights for the object. OTHER: Use OTHER if none of the preceding values pertains and clarify the type and location specifier being used in the OTHERROLE attribute (see below).</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:enumeration value="CREATOR"/>
                    <xsd:enumeration value="EDITOR"/>
                    <xsd:enumeration value="ARCHIVIST"/>
                    <xsd:enumeration value="PRESERVATION"/>
                    <xsd:enumeration value="DISSEMINATOR"/>
                    <xsd:enumeration value="CUSTODIAN"/>
                    <xsd:enumeration value="IPOWNER"/>
                    <xsd:enumeration value="OTHER"/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:attribute>
              <xsd:attribute name="OTHERROLE" type="xsd:string" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">OTHERROLE (string/O): Denotes a role not contained in the allowed values set if OTHER is indicated in the ROLE attribute.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="TYPE" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. It must be one of the following values: INDIVIDUAL: Use if an individual has served as the agent. ORGANIZATION: Use if an institution, corporate body, association, non-profit enterprise, government, religious body, etc. has served as the agent. OTHER: Use OTHER if none of the preceding values pertain and clarify the type of agent specifier being used in the OTHERTYPE attribute</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:enumeration value="INDIVIDUAL"/>
                    <xsd:enumeration value="ORGANIZATION"/>
                    <xsd:enumeration value="OTHER"/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:attribute>
              <xsd:attribute name="OTHERTYPE" type="xsd:string" use="optional">
                <xsd:annotation>
                  <xsd:documentation xml:lang="en">OTHERTYPE (string/O): Specifies the type of agent when the value OTHER is indicated in the TYPE attribute.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="altRecordID" minOccurs="0" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The alternative record identifier element <altRecordID> allows one to use alternative record identifier values for the digital object represented by the METS document; the primary record identifier is stored in the OBJID attribute in the root <mets> element.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:simpleContent>
                <xsd:extension base="xsd:string">
                  <xsd:attribute name="ID" type="xsd:ID" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">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.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type (e.g., OCLC record number, LCCN, etc.).</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                </xsd:extension>
              </xsd:simpleContent>
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="metsDocumentID" minOccurs="0">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">The metsDocument identifier element <metsDocumentID> allows a unique identifier to be assigned to the METS document itself. This may be different from the OBJID attribute value in the root <mets> element, which uniquely identifies the entire digital object represented by the METS document.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:simpleContent>
                <xsd:extension base="xsd:string">
                  <xsd:attribute name="ID" type="xsd:ID" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">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.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
                    <xsd:annotation>
                      <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type.</xsd:documentation>
                    </xsd:annotation>
                  </xsd:attribute>
                </xsd:extension>
              </xsd:simpleContent>
            </xsd:complexType>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">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.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="ADMID" type="xsd:IDREFS" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">ADMID (IDREFS/O): Contains the ID attribute values of the <techMD>, <sourceMD>, <rightsMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain administrative metadata pertaining to the METS document itself. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="CREATEDATE" type="xsd:dateTime" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">CREATEDATE (dateTime/O): Records the date/time the METS document was created.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="LASTMODDATE" type="xsd:dateTime" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="RECORDSTATUS" type="xsd:string" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:anyAttribute namespace="##other" processContents="lax"/>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="dmdSec" type="mdSecType" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">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.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="amdSec" type="amdSecType" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">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.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="fileSec" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The overall purpose of the content file section element <fileSec> is to provide an inventory of and the location for the content files that comprise the digital object being described in the METS document.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:sequence>
          <xsd:element name="fileGrp" maxOccurs="unbounded">
            <xsd:annotation>
              <xsd:documentation xml:lang="en">A sequence of file group elements <fileGrp> can be used group the digital files comprising the content of a METS object either into a flat arrangement or, because each file group element can itself contain one or more file group elements, into a nested (hierarchical) arrangement. In the case where the content files are images of different formats and resolutions, for example, one could group the image content files by format and create a separate <fileGrp> for each image format/resolution such as: -- one <fileGrp> for the thumbnails of the images -- one <fileGrp> for the higher resolution JPEGs of the image -- one <fileGrp> for the master archival TIFFs of the images For a text resource with a variety of content file types one might group the content files at the highest level by type, and then use the <fileGrp> element’s nesting capabilities to subdivide a <fileGrp> by format within the type, such as: -- one <fileGrp> for all of the page images with nested <fileGrp> elements for each image format/resolution (tiff, jpeg, gif) -- one <fileGrp> for a PDF version of all the pages of the document -- one <fileGrp> for a TEI encoded XML version of the entire document or each of its pages. A <fileGrp> may contain zero or more <fileGrp> elements and or <file> elements.</xsd:documentation>
            </xsd:annotation>
            <xsd:complexType>
              <xsd:complexContent>
                <xsd:extension base="fileGrpType"/>
              </xsd:complexContent>
            </xsd:complexType>
          </xsd:element>
        </xsd:sequence>
        <xsd:attribute name="ID" type="xsd:ID" use="optional">
          <xsd:annotation>
            <xsd:documentation xml:lang="en">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.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:anyAttribute namespace="##other" processContents="lax"/>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="structMap" type="structMapType" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">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.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:element name="structLink" minOccurs="0">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">The structural link section element <structLink> allows for the specification of hyperlinks between the different components of a METS structure that are delineated in a structural map. This element is a container for a single, repeatable element, <smLink> which indicates a hyperlink between two nodes in the structural map. The <structLink> section in the METS document is identified using its XML ID attributes.</xsd:documentation>
      </xsd:annotation>
      <xsd:complexType>
        <xsd:complexContent>
          <xsd:extension base="structLinkType"/>
        </xsd:complexContent>
      </xsd:complexType>
    </xsd:element>
    <xsd:element name="behaviorSec" type="behaviorSecType" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">A behavior section element <behaviorSec> associates executable behaviors with content in the METS document by means of a repeatable behavior <behavior> element. This element has an interface definition <interfaceDef> element that represents an abstract definition of the set of behaviors represented by a particular behavior section. A <behavior> element also has a <mechanism> element which is used to point to a module of executable code that implements and runs the behavior defined by the interface definition. The <behaviorSec> element, which is repeatable as well as nestable, can be used to group individual behaviors within the structure of the METS document. Such grouping can be useful for organizing families of behaviors together or to indicate other relationships between particular behaviors.</xsd:documentation>
      </xsd:annotation>
    </xsd:element>
  </xsd:sequence>
  <xsd:attribute name="ID" type="xsd:ID" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">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.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="OBJID" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="LABEL" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="TYPE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">TYPE (string/O): Specifies the class or type of the object, e.g.: book, journal, stereograph, dataset, video, etc.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:attribute name="PROFILE" type="xsd:string" use="optional">
    <xsd:annotation>
      <xsd:documentation xml:lang="en">PROFILE (string/O): Indicates to which of the registered profile(s) the METS document conforms. For additional information about PROFILES see Chapter 5 of the METS Primer.</xsd:documentation>
    </xsd:annotation>
  </xsd:attribute>
  <xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / agent / @ID
Namespace No namespace
Annotations
 
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 xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / agent / @ROLE
Namespace No namespace
Annotations
 
ROLE (string/R): Specifies the function of the agent with respect to the METS record. The allowed values are:
CREATOR: The person(s) or institution(s) responsible for the METS document.
EDITOR: The person(s) or institution(s) that prepares the metadata for encoding.
ARCHIVIST: The person(s) or institution(s) responsible for the document/collection.
PRESERVATION: The person(s) or institution(s) responsible for preservation functions.
DISSEMINATOR: The person(s) or institution(s) responsible for dissemination functions.
CUSTODIAN: The person(s) or institution(s) charged with the oversight of a document/collection.
IPOWNER: Intellectual Property Owner: The person(s) or institution holding copyright, trade or service marks or other intellectual property rights for the object.
OTHER: Use OTHER if none of the preceding values pertains and clarify the type and location specifier being used in the OTHERROLE attribute (see below).
Type restriction of xsd:string
Properties
use required
Facets
enumeration CREATOR
enumeration EDITOR
enumeration ARCHIVIST
enumeration PRESERVATION
enumeration DISSEMINATOR
enumeration CUSTODIAN
enumeration IPOWNER
enumeration OTHER
Used by
Source
 
<xsd:attribute name="ROLE" use="required">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ROLE (string/R): Specifies the function of the agent with respect to the METS record. The allowed values are: CREATOR: The person(s) or institution(s) responsible for the METS document. EDITOR: The person(s) or institution(s) that prepares the metadata for encoding. ARCHIVIST: The person(s) or institution(s) responsible for the document/collection. PRESERVATION: The person(s) or institution(s) responsible for preservation functions. DISSEMINATOR: The person(s) or institution(s) responsible for dissemination functions. CUSTODIAN: The person(s) or institution(s) charged with the oversight of a document/collection. IPOWNER: Intellectual Property Owner: The person(s) or institution holding copyright, trade or service marks or other intellectual property rights for the object. OTHER: Use OTHER if none of the preceding values pertains and clarify the type and location specifier being used in the OTHERROLE attribute (see below).</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="CREATOR"/>
      <xsd:enumeration value="EDITOR"/>
      <xsd:enumeration value="ARCHIVIST"/>
      <xsd:enumeration value="PRESERVATION"/>
      <xsd:enumeration value="DISSEMINATOR"/>
      <xsd:enumeration value="CUSTODIAN"/>
      <xsd:enumeration value="IPOWNER"/>
      <xsd:enumeration value="OTHER"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / agent / @OTHERROLE
Namespace No namespace
Annotations
 
OTHERROLE (string/O): Denotes a role not contained in the allowed values set if OTHER is indicated in the ROLE attribute.
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="OTHERROLE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">OTHERROLE (string/O): Denotes a role not contained in the allowed values set if OTHER is indicated in the ROLE attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / agent / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): is used to specify the type of AGENT. It must be one of the following values:
INDIVIDUAL: Use if an individual has served as the agent.
ORGANIZATION: Use if an institution, corporate body, association, non-profit enterprise, government, religious body, etc. has served as the agent.
OTHER: Use OTHER if none of the preceding values pertain and clarify the type of agent specifier being used in the OTHERTYPE attribute
Type restriction of xsd:string
Properties
use optional
Facets
enumeration INDIVIDUAL
enumeration ORGANIZATION
enumeration OTHER
Used by
Source
 
<xsd:attribute name="TYPE" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): is used to specify the type of AGENT. It must be one of the following values: INDIVIDUAL: Use if an individual has served as the agent. ORGANIZATION: Use if an institution, corporate body, association, non-profit enterprise, government, religious body, etc. has served as the agent. OTHER: Use OTHER if none of the preceding values pertain and clarify the type of agent specifier being used in the OTHERTYPE attribute</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="INDIVIDUAL"/>
      <xsd:enumeration value="ORGANIZATION"/>
      <xsd:enumeration value="OTHER"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / agent / @OTHERTYPE
Namespace No namespace
Annotations
 
OTHERTYPE (string/O): Specifies the type of agent when the value OTHER is indicated in the TYPE attribute.
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="OTHERTYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">OTHERTYPE (string/O): Specifies the type of agent when the value OTHER is indicated in the TYPE attribute.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / altRecordID / @ID
Namespace No namespace
Annotations
 
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 xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / altRecordID / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): A description of the identifier type (e.g., OCLC record number, LCCN, etc.).
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type (e.g., OCLC record number, LCCN, etc.).</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / metsDocumentID / @ID
Namespace No namespace
Annotations
 
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 xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / metsDocumentID / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): A description of the identifier type.
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): A description of the identifier type.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / @ID
Namespace No namespace
Annotations
 
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 xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / @ADMID
Namespace No namespace
Annotations
 
ADMID (IDREFS/O): Contains the ID attribute values of the <techMD>, <sourceMD>, <rightsMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain administrative metadata pertaining to the METS document itself.  For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer.
Type xsd:IDREFS
Properties
use optional
Used by
Source
 
<xsd:attribute name="ADMID" type="xsd:IDREFS" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">ADMID (IDREFS/O): Contains the ID attribute values of the <techMD>, <sourceMD>, <rightsMD> and/or <digiprovMD> elements within the <amdSec> of the METS document that contain administrative metadata pertaining to the METS document itself. For more information on using METS IDREFS and IDREF type attributes for internal linking, see Chapter 4 of the METS Primer.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / @CREATEDATE
Namespace No namespace
Annotations
 
CREATEDATE (dateTime/O): Records the date/time the METS document was created.
Type xsd:dateTime
Properties
use optional
Used by
Source
 
<xsd:attribute name="CREATEDATE" type="xsd:dateTime" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">CREATEDATE (dateTime/O): Records the date/time the METS document was created.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / @LASTMODDATE
Namespace No namespace
Annotations
 
LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.
Type xsd:dateTime
Properties
use optional
Used by
Source
 
<xsd:attribute name="LASTMODDATE" type="xsd:dateTime" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LASTMODDATE (dateTime/O): Is used to indicate the date/time the METS document was last modified.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / metsHdr / @RECORDSTATUS
Namespace No namespace
Annotations
 
RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.
Type xsd:string
Properties
use optional
Used by
Source
 
<xsd:attribute name="RECORDSTATUS" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">RECORDSTATUS (string/O): Specifies the status of the METS document. It is used for internal processing purposes.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / fileSec / @ID
Namespace No namespace
Annotations
 
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 xsd:ID
Properties
use optional
Used by
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / @ID
Namespace No namespace
Annotations
 
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 xsd:ID
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="ID" type="xsd:ID" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">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.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / @OBJID
Namespace No namespace
Annotations
 
OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="OBJID" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">OBJID (string/O): Is the primary identifier assigned to the METS object as a whole. Although this attribute is not required, it is strongly recommended. This identifier is used to tag the entire METS object to external systems, in contrast with the ID identifier.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / @LABEL
Namespace No namespace
Annotations
 
LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="LABEL" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">LABEL (string/O): Is a simple title string used to identify the object/entity being described in the METS document for the user.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / @TYPE
Namespace No namespace
Annotations
 
TYPE (string/O): Specifies the class or type of the object, e.g.: book, journal, stereograph, dataset, video, etc.
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="TYPE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">TYPE (string/O): Specifies the class or type of the object, e.g.: book, journal, stereograph, dataset, video, etc.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
Attribute metsType / @PROFILE
Namespace No namespace
Annotations
 
PROFILE (string/O): Indicates to which of the registered profile(s) the METS document conforms. For additional information about PROFILES see Chapter 5 of the METS Primer.
Type xsd:string
Properties
use optional
Used by
Complex Type metsType
Source
 
<xsd:attribute name="PROFILE" type="xsd:string" use="optional">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">PROFILE (string/O): Indicates to which of the registered profile(s) the METS document conforms. For additional information about PROFILES see Chapter 5 of the METS Primer.</xsd:documentation>
  </xsd:annotation>
</xsd:attribute>
Schema location https://raw.githubusercontent.com/mets/METS-schema/5cc5f10c9950b3e43f1424236ca7a3f8fe4e7e76/mets.xsd
XML Schema documentation generated by ® XML Editor.