This page describes the Dataset_field object (a dataset field) in Anjana Data Platform. It covers the attributes that make up its primary key (PK) (which form its ARI, the identifier used to uniquely represent each object in Anjana) and the tabs that display the object's information in its detail view.
Primary Key (PK) and ARI
Each object in Anjana Data Platform is uniquely identified by its ARI (Anjana Resource Identifier), which is built from the attributes that make up its primary key (PK). In the case of dataset_field, these attributes (with their internal naming in parentheses) are:
-
name
-
dataset infrastructure
-
dataset technology
-
dataset zone
-
dataset plugin location or logical path (
path)
The ARI also includes the name of the dataset that the field belongs to and the dataset's organizational unit (organizationalUnit). For example, for a dataset_field with ID 58:
ANJA:OBJECT:ENTITY:DATASET_FIELD:58:Id_cliente:Europe/SPA/Finance:Clientes:AWS:awsS3:devQA:/data/clientes
where the structure is:
ANJA:OBJECT:ENTITY:DATASET_FIELD:<idDatasetField>:<dataset field name>:<organizational unit of the dataset>:<name of the dataset it belongs to>:<infrastructure of the dataset>:<technology of the dataset>:<zone of the dataset>:<path of the dataset>
NOTES:
-
The name attribute (
name) must not contain the ':' character, since it is the separator used between the components of the ARI and would interfere with the application's internal logic. -
To ensure that the fields making up the ARI cannot be edited, it is the administrator's responsibility to configure those attributes in the templates with "not editable" validations. Any manual change to these values will break the object's referential integrity.
-
The values of infrastructure, technology, zone and organizationalUnit that appear in the ARI do not necessarily match what the user sees in the template. If multi-language support has been configured, the translation key is what forms part of the ARI, while the user sees in the template the translated value of that key for the language selected in their profile.
Detail Tabs
The detail view of a dataset_field is organized into several tabs, each showing a type of information about the object. When accessing the detail view, the screen shown by default is Attributes.
The availability of the "Relationships", "Lineage" and "Stakeholders" tabs depends on the permissions assigned to the user's role. When access to a tab is disabled, it is displayed in gray and the user cannot navigate to it. If a user believes they should have access and do not, they should contact the Anjana Data Platform administrator.
Attributes
When a user accesses the detail view of a dataset field, the screen shown is Attributes, where the user can access the different functional, technical, operational, etc. attributes 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 that particular dataset_field.
Relationships
On 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, for example, which metric is stored in a given field, or which fields are involved in creating a particular report.
Relationships can be:
-
Direct: Relationships in which the dataset_field is the source or target
-
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 target), and the name and subtype of the relationship.
Lineage
On this screen, the user can view the lineage of the dataset field, and can expand the dataset field to see, for example, the dataset that contains it, users adhering to DSAs that include its dataset, relationships with the entities it has, and so on.
The objects shown in this graph depend on the chosen lineage layer and its relationship with the dataset_field (whether it is a source, a target, and the type of relationship). You can filter which entity types, relationships and statuses you want to display.
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 are typed as:
-
Adherents: user who has adherence to its dataset
-
Primary: user who created or owns the dataset_field
-
Secondary: user assigned in a template attribute (if the object has an attribute of type Named User)
Stakeholders can also be filtered by stakeholder type, role or name.
