Governed assets are the central elements of the Anjana Data Platform Data Portal. They represent both logical entities (e.g., business terms, metrics, or reports) and physical assets (datasets, fields, processes, ML models, etc.) and their relationships. Each asset has a detail view that concentrates all the information needed to correctly interpret it, operate on 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, its structure, its traceability, and its status within the organization's governance model.
The functional content and internal parameterization logic that determines which attributes exist, how they are related, or which rules apply to each type of asset is documented in the Functional Configuration section of the official documentation.
.png?cb=4c3ae25bd2593098c57b4e142236a95f)
|
No. |
Title |
Description |
|---|---|---|
|
1 |
Access to the Search Portal |
The Anjana Data Platform logo is a link to the Search Portal. |
|
2 |
Asset header |
Main area for asset identification. Includes the object name, the version, the labels of its primary key known as ARI (organizational unit, infrastructure, technology, zone...) and other relevant information (creation date, modification date...). Allows understanding at a glance which asset is being consulted and what its context is. |
|
3 |
Asset tabs |
Set of tabs that organize the asset's information by functional areas: Attributes, Structure, Relationships, Lineage, Participants, Audit, Versions, and Sample Data. Each tab groups specific metadata and operations. |
|
4 |
Asset status |
Indicator of the governance status in which the object is located (e.g., Draft, Pending validation, Approved, Deprecated, Expired, etc.). Determines which actions are available and reflects its position in 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 validations on the template metadata must be successfully passed. Its availability depends on the object's status and the user's role. |
|
7 |
Send for validation |
Button to send for validation the changes made to the Attributes template or the Structure tab (the latter only available for Datasets) associated with the editing and governance cycle. Before sending, the user must ensure they have saved the changes. Its availability depends on the object's status, the existence of changes, and the user's role. |
|
8 |
Asset actions menu ("...") |
Contextual menu with additional operational actions (e.g., Add to workspace, clone, copy ARI, download metadata/snapshot, create relationship, etc.). The visible options vary according to asset type, status, and user role permissions. |