A manual data element is the business representation of data that may not be available in the catalog but is essential to capture for governance purposes in your organization.
If you are a business user, you can manually create a data element within a data set. A data set can either have technical data elements or manual data elements or a combination of both. Although a manual data element is a type of business asset, it exists in a business data set and not as a standalone business asset. You can associate a manual data element with one business data set only.
Overview tab
On the Overview page, you can view basic information about the manual data element.
The following table describes the properties of the Overview page:
Field
Description
Name
Name of the manual data element.
Data Set
Parent data set to which the manual data element belongs.
Description
Description of the manual data element. The size of the field should not exceed 1 MB.
Reference ID
Unique identifier for the manual data element.
Glossaries
Glossary assets that are related to the manual data element.
Data Element Classifications
Data element classifications that you want to associate with the manual data element.
Stakeholders
Users or user groups responsible for the manual data element or interested in the manual data element.
Asset Groups
One or more asset groups assigned to this asset. Asset groups allow users access to a set of assets in the organization.
You can assign asset groups to an asset if your organization administrator has granted you the Manage Access permission on the asset through access policies in Metadata Command Center.
When you open the parent data set, you can search for a specific manual data element, click the Add icon to add a new manual data element to the data set, or click the Delete icon to remove a specific manual data element from the data set. You can also use filters to narrow the list of manual data elements.
Lineage tab
View the data lineage of the manual data element. A lineage graphically displays the inflow of data from other systems into the manual data element and the outflow of data from the manual data element to other systems. The lineage tab displays data flow that is automatically generated and lineages that you have manually created. For more information about lineage, see Data lineage in the Working With Assets help.
Relationships tab
On this page, you can switch between grid view or graph view to view all the relationships that the manual data element has with other assets. Create relationships with other assets if they can be used together to make business or governance decisions.
The following table describes the fields that appear when you switch to the grid view on the Relationships page:
Field
Description
Name
Name of the related asset.
Type
Type of the related asset.
How It Is Related
Relationship between the related assets and the manual data element asset that you have opened.
Displays the name of the corresponding related assets. Hover the mouse over the arrows of different colors to see if the relationship is direct, indirect, inbound, or outbound.
Hierarchy
Hierarchical path of the asset.
Note: This column is hidden by default. To display the column, right-click on the column header and select Hierarchy.
You can perform the following activities on the Relationships page:
•Click the Filters icon on the top of the page to apply filters to narrow the list of relationships. You can apply filters such as asset type to view related assets of a specific type, direction to view related assets of a particular origin, lifecycle to view assets in a particular stage of the lifecycle, relationship type to view assets that are directly or indirectly connected to the manual data element, or relationship label.
The direction of the asset can be inbound or outbound. The relationship created from the manual data element to the related asset is called an outbound relationship. The relationship created from the related asset to the manual data element is called an inbound relationship.
•Search for a related asset using the Search box.
•Click the Add icon to add a new related asset, or the Delete icon to delete an existing related asset.
Note: You can delete only outbound direct related assets.
Relationship example
The following image shows a sample asset and the different types of relationships with other assets:
In the image, the business term 'Delivery Cost' is the open asset. The Relationships tab shows the grid view of all the assets related to 'Delivery Cost'.
1The highlighted policy asset 'Gov Policy 01' is related to the open asset through an inbound relationship, which is indicated by the orange arrow pointing to the left direction. This indicates that the relationship between the business term 'Delivery Cost' and the policy 'Gov Policy 01' originated in the policy asset 'Gov Policy 01'. The relationship type 'is Regulating' indicates that the policy asset is regulating the business term.
2The highlighted system asset 'Customer Call Analysis Reports' is related to the open asset through an outbound relationship, which is indicated by the blue arrow pointing to the right direction. This indicates that the relationship between the business term 'Delivery Cost' and the system 'Customer Call Analysis Reports' originated in the business term 'Delivery Cost'. The relationship type 'is a Strategic Source for' indicates that the business term is the preferred or recommended source of data for the system asset.
Stakeholders tab
View users that have been designated as stakeholders for the manual data element. Stakeholders are authorized users who are responsible for the manual data element, and can approve or reject change requests for the manual data element. Stakeholders are automatically inherited from the parent data set. You cannot add stakeholders for a manual data element.
The following table describes the properties of the Stakeholders page:
Field
Description
Name
Name of the user or user group.
Role
Role of the user or user group in the organization.
Email
Email address of the user.
Note: This property does not appear for user groups.
User Origin
The origin of the users. For example, when a user logs in using SSO, the value for this field is displayed as SAML.
History tab
View changes that users have made to the manual data element. The History tab provides an audit log that you can use for compliance requirements.
The following table describes the properties of the History tab:
Field
Description
Date
Displays the created and last updated dates of the asset.
Event Type
Displays the type of the event that is performed on the asset:
- Asset. Displays changes in the name, description, certification, or the reference ID of the asset.
- Relationship. Displays additions, deletions, and the updates of the relationships between the assets.
- Stakeholder. Displays additions and deletions of stakeholders to the asset.
Action
Displays the following actions that are performed on the asset:
- Create. Displayed if the asset is created.
- Updated. Displayed if the asset is updated.
- Deleted. Displayed if the asset is deleted.
Current Attributes
Displays the recently changed attributes of the asset.
Previous Attributes
Displays the earlier attributes of the asset.
Changed By
Displays the user who has performed any action on the asset.
Asset Name
Displays the name of the asset.
Asset Path
Displays the origin path of the asset.
Asset Type
Displays the type of the asset.
From Asset Type
Displays the source asset type for which the change is applicable. This is applicable when the event type is Relationship.
To Asset Type
Displays the target asset type for which the change is applicable. This is applicable when the event type is Relationship.
