Contact Email Address (CDQ.POOL)

From CDQ
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. Contact Email Address
Description Informal and comprehensive human-readable definition of a concept. The actual email address such as info@cdq.com
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 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. EMAIL_VALUE
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. Business partner/partner profile/contact email
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. EXACTLY_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. profile.contactEmails[0].value
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

mapping source: EMAIL (BE.CCD), mapping: BE.CCD EMAIL_VALUE
mapping source: CORREIO ELETRONICO (BR.RF), mapping: BR.RF CORREIO_ELETRONICOEMAIL_VALUE
mapping source: email (BR.SINRF), mapping: BR.SINRF emailEMAIL_VALUE
mapping source: endereco_eletronico (BR.SINSF), enderecoEletronico (BR.SINSF), mapping: BR.SINSF endereco_eletronico, enderecoEletronicoEMAIL_VALUE
mapping source: EMAIL (BVD), mapping: BVD EMAIL VALUEEMAIL_VALUE
mapping source: EmailOrWebsite (BVD), mapping: BVD EmailOrWebsiteEMAIL_VALUE, WEBSITE_VALUE
mapping source: value (CDQ.INTEL), mapping: CDQ.INTEL valueEMAIL_VALUE
mapping source: courriel (CHORUS.PRO), mapping: CHORUS.PRO entity_adressePostale_courrielEMAIL_VALUE
mapping source: kontaktoplysning (DK.CR), mapping: DK.CR elektroniskPost_kontaktoplysningEMAIL_VALUE
mapping source: kontaktoplysning (DK.CR), mapping: DK.CR obligatoriskEmail_kontaktoplysningEMAIL_VALUE
mapping source: email (IN.CA), mapping: IN.CA emailEMAIL_VALUE
mapping source: email (MX.SBI), mapping: MX.SBI emailEMAIL_VALUE
mapping source: EmailAddress (SAP.ODM), mapping: SAP.ODM addressEMAIL_VALUE
mapping source: Communication Details Email Address (SPOR.OMS), mapping: SPOR.OMS CommunicationDetailsEmailAddressEMAIL_VALUE
mapping source: communicationDetailsEmailAddress (SPOR.OMS), mapping: SPOR.OMS communicationDetailsEmailAddressEMAIL_VALUE
mapping source: charity_contact_email (UK.CC), mapping: UK.CC charity_contact_emailEMAIL_VALUE
mapping source: Business_Email_Address (US-CT.BER), mapping: US-CT.BER Business_Email_AddressEMAIL_VALUE