Enterprise Metadata Management System · View 15 of 22 · Runtime

Data Quality Metadata

How quality results reach the catalog without the catalog becoming a quality engine.

Editable source SVG draw.io All views

The build/buy line

The platform stores dimensions, rules, scores and history. It runs no tests. Execution stays with the engines that already do it well.
Rules are stored as aspects on the asset, so the catalog knows what is being tested even when it is not the thing testing.
Rejecting a built-in quality engine is what keeps this platform from becoming the silo it exists to remove.

Where it shows up

Quality dimensions carried: completeness, accuracy, timeliness, uniqueness, validity, consistency.
Score, last run and trend on the asset profile; an asset failing its rules cannot be certified.
Breaches route to the asset owner from ownership metadata, not to a shared mailbox.

Risk

Five engines mean five result schemas. Each is behind a versioned adapter with contract tests; a schema change breaks one adapter rather than quality ingestion as a whole.

◀ Drift and Impact Analysis All views Deployment and Infrastructure ▶