Data governance
7 min

Metadata Quality: How to Measure It and What to Do About It

Key takeaways

  • Metadata quality is how complete, accurate, consistent, conformant, current, traceable, and confirmed the records describing your data are. You measure it by running rules over those records and reporting the pass rate.
  • Coverage is the metric most programs report, and it counts a model-written description the same as a steward-written one. Since AI enrichment, coverage can rise while nothing has been approved.
  • Seven dimensions are worth measuring. Six come from the literature and the vendor guides. The seventh, attestation, asks whether an accountable person confirmed the meaning and until when, and no coverage metric has a column for it.
  • Metadata held in RDF is data, so SHACL shapes validate the metadata record itself: one definition per term, a steward who is a person, a review date in the future, a mapping with an approver. The validation report is data too.
  • Score the terms that decide consequential answers separately from the long tail, keep the failed checks as a work queue, and raise the score by letting a model propose and a named expert confirm.
In this article
Share

Metadata quality is the degree to which the records describing your data are complete, accurate, consistent, conformant, current, traceable to a source, and confirmed by a named person. Most programs measure the first of those and stop. The metadata quality dashboard shows the share of described tables climbing each quarter, and nobody asks what the descriptions say. Since AI enrichment arrived, the answer is often a model's guess. Coverage went up. Quality did not move, and the dashboard cannot tell the difference.

This piece sets out what to measure, how to make each measure a check a machine runs, and what to do when one fails. The method rests on one fact the published frameworks leave out. Metadata held as structured data can be validated with SHACL, the W3C standard that validates data. A rule about metadata becomes a test, and the result becomes metadata too.

Metadata quality is measured by rules, scored by consequence, and raised by approval. The rule is a SHACL shape. The score covers the terms that decide answers. The fix is a named expert confirming what a model proposed.

What is metadata quality, and how is it different from data quality?

Data quality asks whether the values are right. Metadata quality asks whether the description of those values is right, and whether anyone would stand behind it. The two fail in different places.

Data quality and metadata quality, side by side

QuestionData qualityMetadata quality
What is testedThe values in a column or a recordThe record that describes the column: its definition, owner, mapping, scope, and dates
Example ruleEvery order carries a customer ID that exists in the customer tableEvery governed term carries exactly one approved definition and a steward who is a person
Who notices a failureA report is wrong, a pipeline breaks, a customer complainsNobody, for a long time. The description reads well and the data loads
What an agent does with a failureReturns a wrong numberReturns a plausible answer built on a meaning nobody agreed

The last row is why metadata quality became urgent. A person reading a stale description notices it. An agent reads it as fact. In our post What Is Metadata Management? we state that an inferred meaning is directionally right until being wrong carries a consequence. Metadata quality assessment is how you find the inferred, stale, and unowned records before an agent resolves against them. For a search result, a mostly right description is fine. For an agent approving a credit limit, 85% accurate isn't good enough.

Which dimensions of metadata quality should you measure?

The research literature settled on a short list. A 2016 review by McMahon and Denaxas in the AMIA Joint Summits proceedings found nine dimensions in prior work. They are accessibility, accuracy, completeness, conformance, interoperability, consistency, frequency, timeliness, and meta-metadata. The vendor guides narrow the list. The lakeFS guide, updated July 2026, lists completeness, accuracy, consistency, validity, uniqueness, and timeliness. The Fast.io guide, updated April 2026, lists completeness, accuracy, consistency, timeliness, and conformity. One dimension is missing from every list, and it is the one an AI system depends on most.

Seven dimensions, and the check behind each

DimensionQuestion it answersA check you can runWhat a filled-field count misses
CompletenessDoes every governed term carry the fields a consumer needs?Definition, steward, scope, mapping, and review date all presentA description a model generated counts as present
AccuracyDoes the description match the data?Profile the column against the rule in the definition; sample and confirmEverything. A filled field counts, right or wrong
ConsistencyDoes one concept have one meaning everywhere?Count definitions per term across catalogs, glossaries, and dashboardsForty tidy descriptions of forty columns can hold five meanings
ConformanceDo values and identifiers follow the agreed form?Date formats, code lists, identifier patterns, required vocabulariesA free-text date passes a presence check
TimelinessIs the record current?Review date in the future; no schema change since the last confirmationA last-edited timestamp records who touched the text
ProvenanceWhere did this description come from?Source of each field, crawler, model, or person, with the dateModel-written and steward-written text look identical
AttestationDid an accountable person confirm this meaning, and until when?Approver is a person, approval is dated, review is scheduled, expired records are flaggedAll of it. No coverage metric has a column for it

Attestation, or SME approval, is the dimension that separates a described record from a trusted one. Our post Ground Truth: SME-Approved vs Inferred Metadata covers why that distinction decides whether an agent's answer can be defended. If attestation is unmeasured, an enrichment agent can raise every other number and approve nothing.

How do you score metadata quality?

A metadata quality score is a set of rules, run over a scope, with the pass rate reported. Three decisions matter more than the arithmetic.

