CDQ Data Model

From CDQ
Data source/CDQ/data model
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. CDQ Data Model
Short description Informal and short human-readable definition of a concept. Basic data concepts of CDQ Cloud Services.
Description Informal and comprehensive human-readable definition of a concept. An important prerequisite for collaborative data management is a common understanding of the shared data. For the CDQ Data Sharing Community, this common understanding is specified by the CDQ Data Model. The concepts of this model are defined and documented in this wiki which can be used as a business vocabulary. Moreover, the wiki provides a machine-readable interface to reuse this metadata by using semantic annotations.
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
Concept(s) Specifies concepts which are controlled by a data quality rule or another schema or constraint.
Business capability Which business capabilities require this feature/data capability Reference Data and Metadata Management
Use cases Understand CDQ Cloud Services
Constraint(s) This feature has no documented constraints
Profile Profiles in which a feature is used, i.e. executed with its standard configuration (e.g. rule engine profiles)

Data model graph

AddressBank account/bankBusiness partnerAddress/versionAddress/administrative areaBank accountFraud caseBank account/bank/contact/contact emailBank account/bank/contactBank account/bank/identifier/issuing bodyBank account/bank/identifierBank account/bank/identifier/typeBank account/bank/contact/phone numberBank account/bank/relationBank account/bank/relation/typeBank account/bank/contact/websiteBank account/bank/nameBank account/bank/name/versionBusiness partner/relationBusiness partner/partner profile/classificationBusiness partner/partner profileBusiness partner/external contextBusiness partner/external context/identifiersBusiness partner/nameBusiness partner/relation/classBusiness partner/statusBusiness partner/status/typeAddress/care ofBusiness partner/partner profile/contact emailAddress/countryFraud case/fraudsterAddress/geographic coordinatesBusiness partner/identifierBusiness partner/identifier/issuing bodyBusiness partner/identifier/typeBusiness partner/legal formAddress/localityBusiness partner/partner profile/minority indicatorAddress/opening hoursBusiness partner/partner profile/phone numberAddress/post codeAddress/postal delivery pointAddress/premiseAddress/thoroughfareBank account/trust scoreBank account/trust score/metadataBusiness partner/partner profile/websiteThis is a graph with borders and nodes that may contain hyperlinks.

Data model concepts