Difference between revisions of "Data source/ACCUITY/data model/Bank/Fax"

From CDQ
Data source/ACCUITY/data model/Bank/Fax
Jump to navigation Jump to search
(Typo corrected)
(Spreadsheet import)
 
Line 1: Line 1:
{{Data model concept property
+
{{Data model concept
|name=Fax
+
|name=PhysicalAddress2
|description=The fax machine telephone number.
+
|description=Additional address information for the institution.  
|data model=Data source/ACCUITY/data model
+
|data source=Data source/ACCUITY
|technical key=Fax
+
|technical key=PhysicalAddress2
 
|parent concept=Data source/ACCUITY/data model/Bank
 
|parent concept=Data source/ACCUITY/data model/Bank
 
|cardinality=ZERO_OR_ONE
 
|cardinality=ZERO_OR_ONE
|path=Bank.Fax
+
|path=PhysicalAddress2
 +
|concept role=LEAF
 
}}
 
}}

Latest revision as of 13:24, 3 December 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. PhysicalAddress2
Description Informal and comprehensive human-readable definition of a concept. Additional address information for the institution.
Example A simple example supporting the understanding of a concept, business rule, etc. no example available
Part of Hierarchical relation between two concepts of the CDQ Data Model. Data source ACCUITY
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. PhysicalAddress2
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. Bank (ACCUITY)
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_ONE
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
Concept type Complex data type of a data model concept, defined by another data model concept. Allows re-use of data type concepts, e.g. for several address types in a data model. SELF
Path JSON Path to identify attributes in a data item. PhysicalAddress2
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