Collections

Collections are used to group a range of different data items to make discoverability and governance of data assets easier.

For example, you can create a collection of Critical Data Elements

Overview of Collection Types

Collections are created in 3 ways:

Automated data collections: These collections are linked automatically tagged to your data based on different rules. An example is usage, which tags data and content used daily/weekly/monthly etc. You can also create linking rules to automatically link data items to a collection using business rules written in a regex format (aka Regex Rule).
Automated platform collections: These collections are used for by the platform to control specific attributes. An example is data role, which allows you to assign users to a specific role within K.
Manually created collections: Data Governance Managers, Data Managers and Administrators have the ability to create manual collections.

How Manual Collections Work

Manual collections are a great way to group your data items. Below is a visual example of how data items are grouped into instances which are linked to a collection.

After your link a data item to a collection, all manual collections appear as an orange tag like the below example

If the collection name you are looking for is missing, reach out to your Data Manager or Data Governance Manager to ask for their help in creating the new collection

Collection Governance Report

Data Owners, Stewards and Data Governance Managers have access to the Collection Governance Excel Report that can be run at the Instance level.

The report can be downloaded via the Governance tab on the Instance profile page.

The Governance Report contains the following information for each data asset that has been linked to the instance:

Trust score
Recent usage over the last 90 days
Total usage by all users since creation
Use cases the asset has been Verified For / Verified Not For
Classification
Domain
Stewards
Owner
Lineage mapping status (e.g. downstream only or both upstream and downstream have been mapped)
Confirmation if data asset description has been completed
Total number of unique data quality tests linked to the data asset
Number of data quality tests run in the last 90 days