Datasets

PK Fields

The fields that make a dataset unique in Anjana are: 

• name

• infrastructure

• technology

• zone

• location

NOTES:

• The “name” attribute must not contain the character ‘:’ to avoid interfering with the internal logic of the application.

• These fields are not editable (except the name). If the object needs a different PK, the object must be cloned with different values in its PK, but the original will continue to exist.

Attributes 

When a user accesses the detail of a dataset, 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.

NOTES:

• The attribute corresponding to the physical path of the dataset data in Anjana Data must not contain ‘:’ to avoid interfering with the internal logic of the application. The internal name of this attribute in Anjana is “path”. 

If Anjana Data is connected to a technology whose plugin allows the creation of structures in the system, when a governed dataset is approved, it will use the “path” attribute to determine where the object will be created.

Structure

If the dataset is structured, the Structure screen displays the dataset schema as well as the metadata corresponding to each of its fields.

From this screen, the user can add or remove dataset_fields from the dataset, copy the ARI, or access the view of each one. Additionally, it displays some attributes of each dataset_field, and the screen can be scrolled horizontally since the first column (with the name) remains fixed.

Clicking “Add a new dataset field” opens a window where the fields that identify each of the dataset fields are entered. 

If the dataset is in draft status, the entered values can be reused for consecutive creations by clicking “Keep values when creating the object”. If the dataset status is approved, adding a new field generates a new draft and, from that draft screen, new fields can be created at the same time.

This screen also presents filters to search for fields in datasets by name, physical name and position, and to easily check fields with valid or invalid attributes.

Relationships

In the Relationships screen, the user can view the existing relationships between the dataset and other entities in the Anjana repository. This allows the user to find out, for example, in which dataset a given business term is stored, or which datasets are involved in the creation of a particular report.

Relationships can be:

• Direct: Relationships in which the dataset is the source or target, including relationships where the dataset is part of an instance through input or output dataset fields

• Indirect: Relationships of the dataset's dataset_fields with other entities

• Composition: Native relationships created by being part of another object, i.e., when it is included in a DSA through the contained entities field

Relationships can also be filtered by the name and subtype of the related entity, the relationship type (source or target), and the name and subtype of the relationship.

Lineage

In this screen, the user can view the lineage of the dataset, and can expand the dataset to see, for example, the organizational unit it belongs to, the DSAs it is contained in, the instances for which it is an input or output, the users who have access to its data through adherences…

The objects displayed in this graph depend on the chosen lineage layer and their relationship with the dataset (whether it is a source, target 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

In the Stakeholders screen, the user can view all users who are stakeholders of the dataset.

Users appear typed as:

• Adherents: user who has adherence to a DSA that contains the dataset

• Primary: creator or owner user of the dataset

• Secondary: user assigned to a template attribute (if the object has any attribute of the nominal User type)

Stakeholders can also be filtered by stakeholder type, role or name.

Audit

In the Audit screen, the user can view all Anjana audit records, both internal ones generated by users through application usage (such as creation, workflow validations, modifications, usage in DSA creation…) and external ones or dynamic lineage showing what happens in the systems with respect to the displayed dataset (such as accesses to dataset data by command, queries that read or write to the dataset, processes that use the dataset data…)

It is possible to filter by whether it is a search action or not, what, who and when an action was performed on that dataset.

The source allows distinguishing between the different sources that generate audit records: “anjana” for internal audit and the system name for external audit.

Versions

In the Versions screen, the user can view the list of versions of the dataset, from which the detail of all of them can be accessed.

In this window, the user can:

• Navigate to each of the versions of the dataset

• Download the snapshot of each version of the dataset

• If a version is pending approval, navigate to its validation workflow

Sample Data

In the Sample Data screen, the user can preview a random data sample as long as the dataset was registered as governed and the option to allow this feature was selected, and the dataset is approved. If so, a limited number of dataset records (configurable) will appear on this screen. Otherwise, this screen is not available. 

Fields whose metadata indicates they contain confidential (or PI) information will appear obfuscated in the data sample so that no user can see the data in plain or raw form.