What this DDI Codebook inspector checks
The tool recognizes namespace-prefixed or unprefixed DDI Codebook 2.1, 2.5, and 2.6-style XML. It inventories study identity, file descriptions, variables, question text, universes, categories, statistics, groups, language declarations, and link attributes. Source-line findings make missing labels, names, IDs, file links, category labels, and inconsistent declared variable counts easier to correct.
References and documentation coverage
Duplicate XML IDs and unresolved local reference attributes are surfaced separately from external locations. Variable-to-file and variable-group membership are checked against IDs in the same document. Coverage ratios report what is present, not whether wording, concepts, weights, disclosure controls, or statistical methodology are adequate.
Privacy and XML safety
Processing is local and static. The parser never fetches schemas, links, controlled vocabularies, or referenced files. DTD and external-entity declarations are rejected, so older DTD-based instances can be structurally reviewed only after using an appropriate trusted workflow to produce DTD-free XML.
Validation boundary
This is a bounded preflight, not a complete DDI validator. It does not apply the full version-specific XSD or DTD, controlled vocabularies, agency profiles, every content rule, or DDI Lifecycle 3.x/CDI semantics. It does not judge documentation quality, disclosure risk, statistical fitness, or repository acceptance. Confirm conformance with the official schema and the receiving archive’s requirements.
Frequently asked questions
Does the tool upload confidential survey metadata?
No. The codebook is parsed by JavaScript in the current browser tab. Links and schema locations are displayed but never requested.
Why can a result pass with warnings?
Errors cover structural conflicts in the supported checks, such as duplicate IDs or dangling file and group references. Missing optional documentation is reported as a warning so teams can make a deliberate completeness decision.
Does this inspect the microdata file?
No. File descriptions and variable links are read from the XML only. The tool does not open, profile, or compare the underlying data rows.
Authoritative references
Use the DDI Alliance’s DDI Codebook overview, DDI-Codebook 2.6 schema documentation, and DDI-C getting-started guidance for authoritative implementation details.
Inspect a PDS4 product label · Inspect a PDS3 label · Browse scientific-data tools