What this EAD inspector checks
The inspector detects the current EAD4 namespace and the EAD3 or EAD 2002 namespaces, inventories nested unnumbered or numbered components, and exposes unit titles, identifiers, dates, containers, extent, level, source line, and full hierarchy path. It also checks version-specific top-level identification sections, duplicate IDs, local ID references, mixed component styles, numbered component depth, basic machine-readable date shape and order, URI declarations, digital-object elements, and access or use sections.
EAD4 and legacy finding aids
EAD4 uses camel-case elements such as archDesc, identificationData, unitTitle, and recordId. EAD3 and EAD 2002 use legacy names such as archdesc, did, unittitle, and recordid or eadid. The report follows the detected version instead of silently rewriting either form. Both unnumbered c and numbered c01–c12 hierarchies are readable, but mixing the two is reported.
Hierarchy and link review
Component paths make misplaced or unexpectedly deep series, files, and items easier to spot. Local IDREF-style attributes are resolved against IDs in the same XML document, while href, valueURI, and vocabulary-source URI values remain a separate non-fetching inventory. A missing stable component ID or unit identifier is a warning because repository practice varies; missing required descriptive wrappers and broken local references are errors.
Validation boundary
A clean report is not EAD schema, Schematron, Best Practices Guide, DACS, ISAD(G), accessibility, publication, or repository-ingest certification. This bounded inspector does not execute the official XSD or Schematron, validate every required order or controlled term, interpret every extension or local profile, fully validate EDTF/ISO dates, follow links, render the finding aid, assess descriptive quality, repair or migrate XML, or prove access and rights statements. Use the current official schemas, EAS XML Validator, best-practice guidance, and repository rules for authoritative validation.
Frequently asked questions
Does it support EAD4?
Yes. The current EAD4 namespace and camel-case core structure are the primary teaching example. EAD3 and EAD 2002 namespaces and their legacy identification wrappers are also recognized.
Does it upload or resolve links?
No. XML parsing and every check run locally in the browser. External and relative URI declarations are listed but never requested.
Why is a missing component title or ID a warning?
Those gaps often deserve review and can weaken navigation or stable linking, but this inspector does not impose an institution's descriptive application profile. Required wrappers and definitely broken local references remain errors.
Can this replace the official EAS XML Validator?
No. Use this page for readable hierarchy and content auditing, then use official schema and Schematron validation for conformance.
Authoritative references
The version detection and bounded checks follow the Library of Congress official EAD site, the EAD4 Tag Library, and the Society of American Archivists EAS schemas repository.
Inspect PREMIS metadata · Inspect a METS package · Browse preservation tools