Metadata Model: The Core Integration Layer

The Metadata Model is the architectural CORE for the entire Canonical Data Model implementation. It is not simply another layer but the central driver that orchestrates integration, ETL automation, data quality enforcement, and lineage tracking across all three layers (LDZ, RDV, and Unica 360).

Why Metadata is the Core:

• Drives Unified Integration: Metadata tables maintain all mappings between source systems, LDZ, RDV, and Unica 360, enabling seamless data flow across layers.
• Enables ETL Automation: Generic ETL processes read metadata definitions to dynamically generate and execute transformations. New subject areas require only metadata configuration, not code changes.
• Enforces Data Quality: Metadata-driven data quality definitions are executed at every layer, ensuring consistent validation and measurement across all subject areas and business processes.
• Captures Complete Lineage: From source → LDZ → RDV → Unica 360, metadata automatically tracks every transformation, enabling end-to-end impact analysis and compliance reporting.
• Enables Rapid Scaling: As the canonical model evolves to support new subject areas (Party, Account, Product, Campaign, etc.), metadata configuration enables rapid onboarding without architectural changes.

Schema: Metadata schema (typically dev_meta, prod_meta, etc.)