The header of an asset provides a summary view of its most relevant information and allows the user to quickly contextualize the object within the governance model. This area is present in all detail views and its content may vary slightly depending on the type of asset being consulted.
In general, the header displays:
-
Asset name.
-
Object subtype, represented by its icon. To check the exact subtype, the user must hover over or click the icon.
-
Governance status of the asset (e.g., draft, pending validation, approved, rejected, deprecated, expired, etc.).
-
Organizational unit associated, when applicable.
-
Relevant dates, such as creation and approval, whenever available for that type of object.
-
Version, only available in entities that support native versioning in Anjana Data Platform (datasets, dataset fields, processes, instances, solutions, and DSAs).
.png?cb=4c3ae25bd2593098c57b4e142236a95f)
|
No. |
Metadata |
Description |
|---|---|---|
|
1 |
Version |
Indicates the version of the asset being viewed. It allows the user to identify whether they are working on the current version or consulting a specific version from the history (when the object supports versioning). |
|
2 |
Organizational unit |
Shows the organizational unit (OU) to which the asset belongs. This data contextualizes the responsibility and governance scope of the object within the organization. |
|
3 |
Infrastructure |
First level of the technical location “triplet”. Internally named |
|
4 |
Technology |
Second level of the triplet. Internally |
|
5 |
Zone |
Third level of the triplet. Internally |
|
6 |
Location or path |
Internally named |
|
7 |
Creation date |
Reflects when the asset was created in Anjana Data Platform. It is a key reference for traceability and auditing. |
|
8 |
Modification date |
Indicates the last update date of the asset. It allows users to know whether the object has been recently modified and is useful for change tracking. |
|
9 |
Status |
An indicator of the governance status of the object (e.g., Draft, Pending validation, Approved, Deprecated, Expired, etc.). It determines which actions are available and reflects its situation in the governance flow. |
|
10 |
Asset version indicators |
They inform about the existence of other versions of the asset, for example, the existence of a more recent draft version. |
Additional information by asset type
In addition to the common elements, the header may include specific information:
Datasets
In dataset-type assets, the header includes the technical information defined at creation, such as:
-
Infrastructure: First level of the triplet, internally named infrastructure.
-
Technology: Second level of the triplet, internally named technology.
-
Zone: Third level of the triplet, internally named zone.
-
Location or path: Internally named path
These attributes allow users to quickly identify where the physical asset resides and in what environment it operates.
Dataset fields
In dataset field-type assets, the header includes the technical information defined at creation, such as:
-
Infrastructure: First level of the triplet, internally named infrastructure.
-
Technology: Second level of the triplet, internally named technology.
-
Zone: Third level of the triplet, internally named zone.
-
Location or path: Internally named path
These attributes allow users to quickly identify where the physical asset resides and in what environment it operates.
The header also includes information about the dataset it belongs to in the form of an icon and a navigable link.
Processes
In process-type assets, the header includes the technical information defined at creation, such as:
-
Infrastructure: First level of the triplet, internally named infrastructure.
-
Technology: Second level of the triplet, internally named technology.
-
Zone: Third level of the triplet, internally named zone.
-
Location or path: Internally named path
These attributes allow users to quickly identify where the physical asset resides and in what environment it operates.
Instances
In instance-type assets, the header includes information about:
-
The solution it belongs to, i.e., the technical contract covering the data processing by the process instance
-
The process that the process instance belongs to
This information is displayed as a pointer to those entities, with an icon and a link to navigate to the object.
Solution
In solution-type assets, no additional information beyond the rest of the native entities is included.
DSA
In DSA-type assets, no additional information beyond the rest of the native entities is included.
Non-native entities
The headers of non-native entities do not include additional information.
Relationships
The headers of relationships display the organizational unit of the source entity and target entity respectively, as well as links to the source and target entities of the relationship. This information is displayed as a pointer to those entities, with an icon and a link to navigate to the object.