Three scoring decisions

  • Score the authoritative slice on its own. One number across fifty thousand assets hides the two hundred terms that decide credit limits, filings, and clinical answers. In our post Context Management: The Complete Guide we state that the authoritative slice is consistently under 5% of all data in TopQuadrant customer engagements. Report that slice separately, with the list of what is missing.
  • Weight by consequence, and publish the weights. A compliance use weights completeness and attestation. A discovery use weights consistency and conformance. The weights sit next to the score.
  • Keep the failures, and count them. A composite of 0.87 tells a steward nothing to do. A list of fourteen failed checks, each naming the record and the rule, is a work queue.

There is a public example at scale. The European data portal runs a Metadata Quality Assessment over every dataset description it harvests. It scores five dimensions out of 405 points and assigns one of four ratings. The Excellent band starts at 351, as reported in an August 2026 arXiv study of the Nordic catalogues. The portal publishes a DCAT-AP SHACL validator alongside the dashboard, per its provider manual. The rules are SHACL shapes.

How does SHACL validate metadata itself?

SHACL, the W3C Shapes Constraint Language, is usually introduced as a way to validate data. Our post What Is SHACL? covers the standard. Metadata held in RDF is data, so a shape applies to a metadata record the same way it applies to a customer record. A rule about what a governed term must carry is written once, runs on every record, and returns a report that names each failure.

Quality rules as SHACL shapes

Quality ruleSHACL constraintWhat the check catches
Every governed term has exactly one definitionsh:minCount 1 and sh:maxCount 1 on the definition propertyTerms with no definition, and terms with two competing ones
The steward is a person, with a successor on filesh:class on the steward property, sh:minCount 1 on the successorOwner fields holding a team mailbox, a departed employee, or nothing
The definition is long enough to mean somethingsh:minLength on the definitionA description that reads "customer table"
The review date is in the futuresh:sparql comparing the review date with todayApproved records that expired quietly
Each term maps to at least one physical columnsh:minCount 1 on the mapping, sh:node on the mapping shapeBusiness terms nobody has connected to data
Each mapping carries its approver and basissh:minCount 1 on prov:wasAttributedTo and on the approval dateMappings a model proposed and nobody confirmed
Codes come from the approved listsh:in or sh:class against the reference data setValues that conform to no vocabulary

Each constraint in that table is defined in the W3C SHACL specification. SHACL carries three severities: Violation, Warning, and Info. A missing steward on an authoritative term is a Violation that blocks publication. A short description on a long-tail asset is an Info that feeds the queue. The validation report is itself an RDF graph, so each result can be stored against the record it tested. The W3C Data Quality Vocabulary defines a quality measurement as "the evaluation of a given dataset (or dataset distribution) against a specific quality metric". The rule, the record, and the result are then data on one open standard. The dashboard reads the same graph the agent reads.

A presence check inside a catalog answers whether a field is filled. It cannot test that two systems hold one definition, that a term resolves to a column, or that an approval has an expiry. The record is text. A shape can test all three, because the record is data.

What do you do when a metadata quality check fails?

A failed check is a work item with a rule and a record attached. The action depends on the dimension that failed.

Finding, action, and who acts

FindingActionWho acts
Missing definitions, stewards, or mappingsLet a model draft them. Every proposal lands in the steward's queue with its evidence. AI proposes, your experts confirmAutomation drafts; a named steward approves
Five meanings of one termApprove one definition at the concept, with its scope, and map the forty columns to itThe data owner for the domain
Expired approvalsMake review cadence a governed state. Consumers refuse an expired record and route it to the stewardThe steward, on the schedule the record carries
Model-written text with no approverApproval writes the approver, the date, the version, and the review interval onto the recordThe steward
Catalog descriptions drifting from the recordSync the catalog from the record. Your catalog stays, and it stops inventing meaningThe platform team

Our post Active vs Passive Metadata: Why a Well-Organized Catalog Still Goes Unused covers why an approved record that never reaches the tools fails in a different way. Our post Metadata Management Framework: Four Stages and a Self-Assessment places these checks on a maturity path. Our post What Is Data Governance for AI? covers who the steward is. Our post Metadata Management Tools for Governance and AI Readiness covers the tooling.

Where does TopQuadrant fit?

TQ Data Foundation holds governed metadata as RDF, SKOS, OWL, and SHACL, so every rule in this piece runs as a shape on the record itself. Records carry when they were last confirmed and by whom, so staleness is visible. Proposed mappings arrive scored, and a steward accepts or rejects them. AI proposes, your experts confirm. The standards are open ones TopQuadrant helped author, so the rules and the results export in full. We maintain 300 reusable standards-based models. Your catalog stays. It syncs from the governed record. Our metadata management use case page shows how TQ Data Foundation does this in practice.

Measure the slice that decides answers first. Write the rules as shapes. Put a name on every record that passes. That is metadata quality an agent can rely on.

Give your AI the context it's been missing

See how the TQ Data Foundation turns your enterprise knowledge into trusted, Al-ready context.