Metadata Management (KA 10) — Catalog, Lineage, Glossary

Metadata Management (KA 10) — Catalog, Lineage, Glossary

The data about data — without it, every other KA is doing CrossFit blindfolded.

Why it matters

Metadata is the cheapest leverage in DMBOK. A serviceable catalog + lineage + glossary triples the speed of every other initiative. Skip it and every analyst spends 30% of their week answering ‘does this table exist?’.

Going deeper

Three metadata layers DMBOK distinguishes:

• Business metadata — definitions, glossary, ownership, KPIs.
• Technical metadata — schema, lineage, freshness, system of record.
• Operational metadata — last run, row count, cost, latency, SLA status.

A catalog that has all three layers, wired together, and visible to analysts in their normal workflow, is the difference between governance theatre and governance reality. Tools: DataHub, OpenMetadata, Collibra, Atlan, Atlas, Unity Catalog — pick one and commit.

Metadata is the card catalog of the library.

Before card catalogs, finding a book meant walking the stacks or asking the librarian. After card catalogs, anyone could find any book by title, author, subject — and know whether it was on loan, in restoration, or lost. A data catalog with all three metadata layers does the same: business definitions (title), technical lineage (subject + author), operational signals (on loan? lost?).

A warehouse without a catalog is the Library of Alexandria without an index — vast, valuable, effectively unsearchable. The cost is paid one analyst at a time, every day, forever.