Difference between revisions of "Fraud case/description"
Fraud case/description
Jump to navigation
Jump to search
(Spreadsheet import) |
(Spreadsheet import) |
||
Line 1: | Line 1: | ||
− | {{Data model concept | + | {{Data model concept |
|name=Fraud Case Description | |name=Fraud Case Description | ||
|description=Some explanation and background to a [[fraud case]]. | |description=Some explanation and background to a [[fraud case]]. | ||
− | |data | + | |data source=Data source/CDQ |
|technical key=FRAUD_CASE_DESCRIPTION | |technical key=FRAUD_CASE_DESCRIPTION | ||
|parent concept=Fraud case | |parent concept=Fraud case | ||
|cardinality=ZERO_OR_MORE | |cardinality=ZERO_OR_MORE | ||
|path=fraudCase.description | |path=fraudCase.description | ||
+ | |concept role=LEAF | ||
}} | }} |
Latest revision as of 08:00, 30 November 2020
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. | Fraud Case Description |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | Some explanation and background to a fraud case. |
Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source CDQ.POOL |
Technical key Defines a unique key by which e.g. data model concepts can be referenced in a technical integration context. These keys are unique in the CDL context. | FRAUD_CASE_DESCRIPTION
|
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | Fraud Case (CDQ.POOL) |
Cardinality Cardinality of data model concepts.<br/><code>ZERO_OR_ONE</code>: Optional, but max. 1 instance related to its parent.<br/><code>EXACTLY_ONE</code>: Exactly 1 instance related to its parent.<br/><code>ZERO_OR_MORE</code>: Optional, multiple instances related to its parent may exist.<br/><code>ONE_OR_MORE</code>: Mandatory, multiple instances related to its parent may exist. | ZERO_OR_MORE
|
Data type Data type of a data model concept, i.e., <code>ARRAY</code>, <code>BOOLEAN</code>, <code>DATE</code>, <code>ENUM</code>, <code>INTEGER</code>, <code>OBJECT</code>, or <code>STRING</code>. | n/a |
Path JSON Path to identify attributes in a data item. | fraudCase.description
|
Concept role The role of a Category:Data model concept in the tree structure of a data model.<br/><code>ROOT</code>: Root concept in a data model, i.e., no parent concepts.<br/><code>NODE</code>: Structure concepts in a data model, i.e., parent and child concepts.<br/><code>LEAF</code>: Leaf concept in a data model, i.e., no child concepts, provides the effective data values.<br/> | LEAF
|
Mapping |