Hi to all,
I am very new here and I hope I am not infringing any policy with asking a very basic question.
As a Data architect, part of my job is to build the architecture (capabilities at the moment) of a MDM (Master Data Management) system for an institution.
So far Data concepts and Data Flows are partially documented.
In your opinion, what would be the best content to cover for a MDM documentation dedicated for both IT, users and data Management team.
Many t hanks in advance for your help.
--------------
Here is the summary content that I am willing to expose in this documentation
Drivers and principles
Data Sources (Integration and quality, acquisition)
Data Validation, Standardization, Enrichment
Entity Resolution (Matching Decision process, Decision Performance, Algorithms, Entity Consolidation rules)
Relationships (Affiliation, hierarchy)
Data Sharing Architecture (Strategy, Latency, Lineage, Storage, distribution)
Data Model Management (Data Concepts, data flows)
------------------------------
Jerome Gransac
------------------------------
#MasterDataManagement