# Data Management

## A Unified Approach to Data Management

In an era where data volume outpaces human capacity, organisations can no longer afford to treat data as a series of disconnected tasks managed by disconnected tools. A unified approach to data management represents a fundamental shift — an integrated architectural layer that connects the right data to the right people at the right time.

By aligning Cataloging, Quality, Preparation, and Semantic Modelling into a single continuous capability, the platform transforms raw, fragmented information into a strategic corporate asset — discoverable by default, trustworthy by design, and ready for action.

### The Data Value Chain: From Discovery to Decision <a href="#the-data-value-chain-from-discovery-to-decision" id="the-data-value-chain-from-discovery-to-decision"></a>

A seamless data-management capability follows a logical progression that mirrors the natural lifecycle of information — from discovery, through validation and refinement, to business interpretation.

<table data-header-hidden><thead><tr><th width="109.99996948242188"></th><th></th></tr></thead><tbody><tr><td><strong>Stage</strong></td><td><strong>Capability</strong></td></tr><tr><td>Discover</td><td><strong>Data Catalog</strong> — automated metadata harvesting, search and discovery, lineage, and social collaboration.</td></tr><tr><td>Validate</td><td><strong>Data Quality</strong> — automated profiling, six-dimensional quality scoring, alerting and remediation, and trust dashboards.</td></tr><tr><td>Refine</td><td><strong>Data Preparation</strong> — self-service wrangling, masking, and PII detection, and reusable transformation recipes.</td></tr><tr><td>Translate</td><td><strong>Semantic Layer</strong> — centralised business definitions, natural-language mapping, row-level security, and universal connectivity.</td></tr></tbody></table>

## Key Outcomes

* [x] **Operational Agility:** Reduce data-engineering backlogs by up to 60% through self-service.
* [x] **Governed Decentralisation:** Business units innovate freely while central oversight and security are preserved.
* [x] **Enhanced Data Literacy:** Bridge the gap between technical data structures and the business-critical questions they answer.

{% hint style="info" icon="bullseye-arrow" %}
**The Vision:** We are not just building a repository; we are building a "live" ecosystem where data is discoverable by default, trustworthy by design, and actionable by everyone.
{% endhint %}

## Quick Reference <a href="#quick-reference" id="quick-reference"></a>

### Module Map <a href="#module-map" id="module-map"></a>

<table data-header-hidden><thead><tr><th width="268.39996337890625"></th><th></th></tr></thead><tbody><tr><td><strong>Capability</strong></td><td><strong>Navigation</strong> <strong>Path</strong></td></tr><tr><td><a href="/pages/bdbdUjvIAAif7AKHSyse">Data Catalog</a></td><td>Left navigation → Catalog</td></tr><tr><td><a href="/pages/Y3EUs10ckQe98gBSz7tL">Data Quality (Catalog scope)</a></td><td>Catalog → asset → Data Quality tab</td></tr><tr><td><a href="/pages/WgHOmptUx8zw8I1GfM1U">Data Quality (Dataconnector scope)</a></td><td>Data Center → dataconnector → Create Data Quality</td></tr><tr><td><a href="/pages/qdGS4uEwtm5vdJFqkkRA">Data Preparation</a></td><td>Data Center → Data Preparation</td></tr><tr><td>Business Objects</td><td>Catalog → asset → Data Connector → <a href="/pages/60kb4QfIxEAktNqt8vwZ">Ontology tab</a></td></tr><tr><td>Semantic Layer</td><td>Catalog → asset → Data Connector → Ontology &#x26; Taxonomy &#x26; Vocabulary</td></tr><tr><td><a href="/pages/EsVTHvJyPz6c9vQCi42N">Lineage</a></td><td>Catalog → asset → Lineage tab</td></tr><tr><td><a href="/pages/NkIrAGSEB1rIJmOUAYwe">History </a></td><td>Catalog → asset → History tab</td></tr></tbody></table>

### Glossary <a href="#glossary" id="glossary"></a>

<table data-header-hidden><thead><tr><th width="150.79998779296875"></th><th></th></tr></thead><tbody><tr><td><strong>Term</strong></td><td><strong>Definition</strong></td></tr><tr><td>Asset</td><td>Any catalogued entity — dataset, table, model, dashboard, report, or Business Object.</td></tr><tr><td>Business Object</td><td>A typed representation of an enterprise concept, with properties, measures, and relationships.</td></tr><tr><td>Classification</td><td>A sensitivity tag (Public, Internal, Confidential, PII) applied to an asset.</td></tr><tr><td>Entitlement</td><td>The set of permissions that determine what a user can do with an asset.</td></tr><tr><td>Lineage</td><td>The traceable flow of data from source to consumer.</td></tr><tr><td>Metric Store</td><td>The centralised repository of governed measures and dimensions defined on Business Objects.</td></tr><tr><td>Recipe</td><td>A reusable, versioned sequence of data-preparation transformations.</td></tr><tr><td>Semantic Layer</td><td>The platform layer that translates physical data into governed business concepts.</td></tr><tr><td>Steward</td><td>A user accountable for an asset's metadata, quality, and lifecycle.</td></tr><tr><td>Trust Score</td><td>A consolidated health rating is derived from quality rule results across the six dimensions.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bdb.ai/bdb-user-documentation/platform-modules/11.0/data-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.