Skip to content

Rapid Battle Cards 25–36

25. As Designed vs As Implemented Lineage

Designed = intended mapping/specification.
Implemented = actual production code/processing.

26. Metadata Coverage vs Metadata Quality

Coverage = how much in-scope Metadata exists.
Quality = how correct, consistent, useful, and trustworthy the content is.

27. Metadata Coverage vs Usage

Coverage = existence/representation.
Usage = actual adoption/search/access/use.

28. Metadata Quality vs Currency

Quality = broad fitness/trust.
Currency = whether Metadata reflects the current state; currency is one quality dimension.

29. DQ Tool Metadata vs Business Rule

DQ tool Metadata = profile, validation rule implementation, score, observed pattern.
Business rule = governed meaning/expectation that may drive the DQ rule.

30. Repository Completeness vs Steward Representation

Completeness = assets/elements covered.
Steward representation = scope with accountable Steward roles assigned/documented.

31. Repository Usage vs Glossary Activity

Usage = use of the overall Metadata environment.
Glossary activity = searches, updates, definition resolution, and coverage specifically within glossary content.

32. ISO/IEC 11179 vs Internal Naming Standard

ISO/IEC 11179 = external Metadata Registry / standardized data-element definition and registration framework.
Internal naming standard = organization-specific convention.

33. Unstructured Data vs Metadata

Unstructured content may lack fixed internal schema; Metadata supplies discovery, provenance, security, retention, and lifecycle context.

34. Data-Lake Ingest vs Later Cataloging

Capture minimum Metadata at entry while context is known. Later reconstruction is weaker and may be impossible.

35. Security of Data vs Security of Metadata

Data security protects values/content.
Metadata security protects descriptive/control information that may reveal sensitive asset existence, location, structure, or movement.

36. Governance vs Repository Administration

Governance = decision rights, standards, ownership, quality/security/lifecycle accountability.
Administration = jobs, movement, refreshes, warnings, interfaces, technical issues.

Source: pp. 401–423.

← Cards 13–24 · Deep A–F →