Governed assets are the core elements of the Anjana Data Platform Data Portal. They represent both logical entities (for example, business terms, metrics, or reports) and physical assets (datasets, fields, processes, ML models, etc.) and their relationships. Each asset has a detail view that brings together all the information needed to interpret it correctly, operate it, and keep it under governance control.
This section of the User Guide explains how to read and use this detail view to understand the asset's context, structure, traceability, and status within the organization's governance model.
The functional content and the internal configuration logic that determines which attributes exist, how they relate to each other, or which rules apply to each asset type is documented in the Functional Configuration section of the official documentation.
.png?cb=e8400dbc1d2f13f24d60f308994962b0)
|
No. |
Title |
Description |
|---|---|---|
|
1 |
Access to Home |
The Anjana Data Platform logo is a link to the home page |
|
2 |
Asset header |
Main area for identifying the asset. It includes the object name, the version, the tags of its primary key known as ARI (organizational unit, infrastructure, technology, zone...), and other relevant information (creation date, modification date...). It allows you to understand at a glance which asset you are viewing and its context. |
|
3 |
Asset tabs |
Set of tabs that organize the asset's information by functional area: Attributes, Structure, Relationships, Lineage, Stakeholders, Audit, Versions, and Sample Data. Each tab groups specific metadata and operations. |
|
4 |
Asset status |
Indicator of the governance status the object is in (for example: Draft, Pending validation, Approved, Deprecated, Expired, etc.). It determines which actions are available and reflects its situation within the governance workflow. |
|
5 |
Asset version indicators |
Version indicators inform about the existence of other versions of the asset, for example, the existence of a more recent draft version. |
|
6 |
Save changes |
Button to save changes made to the Attributes template or the Structure tab (the latter only available for Datasets) associated with the editing and governance cycle. To save changes, the metadata validations for the templates must be passed successfully. Its availability depends on the status of the object and the user's role. |
|
7 |
Send for validation |
Button to submit for validation changes made to the Attributes template or the Structure tab (the latter only available for Datasets) associated with the editing and governance cycle. Before submitting, the user must make sure the changes have been saved. Its availability depends on the status of the object, the existence of changes, and the user's role. |
|
8 |
Asset actions menu ("...") |
Context menu with additional operational actions (e.g., Add to workspace, clone, copy ARI, download metadata/snapshot, create relationship, etc.). The visible options vary depending on the asset type, status, and the user's role permissions. |