Glossary
| Term | Meaning |
|---|---|
| Datablau DAM | Governance product family covering administration, core governance, and related modules |
| Metadata | Information describing resource names, structure, origins, meaning, and ownership; distinct from business records |
| License | Module entitlement; separate from role and data permissions |
| DDC | Asset product domain: Data Catalog and Data Marketplace |
| DDS | Security product domain: Data Security and Security Gateway |
| SQLink | Independently deployable and licensed lineage platform that can extend DAM |
| DIG | Data Governance Agents, DAM's AI assistance; the UI module is Intelligent Data Governance |
| Data Marketplace | Business discovery, exploration, and requests for assets and products |
| Data Services | API development, publication, requests, and calling application management |
| API marketplace | Published APIs and documentation for application access requests |
| Calling application | Identity representing an API consumer, managed separately from API authorization |
| Data Supermarket | Current front-office page or capability name within Data Marketplace |
| Standards mapping | Association of a metadata field with an applicable standard; semantics and technical properties still require validation |
| Intelligent Matching | Candidate basic-standard recommendations based on field properties for acceptance or rejection |
| Grouped Recommendations | Unmapped fields grouped by Chinese business name to identify potential shared definitions |
| Automated Standards Validation | Task-based checks of field-standard mappings; distinct from checking actual data values |
| Data quality validation | Execution of technical rules against actual records |
| Basic Lineage Management | Metadata lineage entitlement, separate from SQLINK |
| Metric Standards | Basic metric definitions and dimension management within Data Standards |
| Metric Management | Atomic, calculated, and qualified metric definitions, mappings, queries, monitoring, and access; separately licensed as Data Metrics |
| Security Gateway | DDS server and Datablau JDBC Driver for dynamic masking and audit |
| Dynamic masking | Identity- and policy-based query presentation without modifying source values |
| Classification information item | Reusable semantics describing a class of information and its security category; not an actual database field |
| Metamodel | Types, attributes, and relationships defining governed object structures |
| Built-in metamodel | Product-provided model available for harvesting or management |
| Custom metamodel | Enterprise-designed and published object model |
| Object collection | Container grouping objects of one type |
| Attribute collection | Definitions of object fields, types, required status, and presentation |
| Root node | Starting object or collection for hierarchical harvesting or display |
| Lineage space | SQLink management scope for database/report resources, jobs, and results |
| Namespace | Identity scope separating same-name lineage objects across systems or environments |
| Schema | Database naming scope used in harvesting and lineage identity |
| DBLink | Database-to-database link used in cross-database lineage |
| Parsing task | Extracts lineage from SQL, scripts, or task files |
| Lineage subgraph | Nodes and edges selected by reference object, direction, depth, and filters |
| Transformation logic | Scripts, expressions, or steps connecting inputs to outputs |
| Forced metadata binding | Requires parsed objects to match harvested metadata; failure to match can fail parsing |
| Preprocessing | Splitting, replacing, filtering, or formatting input before parsing |
| Parsing report | Successes, failures, omissions, and errors for a run |
| Database resources | Database metadata registered in a lineage space |
| Report resources | Report platforms, files, and objects in a lineage space |
| OpenLineage | Open event protocol describing jobs and input/output datasets |
| Lineage map | Graph exploration of upstream/downstream paths and levels |
| Lineage level | Granularity: schema, entity, property, or operator |
| Lineage depth | Number of relationship expansion steps |
| Second-level lineage | Processing detail beneath the current relationship view |
| Application scenario | Saved analysis scope for monitoring, impact, or structural quality |
| Impact broadcast | Notification of potential impact; separate from change approval |
| Metadata coverage | Coverage of registered or harvested metadata within a defined scope; use the page's calculation |
| Lineage coverage | Coverage of lineage objects or relationships within a defined scope |
| Operator lineage | Connections among processing operators, inputs, and outputs |
| Code slicing | Focused code fragments relevant to selected object relationships; source scripts remain unchanged |
| Broken-lineage analysis | Investigation of missing upstream, downstream, or intermediate nodes |
| Lineage-based recommendations | Catalog or classification suggestions using dependency relationships, subject to review |
| Data product | Asset collection or service description discoverable and requestable through the marketplace |
| Data intelligence space | DIG workspace for assets, documents, governance phases, and context publishing |
| Source configuration | System Agent or published template used to instantiate a space agent |
| Governance context | Authorized assets, semantics, and documents used by an agent; not copied source data |
| Context quality report | Coverage checks for assets, semantics, standards, lineage, and classification; not model accuracy |
| Space Agent | Natural-language query access to authorized space context |
| Space MCP | Published context tools for external AI applications; opposite direction from DIG calling an external MCP |
| MCP | Model Context Protocol for connecting agents to capabilities through tools |
| LLM | Large language model for text understanding and generation |
| Text Embedding | Model converting text to numeric vectors for semantic retrieval |
| Skill | Reusable task instructions and execution methods |
| Governance Sprite | Reusable capability performing one bounded atomic task |
| Routine | Workflow combining Sprites with node order, mappings, and failure policies |
| Input schema | Parameter names, types, and constraints; distinct from a database schema |
| Proactive governance | Resident tasks monitoring changes and generating proposals for review |
