An EAD, or encoded archival description, is a standardized XML format that libraries, archives, and museums use to make finding aids available online. This structure enables researchers to discover, browse, and evaluate collections before requesting physical access.
Below you will find a detailed overview of EAD documents, covering their purpose, structure, implementation, and common questions, followed by practical recommendations.
| Aspect | Description | Example Value | Relevance |
|---|---|---|---|
| File Format | Well-formed XML adhering to the EAD schema | .xml | Ensures machine readability and interoperability |
| Major Version | Current EAD standard version in widespread use | 2002, 2014 | Guides schema constraints and element availability |
| Primary Purpose | Describes the context, content, and structure of archival collections | Inventory-level records | Supports discovery and collection management |
| Linking to Digital Objects | Integration with repositories and digital asset systems | iiif manifests, repository URLs | Connects description with access |
Understanding EAD Document Structure
Core Components
Every EAD document contains a header describing the repository and collection, followed by a
Hierarchical Organization
The arrangement of
Implementing EAD in Digital Archives
Technical teams translate finding aids into EAD using schemas and validators to ensure compliance. Integration with discovery layers requires consistent encoding of titles, dates, and controlled vocabularies.
Metadata mapping connects EAD records with other systems, such as library catalogs and digital repositories. Controlled fields like subjects and names improve search precision and support linked data strategies.
EAD Best Practices and Quality Control
Rigorous validation against the official schema prevents structural errors. Regular reviews of descriptive levels ensure that hierarchies remain logical for both staff and researchers.
- Validate each EAD file against the current schema before publishing.
- Use consistent encoding for names, dates, and geographic terms.
- Document internal policies for level of detail and revision history.
- Link to digitized items using stable identifiers and persistent URLs.
- Schedule periodic audits to maintain accuracy over time.
EAD and Interoperability
Because EAD is broadly supported, archives can share data through OAI-PMH harvesting or API integrations. Transformation tools enable exports to CSV, JSON, or discovery platforms while preserving essential context.
Optimizing Collection Description with EAD
FAQ
Reader questions
How does an EAD document differ from a simple inventory spreadsheet?
An EAD document provides machine-readable, structured metadata with standardized elements and relationships, enabling automated discovery, data integration, and preservation workflows that a flat spreadsheet cannot support.
Can EAD be used for digital-only collections?
Yes, EAD describes collections at any level, including digital-only materials, and can include links to digitized objects and technical metadata within the same descriptive framework.
What happens when EAD schema versions change?
Organizations typically migrate records by mapping older elements to newer ones, validating the output, and updating workflows to align with current best practices and schema constraints.
How do I ensure names and subjects are consistent across multiple EAD files?
Use controlled vocabularies, authority files, and shared metadata dashboards, and coordinate descriptive decisions across teams to maintain consistency across collections and EAD instances.