• CIA rating
CIA rating of the data product (link to data classification guideline)
We need to look this
• Steward
A person with registered profile in the data catalogue that is responsible for the data product (link how to register and role description)
As a part of Data Holder information
• Information Model
(Embedded) link or attached file to an information model (link to business term) describing the logical structure of the data.The information architecture team can be contacted through the catalog with conversation or by email (link).
Currently schemaLocationURL as a part of DataOps information. Schematype might be needed also.
• Solution Overview
Describe the data product architecture and internal structure if needed. The aim is to give clarity to how this data product is operating.
Is description enough?
• Data Profiling
Data profiling gives an overview of what type of data the data product has and some statistics about it. A link to the data profiling results can be presented here, or summary of the results.(Link to data profiling guideline)Under development: There is an API in development that allows data product teams to publish their data profiling results into the catalog as soon as the profling results are available.
Is Description enough?
• Observability Metrics
Observability metrics are details about the operation status of the data product. Examples of metrics that can be of value to share with consumers (standard metrics is under development):Metric Value Notes
Latest update time 2022-01-03 12:31:00
Latest data time stamp 2022-01-03 10:00:00
Number or records 12456 Under development: There is an API in development that allows data product teams to publish their data metrics into the catalog as soon as the metrics are available.
As a part of document level attributes, mandatory?
• Planned Updates
Planned updates indicate future changes that the consumers should be aware of. Usually only a major changes need to be presented, that have an effect on data usage.
As a part of document level attributes, optional?
• Change Log
Log of all the changes with regards to the data product. Should be aligned with semantic versioning of the data product.
As a part of DataOps?
kyyberi
commented
4 months ago
• CIA rating CIA rating of the data product (link to data classification guideline)
We need to look this• Steward A person with registered profile in the data catalogue that is responsible for the data product (link how to register and role description)As a part of Data Holder information• Information Model (Embedded) link or attached file to an information model (link to business term) describing the logical structure of the data.The information architecture team can be contacted through the catalog with conversation or by email (link).Currently schemaLocationURL as a part of DataOps information. Schematype might be needed also.• Solution Overview Describe the data product architecture and internal structure if needed. The aim is to give clarity to how this data product is operating.Is description enough?• Data Profiling Data profiling gives an overview of what type of data the data product has and some statistics about it. A link to the data profiling results can be presented here, or summary of the results.(Link to data profiling guideline)Under development: There is an API in development that allows data product teams to publish their data profiling results into the catalog as soon as the profling results are available.Is Description enough?• Observability Metrics Observability metrics are details about the operation status of the data product. Examples of metrics that can be of value to share with consumers (standard metrics is under development):Metric Value Notes Latest update time 2022-01-03 12:31:00 Latest data time stamp 2022-01-03 10:00:00 Number or records 12456 Under development: There is an API in development that allows data product teams to publish their data metrics into the catalog as soon as the metrics are available.As a part of document level attributes, mandatory?• Planned Updates Planned updates indicate future changes that the consumers should be aware of. Usually only a major changes need to be presented, that have an effect on data usage.As a part of document level attributes, optional?• Change Log Log of all the changes with regards to the data product. Should be aligned with semantic versioning of the data product.As a part of DataOps?