EAD3

EAD3
Name	EAD3
Developer	Library of Congress; International Council on Archives contributors
Released	2015
Latest release	2015 (EAD3 draft/standard)
Operating system	Cross-platform
Genre	Archival description standard
License	Open standard

EAD3 EAD3 is an archival description standard used for encoding finding aids and archival inventories, designed to support detailed description of collections, repositories, and collections-level metadata. It builds on earlier archival standards and integrates with bibliographic and metadata frameworks to enable interoperability among institutions, digital libraries, data aggregators, and discovery platforms. The standard is maintained and promoted through collaboration among major institutions and professional bodies.

Overview

EAD3 provides an XML-based schema for encoding detailed descriptive information about archival collections, repositories, and related agents, aligning with international standards such as ISAD(G), Dublin Core, MODS, METS and RDF models. The specification supports linking to authority files and controlled vocabularies like Library of Congress Subject Headings, Virtual International Authority File, Getty Vocabularies, and Wikidata entities to improve discoverability across platforms such as Europeana, Digital Public Library of America, Internet Archive, and institutional repositories like the British Library and National Archives and Records Administration. EAD3 emphasizes modularity and extensibility to accommodate practices used by institutions including the National Archives (UK), Harvard Library, Yale University Library, and the National Library of Australia.

History and Development

EAD3 was developed as the third major revision following earlier versions produced by the Society of American Archivists in collaboration with the Library of Congress and influenced by archival practice in institutions such as the New York Public Library and The Huntington Library. Development drew on standards work from bodies like the International Council on Archives, with consultation from projects at Columbia University, University of California, Berkeley, Cornell University, and University of Toronto. The revision process considered interoperability with initiatives led by OCLC, WorldCat, JSTOR, and national digitization programs in the European Union and the United States. EAD3 reflects lessons from digital library efforts at Stanford University, MIT Libraries, Princeton University, and consortiums including HathiTrust.

Structure and Components

EAD3’s XML schema defines elements for descriptive components such as repository information, collection-level description, biographical/historical notes, scope and content, arrangement, and series/item-level descriptions; these parallel constructs found in ISAD(G) and ISAAR(CPF). Core components include header metadata, control information compatible with METS wrappers, descriptive blocks that can reference authority terms in LCNAF, and linkable identifiers resolvable via Handle System or DOI registration agencies. EAD3 supports structured name and subject encoding to align with authority files maintained by organizations like the Library of Congress, BNF, and Deutsche Nationalbibliothek, enabling integration with discovery systems at institutions such as Smithsonian Institution, British Museum, Vatican Library, and national archives across Canada, Germany, and France.

Implementation and Encoding

Implementations of EAD3 typically use XML editors, XSLT stylesheets, and transformation pipelines employed by archives at University of Michigan, University of Chicago, Yale University, and cultural heritage platforms like Europeana and DigitalNZ. Encoding workflows integrate data from collection management systems such as ArchivesSpace, AtoM, CALM, and legacy systems used by National Archives (UK) and the National Archives and Records Administration. Converters and mapping tools link EAD3 to MODS, MARC21, Dublin Core, and linked data outputs in JSON-LD for harvest by aggregators like OCLC and WorldCat; common utilities include XSLT, XPath, and XML Schema validation. Preservation and dissemination strategies involve repositories like HathiTrust, institutional digital libraries at Columbia University, and national initiatives coordinated through bodies like the Digital Preservation Coalition.

Use Cases and Applications

EAD3 is used to publish finding aids on institutional websites at repositories including Newberry Library, Bodleian Library, Royal Archives, and National Archives (UK), to supply harvestable metadata to aggregators like Europeana and DPLA, and to underpin research portals at universities such as Oxford University, Cambridge University, University of Pennsylvania, and Princeton University. Researchers draw on EAD3-encoded guides for provenance studies, collection-level discovery, and digital scholarly editions hosted by projects at King's College London, University College London, and Max Planck Institute centers. Museums and libraries integrate EAD3 descriptions with catalog records in systems by vendors like Ex Libris and OCLC for cross-collection discovery across platforms such as Google Books and institutional discovery layers.

Compatibility and Interoperability

EAD3 was designed to maximize interoperability with bibliographic and archival standards including MARC21, MODS, METS, Dublin Core, ISAD(G), ISAAR(CPF), and linked data vocabularies such as Schema.org and RDF. Mapping profiles and crosswalks have been developed by consortia like OCLC, projects at Harvard Library, Stanford University, and national libraries including Library of Congress and Bibliothèque nationale de France to enable export and ingestion between systems like ArchivesSpace, AtoM, and national catalogues. Integration with identifiers such as ORCID, VIAF, DOI, and the Handle System improves machine-actionable linking among datasets in repositories and aggregators including Zenodo and Figshare.

Criticisms and Limitations

Critics point to EAD3’s XML complexity and steep learning curve reported by practitioners at smaller repositories, local history societies, and community archives such as those supported by National Endowment for the Humanities grants and regional consortia. Limitations include challenges mapping collection- and item-level granularity to flat catalog systems used by vendors like SirsiDynix and integration issues with emerging linked-data practices championed by projects at Wikimedia Foundation, Linked Open Data community, and university digital humanities centers. Resource-constrained institutions cite costs of tooling, training, and migration similar to concerns raised in assessments by the Digital Preservation Coalition and reports from national libraries.

Category:Archival standards