Label
A label is a logical object that provides a different means of representing an attribute. In other words, a label applies additional descriptors to the related attribute.
Each label can be assigned to only one attribute. An attribute can have one or multiple labels. For example, the Department
attribute can be represented by different labels, such as Full name
, Shortened name
, Number
. When you choose a label for the Department
attribute, you define how you want the attribute values (the company departments) to be displayed:
- Using the
Full name
label:Human Resources
,Research and Development
,Quality Assurance
- Using the
Shortened name
label:HR
,RD
,QA
- Using the
Number
label:1
forHuman Resources
,2
forResearch and Development
, and3
forQuality Assurance
The following table shows the relationship of attributes, attribute labels, and attribute values:
Attribute | Attribute Label | Attribute Values |
---|---|---|
Department | Full name | Human Resources Research and Development Quality Assurance |
Short name | HR RD QA | |
ID | 1 2 3 |
When you create an attribute in your logical data model (LDM), it is added with a single label, which has the same name as the attribute itself. This label becomes the primary label for the attribute. Every attribute has at least one label, and you can add more labels to it.
Attribute Label Cardinality
When configuring labels within your logical data model (LDM), ensure a primary attribute label and its secondary labels maintain an N:1 relationship. This means each primary label value should correspond to exactly one secondary label value, although the reverse—multiple primary labels sharing the same secondary label value—is permissible. For instance, each person_id
(primary) should be linked to a unique person_name
(secondary), but the same person_name
can be associated with different person_id
s.
When the attribute with multiple labels is used in an Visualization, the attribute values belonging to the primary label will be populated into the visualization.
Within an LDM, a label belongs to an attribute in a dataset and must define a source column that corresponds to a column from the database.