Visual Atlas — Maps 01–04
Map 1 — Metadata Knowledge Web
Recall first:
DATA ↔ BUSINESS MEANING ↔ SYSTEMS ↔ PROCESSES ↔ RULES ↔ PEOPLE/OWNERS ↔ QUALITY/SECURITY ↔ LINEAGE
Interpretation: Metadata is organizational knowledge connecting data to meaning, implementation, operation, ownership, controls, and relationships.
Rebuild: Put DATA in the center. Add seven spokes: Meaning; Systems; Processes; Rules; People/Owners; Quality/Security; Lineage.
Answer check: If your map contains only tables and columns, it is too narrow.
Source: pp. 395–398.
Map 2 — Three-Type Triangle
Business — meaning / rules / ownership
Technical — structure / mapping / movement
Operational — execution / logs / usage
Rebuild examples: - Business: definition, Steward, business rule. - Technical: table, mapping, ETL dependency. - Operational: job result, error, query duration.
Decision rule: classify by the role/content of the information, not by who uses it.
Source: pp. 399–401.
Map 3 — Information-Science Lens
DESCRIPTIVE → identify/retrieve
STRUCTURAL → parts/relationships
ADMINISTRATIVE → lifecycle/manage
Examples: title/author/subject → pages/chapters/sequence → version/archive date.
Answer check: This taxonomy supplements B/T/O Metadata; it does not replace it.
Source: pp. 401–402.
Map 4 — Metadata Source Landscape
Place MANAGED ENTERPRISE METADATA at the center. Surround it with:
Application Repos · Business Glossary · BI · CMDB · Data Dictionary · Integration · DB/System Catalogs · Mapping Tools · DQ · Directory/Catalog · Messaging · Modeling · Reference Data · Service Registry · Other Stores
Interpretation: the organization already produces Metadata. Management integrates and governs scattered producers.
Answer check: Be able to identify at least Glossary, Dictionary, Catalog, CMDB, Integration, Modeling, DQ, DB catalogs, and Service Registry from a scenario.
Source: pp. 403–407.