The Purpose of the Data Catalog is to maintain business objects , its definitions, and the tables where it is stored in the Data Ocean.
It will also help in categorizing the data into different domains. Having a Data Catalog enables Data Governance team to control, and monitor the business objects with direct access on the information related to where it is stored and assign Data Owner to it.
How to document the Data Catalog :
The Data Catalog has been divided into domains: Finance, Industrial , Marketing & Sales etc.
Each domain sheet has two sections of data catalog:
1. Data domain , Business object , Business Object definitions
Maintained/ defined by Data Functional Analyst / Data Owners
Functional analyst along with PO / business defines the business objects and then with help of DG they categorized it into the domain.
2. Tables for the Object (DM Tables), Attributes, Business Object Parent (for Attributes) , Contributor : documented/defined by Data architect
Once the Business object , its definition and domain are defined, the Data Architect can input following information in the columns:
a. Tables for the Object (DM Tables): Document the table associated with it.
b. Attribute field : This field is optional incase there is business object which is at the field level then maintain this field otherwise its optional.
For example if there is business object customer address and in the table there is field called as customer address then maintain the field name in this column.
c. Business Object Parent (for Attributes): Here parent business object name should be maintained if it exists.
For example business object material group the parent business object would be material etc.
d. Contributor : Person who is working on it how it is used etc.
