Rapid Battle Cards 01–12
1. Metadata vs Data
Metadata describes or controls context about data; the boundary can depend on use and abstraction.
Clue: ask what role the information plays, not where it is stored.
2. Business vs Technical Metadata
Business: meaning, rules, ownership, governance context.
Technical: physical implementation, mapping, storage, movement.
3. Technical vs Operational Metadata
Technical: design/structure/process definition.
Operational: runtime execution/access evidence such as logs, duration, failures, usage.
4. Business vs Operational Metadata
Approved definition/owner/rule → Business.
Job/query/SLA status → Operational.
5. Descriptive vs Structural Metadata
Descriptive helps identify/retrieve a resource.
Structural describes parts and relationships inside/between resources.
6. Structural vs Administrative Metadata
Structural = organization/relationships.
Administrative = lifecycle/management information such as version or archive status.
7. Business Glossary vs Data Dictionary
Glossary = business concepts, terminology, definitions, ownership.
Dictionary = detailed data-set/data-element structure and characteristics.
8. Data Dictionary vs Directory/Catalog
Dictionary = field/data-set properties.
Directory/Catalog = where systems/data/assets can be found.
9. Business Glossary vs Directory/Catalog
Glossary answers “What does it mean?”
Catalog answers “Where can I find it?”
10. CMDB vs Metadata Repository
CMDB = IT configuration assets, versions, and relationships.
Enterprise Metadata repository = broader integrated knowledge across terms, models, mappings, lineage, DQ, stewardship, operations, and more.
11. Modeling Repository vs Metamodel
Modeling repository = a source of model Metadata.
Metamodel = the model defining Metadata entities/attributes/relationships in the managed environment.
12. Data Model vs Metamodel
Data model = Customer / Order / Product.
Metamodel = System / DataElement / Mapping / Steward.
Clue: model of data vs model of Metadata.
Source: pp. 397–414.