From CDQ
Data source/LEI/data model/RelationshipRecord/0/Registration /
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
| 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.
|
Registration
|
| Description Informal and comprehensive human-readable definition of a concept.
|
n/a
|
| 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 LEI
|
| 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.
|
Registration0
|
| Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model.
|
Data source/LEI/data model/RelationshipRecord
|
| 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.
|
relations[0].relationship.registration
|
| 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/>
|
NODE
|
| Mapping
|
|
Sub concepts
| Concept | Description |
|---|
| InitialRegistrationDate (LEI) | A date and time, including the timezone, based on ISO 8601. |
| LastUpdateDate (LEI) | A date and time, including the timezone, based on ISO 8601. |
| ManagingLOU (LEI) | |
| NextRenewalDate (LEI) | |
| RegistrationStatus (LEI) | A value of type RegistrationStatusEnum in a file conforming to this standard SHALL be one of the following code strings:
PENDING_VALIDATION - A relationship data report that has been submitted and which is being processed and validated, prior to publication
PUBLISHED - A relationship record that has been validated and published, and which identifies a relationship that was reported by an entity that was an operating legal entity as of the last update
DUPLICATE - A relationship record that has been determined to be a duplicate of the same relationship as another relationship record; the DUPLICATE status is assigned to the non-surviving record
LAPSED - A relationship record that has not been renewed by the NextRenewalDate
RETIRED - The relationship is considered to have ended, but the relationship report is kept in publication for historical audit trail purposes
ANNULLED - A relationship record that was marked as erroneous or invalid after it was issued
TRANSFERRED - A relationship record that has been transferred to a different LOU as the managing LOU
PENDING_TRANSFER - A relationship record that has been requested to be transferred to another LOU. The request is being processed at the sending LOU
PENDING_ARCHIVAL - A relationship record is about to be transferred to a different LOU, after which its registration status will revert to a non-pending status |
| ValidationDocuments (LEI) | |
| ValidationSources (LEI) | |