Reference Data and Metadata Management
Capability/Reference Data and Metadata Management
Jump to navigation
Jump to search
Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language. | Reference Data and Metadata Management (category: Transparency, sort rank: 910, product: CDQ Cloud Platform) |
---|---|
Short description Informal and short human-readable definition of a concept. | Continuous updates of global data requirements due to legal changes or data standards. |
Description Informal and comprehensive human-readable definition of a concept. | Data quality is, beside other factors, compliance of given data to laws and standards, i.e. data requirements. Such requirements come from national regulation and change over time. Clients have to track such requirements country by country and continuously. For many (and a growing number of) countries, officially registered company information is provided as Open Data. Such reference data does not follow any standardized data model or data provision. Identification, integration, and continuous updates cause effort for each data source. The Data Sharing Community collaborates on identifying data requirements globally. The same for identifying reference data sources, both Open Data and commercial. CDQ collects all such information, machine-readable in a semantic graph, as well-structured metadata. CDQ derives data quality rules from this semantic metadata, automatically, for measuring data quality. And CDQ automatically integrates all reference data into a Data Pool. All metadata and reference data is accessible also for Clients, both documented for humans and machine-readable, in this wiki. |
Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it. | LIVE
|
Use cases | Understand CDQ Cloud Services |
Apps |
Following apps provide this capability
|
APIs |
Following APIs provide this capability
|
Features
Feature | Short description Informal and short human-readable definition of a concept. | Release status The release status in terms of development progress or maturity of a product feature or a business capability.<br/><code>EMPTY</code> (0): No feature considered yet, just rough idea for capability.<br/><code>IDEA</code> (1): Just an idea, not yet designed in detail.<br/><code>DESIGN</code> (2): Software design ready, development not yet started.<br/><code>DEVELOPMENT</code> (3): Software development in progress.<br/><code>ALPHA</code> (4): First functional release, in terms of a Minimal Viable Product (MVP).<br/><code>BETA</code> (5): Tested by selected users.<br/><code>RC</code> (6): Release candidate, fully tested, not yet used in production by many customers.<br/><code>LIVE</code> (7): Used in production by customers, fully monitored and supported.<br/><code>DEPRECATED</code> (-1): End of life planned, but still available.<br/><code>EOL</code> (-2): End of life, historic service, no longer available.<br/><code>BROKEN</code> (-3): Service was used in production but is currently not available. However, CDQ tries to repair or reactivate it. |
---|---|---|
Administrative Area Metadata | Managed reference data for administrative areas with language-specific terms and short names according to ISO 3166-2. | LIVE
|
Business Identifier Metadata | Managed reference data for identifiers with default mapping to SAP fields and corresponding country. | LIVE
|
CDQ Data Model | Basic data concepts of CDQ Cloud Services. | LIVE
|
Capabilities and Features | Capabilities and features provided by CDQ Cloud Services. | LIVE
|
Country Metadata | Managed reference data for countries with language-specific names and short names according to ISO 3166-2. | LIVE
|
Data Quality Rules | Documentation of data quality rules with explanation and technical constraints to validate business partner data records. | LIVE
|
Data Source Metadata | Managed reference data for external data sources with documentation of the sources' data models and mappings to the CDQ Data Model. | LIVE
|
Legal Form Metadata | Managed reference data for legal forms with official and commonly used abbreviations and corresponding country. | LIVE
|
Registration Authority Metadata | Managed reference data for issuing bodies of identifiers | LIVE
|
Use Cases | Use cases to use capabilities and features of CDQ Cloud Services for. | LIVE
|
Post Office Box Terms | Managed reference data for postal delivery points of type Post Office Box (CDQ.POOL) used for identification, extraction, harmonization and standardization. | BETA
|
Street Terms | Managed reference data for thoroughfares of type Street (CDQ.POOL) used for harmonization and standardization. | BETA
|
Custom Rulebook | Data quality- and automation rulebook customized for a client | ALPHA
|
Data Maintenance Procedures | Collection of metadata (e.g. data sources, data quality rules) per country. | ALPHA
|
Bank Account Metadata | Managed reference data for bank accounts worldwide | DEVELOPMENT
|
Facts and Figures
Administrative Areas | 3,351
|
---|---|
Countries | 317
|
Data Quality Rules | 2,423
|
Data Sources (external) | 0
|
Identifiers | 432
|
Legal Forms | 942
|
Registration authorities (issuing bodies) | 714
|
Terms | 1,682
|
Business capabilities | 32
|
Product features | 168
|
Use cases | 31
|