Data Quality

Top-level UI section for data-quality signals in ODD — test results imported from Great Expectations / dbt / odd-collector-profiler / custom frameworks, the catalog-wide Quality Dashboard, and the ope

The Data Quality section of ODD Platform is the home for the catalog's correctness signals — test results pushed in from quality frameworks, the cross-catalog quality dashboard, and the operator-set dataset SLA statuses that downstream BI reports consume.

ODD covers Data Quality fully as an aggregator. Quality checks are not performed inside ODD Platform — the platform integrates with leading tools in the field and surfaces their results in one operator-friendly view. See the Data Governance map for the position of Data Quality among the other governance pillars.

Open it from the top-level navigation Data Quality tab (the catalog-wide dashboard) or from any data entity's Test reports tab (per-entity test results and SLA status).

Subsections

• Test Results Import — how test results land in the catalog: push-client integrations with Great Expectations and dbt, statistical profiles via odd-collector-profiler, and the POST /ingestion/entities/datasets/stats endpoint for custom frameworks.

• Quality Dashboard — the catalog-wide quality view at /data-quality — three breakdown rings (Table Health / Test Results / Monitored Tables), six anomaly-class metrics, and the per-side filter sets (tables vs tests).

• Dataset Quality Statuses (SLA) — Minor / Major / Critical statuses on test results, the dataset-level aggregate SLA colour, and the /api/datasets/{id}/sla endpoint for BI-report import.

Why this is a separate pillar

For how Data Quality relates to the other governance pillars (Data Discovery, Data Modelling, Master Data Management, Data Lineage, Data Glossary), see Main Concepts → Data Governance map → Pillar differentiation — the canonical home for the six-pillar framing. Quality is its own pillar because the correctness signal cuts across every catalogued dataset; this landing consolidates the three ways an operator interacts with it (ingest test results, view the catalog-wide dashboard, curate per-dataset SLA statuses for BI consumption).

Where to next

• If you are connecting a quality framework into the platform → Test Results Import.

• If you are auditing the catalog's overall quality posture → Quality Dashboard.

• If you are exposing dataset-level quality to BI reports → Dataset Quality Statuses (SLA).

• For the data-quality-engineer use case end-to-end → Visibility for Data Quality Engineer.

• For DQ-test-failed alerts and where they surface → Alerting.

• For the broader catalog vocabulary → Main Concepts.