Metadata Encoding and Transmission Standard

Metadata Encoding and Transmission Standard
Name	Metadata Encoding and Transmission Standard
Abbreviation	METS
Developer	Library of Congress; Network Development and MARC Standards Office
Released	1999
Latest release	1.16 (example)

Metadata Encoding and Transmission Standard

Metadata Encoding and Transmission Standard is a XML-based schema designed to package descriptive, administrative, and structural metadata for digital objects. It provides mechanisms for linking to file-level metadata, preservation information, and metadata profiles used by archives, libraries, and cultural heritage institutions. METS is widely used by bibliographic repositories, digital preservation projects, and aggregator services.

Overview

METS defines an XML framework that organizes metadata from systems such as MARC 21, Dublin Core, MODS, PREMIS, and EAD while enabling integration with content management systems used by institutions like the Library of Congress, National Archives and Records Administration, British Library, Smithsonian Institution, and Bibliothèque nationale de France. Implementations often interoperate with protocols and standards including OAI-PMH, IIIF, SRU, Z39.50, and SWORD to enable harvesting, delivery, and deposit across networks like Digital Public Library of America and Europeana. METS is commonly used alongside format registries and preservation services from organizations such as Open Preservation Foundation and Internet Archive.

History and Development

METS was initiated by the Library of Congress in collaboration with the National Information Standards Organization and the Research Libraries Group to address needs identified by projects like Making of America and National Digital Newspaper Program. Early adopters included university projects at University of Michigan, University of California, Berkeley, and Yale University which contributed use cases and implementations. Over successive versions METS incorporated community feedback from digital library consortia such as OCLC, JSTOR, HathiTrust, and DPLA partners, and was influenced by metadata work at INRIA and German National Library.

Technical Specifications

The METS schema organizes metadata into sections: the descriptive metadata section (dmdSec) for schemas like Dublin Core and MODS; the administrative metadata section (amdSec) which accommodates standards such as PREMIS and METS rightsMD; the file section (fileSec) referencing digital objects; the structural map (structMap) for hierarchical ordering; and the structural link (structLink) for non-hierarchical relationships. METS documents are encoded in XML Schema and validated against namespaces used by XML, XLink, and MIME registries. Packaging supports multipart objects, checksums described with MD5 or SHA-1 and integrates with package formats referenced by BagIt and METS-EXT profiles maintained by consortia like DuraSpace and Fedora Commons.

Profiles and Implementations

Several profiles constrain METS for domain-specific use: the METS profile for digitized newspapers, institutional profiles developed by National Library of Australia, and project profiles from Chronicling America and Europeana Data Model implementers. Repository software that supports METS includes Fedora Commons, DSpace, Islandora, Archivematica, and CONTENTdm. Commercial platforms such as Ex Libris products and projects at ProQuest and EBSCO Information Services use METS for ingest/export workflows. Community-contributed tools like JHOVE, METSvalidator, and libraries in Python, Java, and Perl facilitate parsing, validation, and transformation to formats like METS-ARCLIN or exports for Solr indexing.

Applications and Use Cases

METS is used to describe digitized manuscripts for collections at institutions like British Library, Library of Congress, and New York Public Library; to package born-digital theses and dissertations at universities such as Harvard University and Stanford University; and to support newspaper digitization programs including Chronicling America and Trove. It underpins preservation workflows in national programs at National Archives of Australia and regional consortia including California Digital Library and DigitalNZ. Aggregators such as Europeana and DPLA ingest METS packages or METS-derived data to build search indexes and provide access services.

Interoperability and Standards Integration

METS is explicitly designed to be interoperable with metadata standards like MARC 21, MODS, Dublin Core, and preservation metadata standards like PREMIS, enabling conversion to and from database schemas used by OCLC, PROQUEST, and institutional repositories. It maps to delivery frameworks such as IIIF manifests and harvesting services like OAI-PMH. METS registries and application profiles are maintained in coordination with standards bodies including NISO and the Library of Congress’s Network Development and MARC Standards Office to align with registries like IANA for MIME types and checksum algorithms.

Criticism and Limitations

Critics note METS's complexity and steep learning curve for small institutions compared to lightweight schemas like Dublin Core or straightforward packaging approaches like BagIt. Implementation variability across profiles has led to interoperability challenges among aggregators such as Europeana and DPLA, and inconsistent use of sections like amdSec can hamper automated preservation workflows involving Archivematica or Preservica. Dependence on XML and verbose serialization is contrasted with modern JSON-based approaches used by platforms like ElasticSearch and IIIF JSON manifests, prompting some projects to adopt simplified mapping layers or conversion services.

Category:Metadata standards