Discover data
Build a resource inventory through metadata harvesting and cataloging.
Metadata Management
Follow governance tasks from resource discovery to trusted data use, with clear product and permission boundaries.
Datablau DAM covers administration, metadata, standards, quality, assets, security, services, lineage, and Data Governance Agents. Each module has its own goals, entry points, permissions, and workflows. Read by module or follow the governance journey.
| Module | Purpose | Guide |
|---|---|---|
| System Management | Users, organizations, roles, workflows, tasks, configuration, licenses | Administration |
| Metadata Management | Harvest and maintain tables, fields, reports, files, and basic object lineage | Metadata |
| Data Standards | Definitions, codes, dictionaries, metrics, dimensions, field mappings | Standards |
| Data Quality | Rules, validation, remediation, verification | Quality |
| Data Catalog | Catalog structures, registration, inventory, publication | Catalog |
| Data Marketplace | Discover and request assets or products with approval records | Marketplace |
| Data Security | Classification, discovery, policies, masking governance | Security |
| Security Gateway | Server and JDBC-based dynamic masking and audit | Gateway |
| Data Services | Develop, test, publish, request, and call APIs | Services |
| Data Lineage | Maps, parsing, impact analysis, application scenarios | SQLink |
| Data Governance Agents | AI-assisted governance through Intelligent Data Governance | DIG |
For API publication and consumption, use Data Services. Product requests and API authorization are separate workflows. For governance metadata integration, use the REST API guide, distinct from published business data APIs.
| Capabilities | Responsibilities and boundaries | When to combine |
|---|---|---|
| Metadata lineage and SQLink | Metadata provides object-based dependency views. Independently deployable SQLink adds spaces, parsing, maps, impact, and scenarios. Basic lineage entitlement is separate from SQLink. | Use basic views for object tracing; use SQLink to build and validate advanced paths. Connectivity and synchronization follow deployment settings. |
| Metric Standards and Metric Management | Both belong to Data Standards. The former maintains definitions and dimensions. The latter adds atomic/calculated/qualified metrics, mappings, queries, monitoring, and permissions under the Data Metrics license. | Use basic definitions for consistent meaning; use management for operational queries and monitoring. Definitions alone do not produce values. |
| Catalog and marketplace | Catalog administrators organize, maintain, and publish assets. Consumers discover and request them. Marketplace approvals retain decisions; they do not deliver data. | Publish discoverable content, submit requests, then coordinate offline delivery. |
| Security and gateway | Security defines classification and policies. Gateway server and JDBC Driver enforce dynamic masking and audit on configured paths. | Define protection requirements, configure the actual access route, and verify results. |
| DAM and DIG | Traditional DAM modules hold governance objects and results. DIG assists tasks and organizes governed semantics and knowledge into context. Its UI name is Intelligent Data Governance, subject to license and permissions. | Review proposals and verify target results; validate space context before publishing to AI applications. |
Complete system preparation for organizations, roles, workflows, and sources. Check license, functional permissions, data scope, and approval policy separately. An available menu does not grant every operation or object.