Lesson 1 — Metadata as Organizational Knowledge
“Data about data” is only the doorway
The phrase is useful, but Chapter 12 expects a larger idea. Metadata is the information that lets an organization understand, locate, process, govern, secure, audit, trust, reuse, and change data safely.
Consider a warehouse field named CUSTOMER_STATUS with values A, I, and P. The values are data. But a useful enterprise needs context around them:
- What does Customer Status mean?
- What do A, I, and P mean?
- Who owns the definition?
- What system is the source of record?
- What table and datatype implement it?
- What transformation creates the warehouse value?
- What reports depend on it?
- What quality rule applies?
- Is it sensitive?
- When did the last load run, and did it succeed?
- What will break if the source changes?
Those answers are Metadata. Together they form organizational knowledge about data.
The library analogy
DAMA compares poor Metadata Management to a large library without a catalog. The books may exist, but a user cannot efficiently answer:
- What exists?
- Where is it?
- What is it about?
- Which version is authoritative?
- How is it related to other information?
The same problem occurs in a company with thousands of tables, reports, files, services, definitions, mappings, and models. Merely possessing data does not make it usable.
Metadata is itself data
Metadata has owners, quality, security, lifecycle, history, standards, and consumers. It therefore must itself be managed as data.
The boundary is contextual. A datatype such as VARCHAR(20) is Metadata to an analyst examining a column. Inside the DBMS system catalog, that datatype is simply a stored value. The exam lesson is not to seek a philosophical absolute. Ask what role the information plays in the scenario.
Five Metadata Management goals
Chapter 12’s goals can be compressed into five ideas:
- Manage organizational knowledge of business terminology so people use data consistently.
- Collect and integrate Metadata from diverse sources so similarities and differences can be understood.
- Ensure Metadata quality, consistency, currency, and security.
- Provide standard access so people, systems, and processes can use Metadata.
- Establish and enforce technical Metadata standards that support exchange.
A Business Glossary supports these goals, but a glossary alone is not Metadata Management.
Why poor Metadata creates risk
Poorly managed Metadata creates competing definitions, redundant dictionaries, obsolete documentation, misunderstood data, slow research, duplicated work, change risk, and loss of trust. Reliable Metadata helps with reuse, impact analysis, compliance, onboarding, communication, development speed, and reducing dependence on individual memory.
Stop and check
A team has every table and column documented but cannot explain what “Net Revenue” means, who owns it, how it is calculated, or which reports use it. Does it have complete enterprise Metadata?
Answer: No. Technical structure is only one part of the knowledge required to understand and govern the data.
Source anchor: pp. 395–399.