What this PREMIS inspector checks
The parser accepts a PREMIS wrapper or a standalone object, event, agent, or rights entity. It inventories semantic identifier pairs and xmlID values; checks essential object, event, agent, and rights fields; surfaces object classes, sizes, formats, fixity declarations, event dates and outcomes, and agent descriptions; and preserves exact source lines for findings.
Relationship resolution
Linking object, event, agent, and rights-statement identifiers plus related object and event identifiers are reconciled against entities inside the selected document. Explicit XML IDREF attributes are checked independently, expected target kinds are compared, and conflicts between semantic identifiers and xmlID targets are errors. A semantic identifier absent from this file remains a warning because PREMIS can link to an entity managed elsewhere.
Fixity declarations
Each object fixity block exposes its message-digest algorithm, value, and originator. Missing fields are errors, and unusual hexadecimal lengths for MD5 or common SHA families are warnings. The XML contains declarations rather than the preserved files themselves, so this page cannot recalculate or authenticate those digests.
Validation boundary
A clean report is not PREMIS schema, semantic, conformance, or repository-ingest certification. This bounded inspector does not execute the official XSD, validate every required ordering or basis-specific rights rule, dereference controlled vocabularies, inspect extension content, verify preserved-file bytes or signatures, prove event truth, apply local application profiles, repair XML, or judge legal rights. Use the current PREMIS Data Dictionary, official schema, controlled vocabularies, and repository rules for authoritative validation.
Frequently asked questions
Can I inspect PREMIS embedded inside METS?
This page expects a PREMIS wrapper or standalone PREMIS entity. Extract the PREMIS XML element first. Use the METS package inspector for METS fileSec and structMap relationships.
Why is an unresolved identifier only a warning?
A linking identifier can describe an entity stored outside this document. An explicit xmlID reference is local by definition, so a missing xmlID target is treated as an error.
Does a correct-looking digest prove fixity?
No. This page checks declaration completeness and common hexadecimal shape only. Fixity verification requires hashing the separately identified preserved object and comparing trusted values.
Does it support PREMIS 1 or 2?
The XML remains visible, but namespace and version warnings are issued because the implemented field and relationship audit targets PREMIS 3.
Authoritative references
The data model and bounded checks follow the Library of Congress PREMIS official site, PREMIS 3.0 Data Dictionary, and official PREMIS 3 XML Schema source.
Inspect a METS package · Validate a BagIt package · Browse preservation tools