2.1 Metadata standards and ontologies
Program components address most questionsThe program publishes the metadata schemas used by NADA and the Metadata Editor, develops methods to complete and check records with AI under curator review, and works on classifications, concept links, and a question bank. The cookbook translates these into a three-layer check and templates that an organization can run on its own catalog.
Questions in this dimension 5 of 5 addressed by a program component
- 2.1.1Adoption of metadata standards
- 2.1.2Classifications, concepts, vocabularies
- 2.1.3Linkage between data and metadata
- 2.1.4Machine-readable publication and web discoverability
- 2.1.5Provenance and lineage
Program resources
- Metadata EditorTemplates, validation, export to SDMX, schema.org, Croissant, DCAT; publishes to NADA
- NADA catalogCatalog pages with schema.org markup, search, a catalog administration REST API, managed access; semantic search and MCP access through NADA AI, being integrated into NADA
- Metadata AugmentationDDI-style variable groups from data dictionaries
- Ontologies and knowledge graphsWorkstream: concept links across catalogs
- Microdata LibraryNADA catalog with DDI records and DataCite DOIs
- World Bank metadata schemasJSON Schema for indicators, microdata (DDI), geospatial (ISO 19115), documents, tables, images, scripts
- Global Question BankWorkstream: reusable questions and concepts across surveys
- AI-ready metadata and standardsWorkstream: standards adoption guidance for AI-ready data
What it takes roles and effort summed from the linked recipes; systems and hosting written per dimension
| Step | Who | One-off effort | Work that recurs | Systems that have to exist |
|---|---|---|---|---|
| A to BFoundational recipes | Developer or data engineer, Subject-matter staff, Data curator, Catalog or data manager, and 3 more | about 5 person-days | Per item: about 30 minutes per indicator; an hour per questionnaire; half an hour per documentPer period: minutes after that |
|
| B to CAI-ready recipes | Developer or data engineer, Data curator, Catalog or data manager, Subject-matter staff, and 2 more | about 4 person-days | Per item: half a day per source; half an hour per document; half an hour per tablePer period: minutes per period; part of each round; an hour per period to review |
|
| C to DAI-native recipes | Developer or data engineer | 5 to 10 person-days | — |
|
- Hardware and hosting, medium office
- The catalog host and a small server for the review pipeline
- Kinds of cost
- Staff time of curators (the largest cost at every level)
- No licence costs: the editor, the catalog, and the schemas are open source
- Depends on
- No other dimension; this is where the data side starts.
Effort is the sum of the time lines of the recipes the dimension links, written for a first implementation on the running examples; a large catalog multiplies the per-item work. Money is given as kinds of cost because prices differ too much between countries and years for a figure to hold. Pillar I has no such table: its investments are institutional decisions the program does not cost.
Relevant cookbook chapters
- Chapter 1: recipe 1.1 (check records against the schema and a profile), recipe 1.2 (schema.org on every page)
- Chapter 3: definitions and method notes, code lists and crosswalks, breaks and revisions as data
- Standards by chapter: SDMX, DDI, ISO 19115, Dublin Core, DCAT, DataCite
- Application by data type: schema, format, and interface per type
- Metadata Curation, chapter 6: controlled vocabularies (SKOS) and mapping free text to them
- Metadata Curation, chapter 2: moving legacy records into the schema
- Metadata Curation, chapter 3: fields drafted by a model, held in draft status until a curator accepts them
- Language Models in Statistical Production, chapter 3: open text coded to a classification with the classification as context and accuracy measured by level
- Language Models in Statistical Production, recipe 2.2: new questions matched to the question bank
- Data from Documents, chapter 7: table records with provenance, linked to documents and series
- Data from Documents, chapter 1: a catalog record per document with the series and surveys it draws on
- Publishing ML-Ready Datasets, chapter 3: the Croissant record generated from the dictionary and validated (machine-readable publication)
Progression between maturity levels
- A B
Document each product in the World Bank schema for its type with the Metadata Editor or the CSV template, and run the completeness check at the foundational level.
- B C
Publish code lists and crosswalks, record breaks and provenance as fields, and emit schema.org or DCAT from the catalog (NADA does this on every page).
- C D
Reach the AI-ready profile across the catalog, link concepts to shared vocabularies, and use AI-assisted review under a curator to keep records consistent.
Levels A to D are the maturity scale of the framework. The actions listed are those supported by program resources; the framework's suggested actions for each transition also apply.
Evidence for the assessment form
- Completeness report at the target level using the organization's profile
- A validated schema.org or DCAT record
- Published code lists and crosswalks
- Provenance block in records