🗂️Data assets

What is a data asset?

In the left panel of you Catalog instance, under the Data section, you are going to find tables & views sourced directly from data warehouses and grouped under databases and schemas.

Tables & Columns documentation

Documentation can be added at both the table level - in the Readme section - and at the columns level - on the right hand side of each column. Documentation can also be imported directly from the data source, if it exists..

Below are some examples of questions that your table readme documentation could / should answer:

• Why do we have the table? What is its purpose? Describe why the table exists / main use cases: eg part of the ETL process that calculates x or main transactions table used to for basket revenue analysis

• Who should use it? Target audience

• What does it contain? Describe what the table contains: Key measures and attributes History: years of data Granularity: daily / transaction level etc Key sources (if not automated and present in tags)

• How and when is it refreshed? Describe how the data is captured and how frequently it is refreshed

• Anything special we should know? Mention particular calculations, joins etc. If this is an asset used in presentation layer for analysis - consider creating separate Knowledge entries for metrics or important attributes

• Technical observations: specific SQL examples etc

Similarly, for column documentation, ensure you add a short description of the meaning of the column, enumerate values if it is a an enum type, consider creating a knowledge page and pin it (see Pinned assets & Mentions) if it represents a major metric of business concept.