🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →

Sequence 210 — Manual metadata build - glossary vs dictionary vs catalog

Context: Chapter 12 - Metadata Management | Applied Lab Deepening
Source: CDMP Master Execution Manual

When / purpose

Make the distinctions concrete using Meridian artifacts before touching a governance platform.

What you should learn

• Business glossary focuses on business terms/meaning.
• Data dictionary focuses on technical/structural data-element detail.
• Catalog brings broader searchable asset context together.
• Lineage and ownership add context but do not collapse the distinctions.

What to read / study

• MUST: Chapter 12 applied lab folder — use the source-grounded manual metadata lab once built; do not let OpenMetadata/Purview define the DMBOK distinction.
• MUST: Meridian artifacts from earlier chapters — reuse real lab outputs; do not invent fake assets if real Meridian examples exist.

Do this in order

1. Choose 10–20 existing Meridian assets/fields.
2. Create a small business glossary.
3. Create a technical data dictionary for selected fields.
4. Create a catalog register linking assets, owners/stewards, classifications and source/target context.
5. Explain what belongs in each and what would be duplication.

Meridian application

Reuse Customer/Product/Order, warehouse, master/reference and quality artifacts already created.

Create / save

Glossary + dictionary + catalog register.

Stop / boundary

Stay inside the current source/skill boundary. Do not pre-learn later chapters or engineering depth. If the separate applied-lab artifact is required but missing, this card’s learner gate still controls; migration does not create it.

Completion gate

You can defend the placement of each piece of metadata and explain the distinctions without naming a product.

NEXT → Sequence 211

Operationalized from the verified canonical 00C Master Execution Manual; not a verbatim transcription. Separate chapter artifacts are not created by this migration.