Lesson 6 — Standards and Store Management
Two activities can sound similar because both keep a Metadata environment orderly. They solve different problems.
Apply Metadata Standards
Source tools often use different naming conventions, identifiers, custom attributes, classifications, and visibility rules. Standards create consistency and support exchange.
Internal standards may define: - naming conventions; - identifiers; - custom attributes; - security/visibility rules; - classification conventions.
External standards can support shared registration/exchange models.
ISO/IEC 11179
Chapter 12 presents ISO/IEC 11179 as a Metadata Registry standard supporting precise standardized data-element definitions, naming/identification, registration, and Metadata-driven exchange.
The chapter names Parts 1, 3, 4, 5, and 6. Exam priority is the purpose—not memorizing every clause.
Governance must monitor compliance. A published naming standard has little value if source teams ignore it and the enterprise repository cannot reconcile equivalent objects.
Manage Metadata Stores
Once a repository exists, it becomes an operational system that requires control:
- monitor harvest/import jobs;
- check warnings and logs;
- manage interfaces;
- resolve errors and failed refreshes;
- administer access and changes;
- watch capacity;
- generate metrics;
- train users/operators;
- maintain Governance oversight.
A failed harvest from a modeling repository is normally a store-management problem, not a reason to rewrite Metadata strategy.
Standards vs Store Management
- Apply standards → define/enforce conventions.
- Manage stores → keep repository movement, refreshes, interfaces, jobs, and administration functioning.
Governance vs administration
Repository administrators may execute governance controls, but they do not replace Governance. Governance decides ownership, standards, quality expectations, approval, security, stewardship, and accountability.
Source anchor: pp. 401–402 and 413–415.