This page defines the core terms and concepts used throughout the K platform and this Knowledge Base. Familiarising yourself with these terms will help you get the most out of K.
Platform & Architecture
|
Term |
Definition |
|---|---|
|
K |
The core KADA data knowledge platform — used for data discovery, knowledge management and data governance. |
|
KADA's data quality module, used to define, run and monitor data quality checks across your data estate. |
|
|
K's AI capabilities, including auto-generated descriptions and smart suggestions for glossary terms and metadata. |
|
|
A KADA-provided Python library deployed by your team to extract and load metadata from data sources into K. Typically used for on-premise or restricted sources. |
|
|
The service used for connecting to, extracting and loading metadata and usage logs from data sources and tools directly into K. |
|
|
A score calculated by K to reflect the relevance, freshness and quality of a data asset, used to rank search results. |
Data Assets & Objects
|
Term |
Definition |
|---|---|
|
Data Asset |
Any piece of data or content catalogued in K — including tables, columns, reports, dashboards, pipelines, code, and more. |
|
The central page in K for a given data asset. Contains automated and manually curated metadata, lineage, usage, knowledge, issues, and data quality information. |
|
|
A user-defined grouping of data assets. Collections are used to organise assets by domain, criticality, team, or any other meaningful category. |
|
|
Collection Instance |
A specific member or record within a Collection (e.g. a single Critical Data Element in a "Critical Data Elements" collection). |
|
An object in K that provides context for a data asset — such as a glossary term, tag, or policy — used to describe, classify and link assets. |
|
|
The upstream and downstream relationships between data assets. K automatically detects and maps lineage across your data ecosystem. |
Knowledge & Governance
|
Term |
Definition |
|---|---|
|
A defined business or technical definition linked to one or more data assets to provide consistent meaning across the organisation. |
|
|
Tag |
A label applied to a data asset to classify or categorise it (e.g. PII, Sensitive, Finance). Tags can be applied manually or automatically via business rules. |
|
Data that can be used to identify an individual. K includes a built-in PII scanner to detect potential PII in your data estate. |
|
|
Data Issue |
A recorded problem with a data asset — such as a quality failure, incorrect value, or known defect. Issues can be tracked and managed directly in K. |
|
An automated upstream and downstream analysis that helps assess the impact of a change to a data asset on dependent assets. |
Users & Access
|
Term |
Definition |
|---|---|
|
Business User |
A consumer of data products (reports, dashboards, analyses). Has read access to K content and can contribute knowledge. |
|
Data Worker |
A technical user who works with data day-to-day (e.g. data analyst, data engineer, data scientist). |
|
Data Owner |
A user accountable for the collection, handling and use of a data product or data domain. |
|
Data Governance User |
A user responsible for managing and governing the use, classification, description and access to data. |
|
Data Manager |
A user responsible for the oversight of data platforms and the data ecosystem. Has the highest level of access among non-admin roles. |
|
Administrator |
A platform admin with the ability to configure K, onboard new sources, manage users and change global settings. |
|
Role Hierarchy |
Roles in K are inherited — higher roles include the permissions of lower roles. |
Platform Features
|
Term |
Definition |
|---|---|
|
A daily email from K summarising key updates in your data ecosystem that are relevant to your profile and the data assets you follow. |
|
|
A personalised feed on the K home page showing recent changes and updates across your data ecosystem. |
|
|
A self-service feature that allows users to ask natural language questions about their data ecosystem and receive data-driven answers. |
|
|
A page in K where users can create, save and share reusable search filters. |
|
|
The section in K that lets you navigate and explore your organisation's complete data landscape. |
|
|
A personalised view within the Data Ecosystem section showing how you specifically interact with the data estate. |