PK Fields
The fields that make a dataset_field unique in Anjana are:
-
name
-
infrastructure (of the dataset it belongs to)
-
technology (of the dataset it belongs to)
-
zone (of the dataset it belongs to)
-
location (of the dataset it belongs to)
NOTES:
-
The “name” attribute must not contain the character ‘:’ to avoid interfering with the internal logic of the application.
Attributes
When a user accesses the detail of a dataset field, the screen displayed is the Attributes screen, where the user can access the different functional, technical, operational, etc. attributes that have been defined in the template, within the corresponding menus and sections, as well as the specific attributes that are not part of the template but have been included in the particular dataset_field.
Relationships
In the relationships screen, the user can view the existing relationships between the dataset field and other entities in the Anjana repository. This way, the user can find out which metric is stored in a field, or which fields are involved in the creation of a specific report.
Relationships can be:
-
Direct: Relationships in which the dataset_field is the source or destination
-
Indirect: Relationships of its dataset with other entities
Relationships can also be filtered by the name and subtype of the related entity, the type of relationship (source or destination), and the name and subtype of the relationship.
Lineage
In this screen, the user can view the lineage of the dataset field, being able to expand the dataset field to see, for example, the dataset that contains it, users subscribed to DSAs that include its dataset, relationships with the entities it has…
The objects shown in this graph depend on the chosen lineage layer and their relationship with the dataset_field (whether it is source, destination, and what type of relationship). It is possible to filter which entity types, relationships, and statuses are to be displayed.
More detail about the graph is included in the Lineage section of this Guide.
Stakeholders
Within the Stakeholders screen, the user can view the users who are stakeholders of the Dataset Field.
Users appear typed as:
-
Subscribed: user who has a subscription to its dataset
-
Primary: creator or owner user of the dataset_field
-
Secondary: user assigned to some attribute of the template (in case the object has any nominal User-type attribute)
Stakeholders can also be filtered by stakeholder type, role, or name.
