9 Dots Action Menu
This article is intended to teach users to navigate and effectively use Nine Dots Action’s functionalities, including adding or editing Tags and Terms, adding data objects to a project, adding data objects to My Watchlist, or raising service requests on data objects.
Introduction to Data Catalog Object Nine Dots Options
Performing Action Items on Multiple Data Objects
Performing Action items at a single data object or summary page level
Perform Action Items on Multiple Data Objects
Add / Remove to My Watchlist (S, T, TC, R)
Purpose: When users add a data object to their watchlist, they gain access to real-time notifications that keep them informed about any changes or updates associated with that specific object. It ensures that users stay up-to-date with the latest changes or updates happening both within the catalog and across remote data sources. Users can make well-informed decisions and effectively leverage the data to meet their business needs by receiving timely notifications.
Metadata changes: If any changes are made to the business descriptions, tags, or terms associated with the data object within the OvalEdge instance, these changes will be displayed. This ensures that users stay informed about any updates or modifications to the metadata, helping them stay updated with the latest information.
Remote metadata changes: In addition to changes made within the OvalEdge instance, users can also receive notifications when the data object at the remote source is updated. This feature enables users to monitor external changes, ensuring they have the most accurate and current metadata information.
Significant data changes: This feature provides users with the ability to receive notifications regarding significant data changes in the data object located at the remote source. These changes can include adding or deleting new rows within the data object.
Users can define a threshold value, and notifications can be triggered if the change in row counts exceeds this threshold. For example, if the threshold is set to 50% and the row count of the data object increases by more than 50%, a notification will be generated.
How to: To add multiple data objects in your watchlist, select the desired data objects and choose either the "Add to My Watchlist" or "Remove from My Watchlist" option from the menu (nine dots). This allows users to add or remove the selected data objects from the "My Watchlist" section in the "My Resources" area.
If the Remove from My Watchlist option is selected for a watchlisted data object, it will be removed from the My Resources > My Watchlist page, and all alert notifications will be disabled for that data object.
Add/Remove Tags
Purpose: Tags are like labels or keywords that group data objects together to make them easier to search for and discover. They can be very useful for managing and organizing data objects when dealing with large volumes of information. A single data object can have multiple associated tags, and a tag can be applied to multiple data objects. This allows for flexible grouping and organization of data objects based on various criteria.
How to Bulk Update Tags on Multiple Data Objects
In the left panel menu, select Data Catalog.
Select Data Object Type: From the top menu in the Data Catalog, select the appropriate data object type tab.
Choose Multiple Data Objects: In the tabular plugin, select the checkboxes corresponding to the data objects where users want to update tags.
Access Tag Options: Click on the Nine dots (menu) and select "Add Tags" from the available options. An Add Tag pop-up window appears, displaying the available tags in the left panel.
To add Tags: Click on the "+" icon next to the desired tags to add them to the data objects.
To Remove Tags: After completing steps 1 to 3, choose the 'Remove tags' option from the Nine dots menu. A "Remove Tags" pop-up window will appear, showing all the tags assigned to the selected data objects. Click the "x" icon next to each tag and the selected tags will be removed from the data objects.
To verify the updates, navigate back to the Data Catalog - Tabular Plugin and review the updated tags listed under the "Tags" column for each data object.
Add/Remove Terms
Purpose: Terms are unique and standardized definitions for key organizational processes and concepts. They are assigned to data objects to apply term properties, allowing for greater control and governance over the data. By associating a term with a data object, users can accomplish various tasks such as applying classifications, data masking, user restrictions, assigning governance stakeholders, and copying titles and descriptions to associated data objects.
Each data object can have only one primary term associated with it, but multiple auxiliary terms can be applied. However, it's important to note that terms cannot be applied to objects with DAG tags and vice versa.
For Example, In a financial organization, the term "Confidential Customer Data" has several properties, including masking policies, copying the term title to the data catalog, and copying the governance stakeholders (owners, stewards, and custodians). When this term is applied to a data object, it associates the term properties, overrides existing governance stakeholders with the term's governance stakeholders, updates the title with the term title, and applies the specified masking policy to the data object.
How to Bulk Update a Term on Multiple Data Objects?
In the left panel menu, select Data Catalog.
Select Data Object Type: Choose the appropriate data object type tab from the top menu in the Data Catalog.
Choose Multiple Data Objects: In the tabular plugin, select the checkboxes corresponding to the data objects for which users want to update tags.
Access Term Options: Click on the Nine dots (menu) and select "Add Terms" from the available options. An Add Term pop-up window appears, displaying the available tags in the left panel.
To add a Term: Click on the "+" icon next to the desired tags to add them to the data objects.
To Remove Terms: After completing steps 1 to 3, choose the 'Remove Terms' option from the Nine dots menu. A "Remove Terms" pop-up window will appear, showing all the terms assigned to the selected data objects. Click the "x" icon next to each term to remove the selected terms from the data objects.
To verify the updates, navigate to the Data Catalog - Tabular Plugin and review the updated tags listed under each data object's "Terms" column.
Add/ Remove Data Objects to Default Project
Purpose: Data objects are added to any project set as the default project. For example, a team is working on a project called "Customer Feedback Analysis." By setting this project as the default, data objects (referred to as tasks in projects) related to customer feedback can be easily added to the project. This ensures that all team members can quickly access the relevant data objects and collaborate and effectively work around them.
Set a default project: It is first important to designate a preferred project as the default one. Once a default project is set, any data objects added to the system will automatically be assigned to the default project.
Add Data Objects to a Default Project:
Data Catalog > List View—The image below demonstrates the 'Add to Project' icon in a data catalog's list view. Users can simply click the icon to include objects in the chosen default project.
Data Catalog > List View—The image below demonstrates the 'Add to Project' icon in the List View of a data catalog, which allows users to add multiple data objects to a default project in bulk. Users can select the multiple checkboxes for the corresponding data objects and click on the Nine dots icon to select Add to Project.
Data Catalog > Data Object Summary Page - The image below demonstrates the 'Add to Project' icon in the detailed view of a data object. Users can simply click the icon to include objects in the chosen default project.
Add Data Objects to the Access Cart:
When the Access Cart is set as the default project, it serves as a centralized access request management system. Users can add multiple data objects to the cart and raise access requests in bulk. This simplifies the process of managing and tracking access permissions for the selected data objects, improving efficiency in granting appropriate access to users on the data objects.
Set default project as Access Cart: It is important to first designate a preferred project as the Access Cart. When “Access Cart” is chosen as the default project, the selected data objects are automatically added to the access cart when the Add to Access Cart button is clicked.
Update Governance Roles
The Update Governance Roles feature allows users to add and update governance roles, including Owner, Steward, Custodian, and additional custom Governance Roles (if configured). Users can select members from a dropdown list to assign these roles. This feature ensures that the data object has designated individuals responsible for governing it and can serve as points of contact for any queries related to the data object. The following options are available at the bottom of the window:
Don't Cascade: If any of the new governance roles are present at a table or file level, they will not be transferred to the associated columns.
Cascade to Hierarchy: The selected governance stakeholders will be transferred to the columns, if any, in the table's hierarchy.
Apply Certification Type
Apply Certification is an important action item that can only be performed by users with meta-write(Author) privileges. It provides assurance regarding the quality and trustworthiness of a data object for decision-making purposes. Using these certification status indicators, users can quickly identify and trust high-quality data assets while being aware of any limitations or issues associated with uncertified or cautionary data objects.
Certified: The Certified icon signifies that a data object meets specific standards and can be relied upon for decision-making. For example, a sales report that has undergone rigorous data validation and quality checks may be certified.
Caution: The Caution icon indicates that a data object has certain limitations or issues that users should be aware of before basing decisions on it. For instance, a Customer Details Table may have incomplete or outdated records, which might impact the accuracy of analyses performed on it.
Violation: The Violation icon suggests that a data object does not meet certain standards or requirements, rendering it unreliable or unsuitable for decision-making. For instance, a financial report with discrepancies or irregularities may be marked with a violation status.
Inactive: The Inactive status signifies that a data object is not currently in use or has been archived. It may no longer be relevant for decision-making or ongoing operations. An example could be a historical dataset that is no longer actively updated or used for analysis.
None: The None status indicates that a data object has not undergone certification. Its reliability and accuracy cannot be assured, and users should exercise caution when utilizing it for decision-making. An example could be a newly created dataset that hasn't been reviewed or validated yet.
Add Data Objects to Impact Analysis (T, TC, F, FC, R, RC, API, APIA)
The "Impact Analysis" feature allows users to preview the data objects that will be affected if any changes or modifications are made to a specific data object. It helps users understand the potential impact of their actions on the overall data ecosystem if they were to change the value or any row of the selected data object.
Let's consider a scenario where an organization plans to change a critical File, ‘Financial Performance,’ within its data infrastructure. This file is extensively used by various downstream systems and processes. Before implementing the changes, the organization wants to assess the potential impact on other interconnected data objects (files, tables, or reports).
Once a data object is added to a predefined impact analysis and once it is executed, OvalEdge performs a comprehensive analysis of the data lineage, taking into account the complex relationships and dependencies. The impacted data object results are presented in a clear and concise tabular format, displaying the count of impacted objects. For example, if the Impacted data object count displays 50, the analysis might reveal that the changes to the critical data object will impact 50 other data objects across multiple levels of lineage. The tabular display allows users to understand the scope and magnitude of the potential impact quickly.
How to add:
Click the Add to Impact Analysis option to see the pre-defined Impact Analysis.
Select the appropriate Impact Analysis from the list of predefined Impact Analyses. The data object gets added to the corresponding Impact Analysis.
Go to Advanced Tools (left menu) > Impact Analysis > select the preferred Impact Analysis. Execute the Impact Analysis using the Nine Dots icon.
Impacted Objects: Review the results presented in a tabular format, which will display the count of impacted objects and provide insights into the potential impact on the interconnected data ecosystem.
Profile
Who can perform: Only the Integration Admin can perform this operation.
Profiling is an analysis performed on the remote source to gather statistical information on data objects. It retrieves data objects' details, including row count, top values, null density, and density. However, for data objects that do not have profiling details, the nine dots action menu can be used to profile the details of a single data object individually. This approach helps reduce the workload on remote sources.
How to: Upon clicking the 'Profile' option, a background job is triggered to initiate profiling. Once the job successfully completes the profiling process, the profiling statistics are updated on the summary page of the data object.
If the profiling is performed on a schema, the tables and columns within the schema are updated with the corresponding profiling details. Similarly, when profiling is performed on a specific table, the profiling information for the table's columns is updated within the table itself.
Profile Unprofiled
Who can Perform: Only the Integration Admin can perform this operation.
The "Profile Unprofiled" option allows for schema-level profiling of data objects that have not been profiled yet. This feature enables the profiling of data objects within a schema that does not have existing profiling information. Users can initiate the profiling process for these unprofiled data objects to gain valuable statistical insights.
Add / Remove to My Watchlist
Purpose: When users add a data object to their watchlist, they gain access to real-time notifications that keep them informed about any changes or updates associated with that specific object. It ensures that users stay up-to-date with the latest changes or updates happening both within the catalog and across remote data sources. By receiving timely notifications, users can make well-informed decisions, and effectively leverage the data to meet their business needs.
Metadata changes: If changes are made to the business descriptions, tags, or terms associated with the data object, these changes will be displayed within the OvalEdge instance. This ensures that users are informed about any updates or modifications to the metadata, helping them stay updated with the latest information.
Remote metadata changes: In addition to changes made within the OvalEdge instance, users can also receive notifications when the data object at the remote source is updated. This feature enables users to monitor external changes, ensuring they have the most accurate and current metadata information.
Significant data changes: This feature allows users to receive notifications regarding significant data changes in the data object located at the remote source. These changes can include the addition or deletion of new rows within the data object.
Users can define a threshold value, and notifications can be triggered if the change in row counts exceeds this threshold. For example, if the threshold is set to 50% and the row count of the data object increases by more than 50%, a notification will be generated.
How to: To add multiple data objects in your watchlist, select the desired data objects and choose either the "Add to My Watchlist" or "Remove from My Watchlist" option from the menu (nine dots). This allows users to add or remove the selected data objects from the "My Watchlist" section in the "My Resources" area.
If the Remove from My Watchlist option is selected for a watchlisted data object, it will be removed from the My Resources > My Watchlist page, and all alert notifications will be disabled for that data object.
Download Descriptions
To download Business and Technical Descriptions of the tables associated with the scheme to your local system in a .xlxs file format.
Governance Roles
The Update Governance Roles feature allows users to add and update governance roles, including Owner, Steward, Custodian, and additional custom Governance Roles (if configured). Users can select members from a dropdown list to assign these roles. This feature ensures that the data object has designated individuals responsible for governing it and can serve as points of contact for any queries related to the data object.
Don't Cascade: The new set of governance roles will not be transferred to the associated columns if any are present at a Table or File level.
Cascade to Hierarchy: The governance stakeholders selected will be transferred to the columns, if any, present in the table's hierarchy.
Process Upstream / Downstream objects
Process Upstream and Downstream Objects offer the ability to update two important parameters: Adding Metadata to lineage data objects and applying Caution certification to downstream objects. It enables effective data management by automating crucial tasks and ensuring data integrity.
Using Lineage, users can easily apply the Caution certification to downstream data objects associated with the current data object. This ensures that users of the data object are promptly informed about any potential issues or sensitive data present in the related data objects (Tables, Files, or Reports). This certification acts as a warning or alert to raise awareness among users.
Users can also add metadata to the different lineage levels. This metadata can include Business Description, Technical Description, and Tags. They can apply this metadata to either upstream or downstream data objects or both.
How to perform:
Apply/remove caution certification on data objects: Select the radio button corresponding to the desired option.
Copy Metadata using Lineage:
Step 1: Enable the Copy Metadata Using Lineage checkbox to activate additional settings. By default, the Propagate to all levels checkbox is selected.
Step 2: Lineage Levels: Set the lineage level to update metadata to the specified level. If users enter a value of 3 for lineage levels, the metadata updates will propagate up to three levels of lineage.
Step 3: Direction: Choose to update metadata on Upstream or Downstream data objects or both.
Step 4: Content: Select the specific metadata content users wish to update or add, such as Tags, Technical Description, or Business Descriptions. Users can choose all or specific options.
Step 5: Click Submit to apply the changes.
Add Data Objects to Impact Analysis (T, TC, F, FC, R, RC, API, APIA)
The "Impact Analysis" feature allows users to preview the data objects that will be affected if any changes or modifications are made to a specific data object. It helps users understand the potential impact of their actions on the overall data ecosystem if they were to change the value or any row of the selected data object.
Let's consider a scenario where an organization is planning to make changes to a critical File, ‘Financial Performance,’ within its data infrastructure. This file is extensively used by various downstream systems and processes. Before implementing the changes, the organization wants to assess the potential impact on other interconnected data objects (files, tables, or reports).
Once a data object is added to a predefined impact analysis and once it is executed, OvalEdge performs a comprehensive analysis of the data lineage, taking into account the complex relationships and dependencies. The impacted data object results are presented in a clear and concise tabular format, displaying the count of impacted objects. For example, if the Impacted data object count displays 50, the analysis might reveal that the changes to the critical data object will impact 50 other data objects across multiple lineage levels. The tabular display allows users to understand the scope and magnitude of the potential impact quickly.
How to add:
Click the Add to Impact Analysis option to see the pre-defined Impact Analysis.
Select the appropriate Impact Analysis from the list of predefined Impact Analyses. The data object gets added to the corresponding Impact Analysis.
Go to Advanced Tools (left menu) > Impact Analysis > select the preferred Impact Analysis. Execute the Impact Analysis using the Nine Dots icon.
Impacted Objects: Review the results presented in a tabular format, which will display the count of impacted objects and provide insights into the potential impact on the interconnected data ecosystem.
Download
Download Data: To download the data records of the data object to your local system.
Download Descriptions: To download the Business and Technical Descriptions of the data object.
Download Entity Relationships: To download the PK and FK relationship details associated with the table to your local system with Unique match scores and left and Right table counts.
View in Query Sheet
Adding a data object to the query sheet enables users to include specific tables in the query sheet. It provides access to the data within these table columns and allows to perform various operations, filter results, apply aggregations, and extract meaningful insights from the data.
Query sheet provides a user-friendly interface for building and running queries without needing extensive experience with SQL or programming languages. It allows users to select the data tables they want to include in their query and specify any criteria or conditions the data must meet.
It has two modes: Advanced mode and Auto SQL mode.
In advanced mode, users have complete control over the selected table query and can write their own SQL codes to specify exactly what data they want to retrieve.
In auto SQL mode, users who are less familiar with SQL and coding can use the filters and functions to perform union/join operations and retrieve data, but it is optional for them to write their own SQL code to run simple queries.
Send Messages
Send Messages allows users to collaborate with the Owner/Steward/Top Users regarding any concerns. Users can send messages to a maximum of 5 top users,
Enable or Disable Access Management (S, T, TC, F, FC, API, APIA)
The process of allowing/restricting Access Requests from being raised on Data objects can be controlled using Enable/Disable Access Management, which can only be controlled by the Security & Governance Admin of that connector and the corresponding Governance Roles of those Data objects.
Folders - Action Items
Catalog all the Subfolders
The Data Catalog follows a selective approach in cataloging files/folders from remote data sources. While the first-level folder is stored directly in the Data Catalog, all subsequent sub-folders and files are not directly cataloged. Instead, the actual file structure is stored in the File Manager module.
However, users have the option to catalog all sub-folders if needed. This allows users to organize and manage the corresponding sub-folders and files by moving them from the File Manager to the Root Folder at the top level (level '0') of the Data Catalog. Users can specify the level of sub-folders they wish to catalog, ensuring flexibility and control over the organization of files/folders within the catalog. Users can specify the level of subfolders to be cataloged.
Catalog all the Files
The Data Catalog follows a selective approach in cataloging files/folders from remote data sources. While the first-level folder is stored directly in the Data Catalog, all subsequent sub-folders and files are not directly cataloged. Instead, the actual file structure is stored in the File Manager module.
However, users have the option to catalog all sub-folders if needed. This allows users to organize and manage the corresponding sub-folders and files by moving them from the File Manager to the Root Folder at the top level (level '0') of the Data Catalog. Users can specify the level of sub-folders they wish to catalog, ensuring flexibility and control over the organization of files/folders within the catalog. Users can specify the level of subfolders to be cataloged.
Catalog and Profile All Files
The Data Catalog follows a selective approach in cataloging files/folders from remote data sources. While the first-level folder is stored directly in the Data Catalog, all subsequent sub-folders and files are not directly cataloged. Instead, the actual file structure is stored in the File Manager module.
Furthermore, this option also performs profiling on all the files that are cataloged to update file details such as minimum and maximum values, top users, and other relevant statistical information. By profiling the files, users gain valuable insights into their data, making it easier to understand and work with the information stored in them.
Profile Folders assuming the same content
To profile a folder, it must contain at least one file, and the first file within the folder must be in a supported file format. The option to "Profile Folders with the same content" allows profiling all files and folders within the root folder (the top-level folder at level '0'). During the profiling process, the system runs the profiling job on the first file in the selected folder, extracting and applying statistical details to the entire folder. It's important to note that since a folder itself does not hold any information, it is necessary to have a file present in order to obtain profiling details.
Some of the File formats that OvalEdge supports to profile include CSV, JSON, parquet, orc, xlsx, avro, and GZ. Unsupported File formats are class, zip, dll, yaml, sql, html, and jar.
Uncatalog Files / Folder
It removes the file/folder from the Data Catalog > Files. However, if needed, it can easily be re-cataloged to the Data Catalog from the File Manager.
Run Folder Ovalsight
The folder ovalsight feature is designed to provide users with valuable insights into the structure and contents of a selected folder within a connector. This functionality enables users to understand the folder hierarchy comprehensively and obtain useful information about the folders and files. It provides a convenient way to understand the contents of a folder at a glance, enabling users to make informed decisions about their data.
Reports - Action Items
Add to Dashboards
Adding a report to a Dashboard enables data visualization by offering pertinent insights and metrics in a centralized and accessible format.
Remove from Dashboards
Remove from Dashboard removes the report from the dashboard.
Codes - Action Items
Add New Code
Supported data objects: Codes
When the OvalEdge application performs crawling, queries are cataloged and included in the data catalog. Additionally, the Querysheet feature enables users to record and monitor the queries executed within the system. Similarly, the Add New Code option allows users to include a new code or query to a chosen Connector/Schema in OvalEdge.
Select the desired Connector/Schema: Choose from the drop-down options to select the specific Connector and Schema where users want to add the code/query.
Provide the name: Enter a name or label for the new code/query. This name should provide a brief and meaningful description of the purpose or functionality of the code.
Enter the query: Input the query or code into the designated input field. This query represents the specific SQL statement, code snippet, or query language syntax that users want to add to the data catalog for the selected Connector/Schema.
Recommended Lineage and References
The 'Recommended Lineage and References' option serves a dual purpose in the application:
Lineage Establishment: When new codes are added, or modifications are made to existing codes from the query sheet, this functionality helps establish the latest connections and associations. It tracks the lineage of codes, documenting their origin, modifications, and relationships to other data objects.
References and Associations: Additionally, this feature displays the associations between the query and other data objects. It highlights the relationships and dependencies that the query has with various data elements, providing a comprehensive view of how the code interacts with the broader data ecosystem.
Delete Associations
When the "delete associations" option is utilized, it removes any connections or links the query has with other data objects. This action eliminates the associations between the query and related data objects.
Delete Lineage
Deleting a query's lineage removes the historical record of how the query was created, modified, and connected to other data objects. This action effectively erases the lineage information associated with the query.
Delete Code
Deleting code refers to the act of removing a specific code from the OE instance. When code is deleted, it is permanently removed and no longer exists within the DataCatalog > Codes.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA
Last updated
Was this helpful?