Navigate Across the Data Catalog
In this segment, we will explore a variety of data objects, navigation methods in the Data Catalog, and the diverse features and functionalities enhancing data governance.
Data Objects
The crawled metadata information from remote data sources is organized intelligently into separate tabs on the main page of the Data Catalog. The data objects include:
Databases
-
Tables
Table Columns
File
File Columns
Reports
Report Columns
Codes
-
APIs
API Attributes
List View of Data Objects
Viewers can conveniently access metadata for various data object types in one centralized location. The List View is a consolidated view that displays the crawling, profiling, and metadata information.
Quick & Easy Data Discovery
Streamline data discovery with the Global Search feature enabled at the top of the main header is conveniently accessible from any page within the application. Utilize the List View in the Data Catalog page to improve the search experience with filter, sort, and search options based on data object attribute details.
Filter to narrow the search results based on a group of selected options from a drop-down with pre-defined filter options. Utilize the search bar within the filter window to refine further and find the desired attributes. The Data Catalog offers object filtering options based on Data Source, Database, Tags, Terms, and Governance Roles. Advanced Filtering for Single/Multi-Value Columns in Data Catalog List View In the Data Catalog All Objects List View, single-value columns (Type, Connection Name, Database, Schema) now feature two dropdown options such as Equals to and Not equals to. Multi-value columns (Tags, Terms, Domain, Category, Sub Category, Classification, Multi-option code custom fields) feature two dropdown options:
"Equals to Any of / All of"
"Not Equals to Any of / All of"
Apply these conditions to multi-value columns to filter objects as follows:
Equals to Any of – Displays objects that match any of the selected values.
Equals to All of – Displays only objects that match all selected values.
Not Equals to Any of – Excludes objects that match any of the selected values.
Not Equals to All of – Excludes objects that match all selected values.
Sort to arrange the results in a specific order, such as alphabetical, ascending, or descending. Based on the first column sorting results, the contents of the rest of the columns can be further sorted. If a field contains a combination of letters and numbers, the sorting is done based on the alphanumeric characters and not the numerical values.
Search for specific data objects using keywords or phrases. It helps in precisely identifying the data objects within the vast data ecosystem. Also, a Conditional search icon
represented by the eight dots icon is enabled next to the search field to further refine the search results by excluding/including keywords in search results. Search using Conditional Filter
Dependent filters and search
An Add-on functionality has been integrated to the existing filter and search mechanism in which the available options in one filter change based on the selection made in another. This dynamic filtering helps to refine the search in a more guided and relevant way.
For example, filtering a Connection Name (here Delta Lake) displays all its dependent objects. (Database, Schema, Title, Tags, Terms, etc.)
For example, searching a Table (here Equals to CUSTOMER) displays all its dependent objects. (Type, Connection Name, Database, Schemas, Title, etc.)
Configure Views
The Configure View feature allows all (Meta-Read or Meta-Write access) to customize the List View Columns according to their preferences, allowing for a personalized display of data object attributes and metadata details. Select the default System View format on the Data Catalog's List Page (displaying a set of predefined attributes), explore public views if available, or create a customized view that aligns with specific requirements. We can create as many configured views as per the requirement.
To learn more about the Configure View provided in the Data Catalog List Pages, please visit: Configuring Views
Data Objects Summary View
The Data object summary provides a detailed overview of metadata, containing various dates (Crawled date, Meta-sync date, Modified date, etc.) and fields specific to the data object. It includes crucial information about the data object, enabling it to gain deeper insights for analysis and decision-making.
Meta-Write privileges have the flexibility to actively manage and refine the data object details directly from the summary page. This capability allows them to customize descriptions, assign tags and fields, certify, and endorse data objects ensuring they meet specific requirements and preferences.
Some of the most common fields and features in the Summary Pages are mentioned below:
Anchor Menu
Anchor Menu enables quick navigation within a webpage by linking each menu item to a specific section. It helps move directly to different parts of the content without manual scrolling.
Left Section
Descriptions
Business Description: It displays the business purpose for creating a particular data object (such as Tables, Reports, Files, APIs, or Codes). On the summary page, Authors can edit business descriptions and attach images, links, videos, or tables, apply basic formatting options to the text, and add object references using the "@" annotation. In the List View, while editing business descriptions, like formatting and Select All text options, Code View, and Help icon to reveal shortcuts.
Technical Description: A clear overview of how the data object is formatted and structured from a technical perspective. On the summary page, Authors can edit technical descriptions to attach images, links, videos, or tables, apply basic formatting options to the text, and add object references using the "@" annotation. In the List View, while editing technical descriptions, like formatting and Select All text options, Code View, and Help icon to reveal shortcuts.
Source Description: A detailed account of the comments on the data object at the remote data source is fetched and displayed as a source description.
Table Columns
The table summary displays the list of all the columns. The following enhancements have been made as below:
The required column(s) can be selected and added to the access cart.
A new configured view can be created from the System View drop-down list.
An expanded view icon helps expand the table columns' view.
Clicking on any table column displays its quick view summary.
Tags & Terms
Displays the tags or terms associated with the data object.
Classifications
Classification is the process of categorizing data objects based on sensitivity, confidentiality, and organizational importance. When creating a domain, the related classifications are configured. Any configured classification(s) can also be selected as default. The domain-specific classifications will appear on the related term(s) summary page. If "show classification in the catalog" is enabled for a term, its associated object(s) will also inherit these classifications.
Catalog Details
Catalog Details refer to the metadata and descriptive information about objects stored in a catalog or database. The catalog details include Type, Row Count, Column Count, Environment, etc.
Type: Type refers to the specific object type or an attribute value. Meaningful Name
Tables: The object type is a Table, View, or Materialized View.
Table Columns: The object type is a Table, View, or Materialized View, and the Data Type can be a string, int, number, Varchar, etc.
Files: The object type is a File/Folder.
File Columns: The object type is a File/Folder, and the Data Type can be string, int, number, etc.
Reports: This object type is a report type available for reporting tools such as dashboards, reports, views, etc.
Report Columns: The object type is an attribute type, and the data type can be a string, integer, double, date, Boolean, decimal, etc.
API Attributes: The API Attribute Type is a Request or Response parameter. The Data type can be Int, String, Object, Number, etc.
GUID: A GUID (Globally Unique Identifier) is a 36-character unique identifier assigned to a data object during the crawling process.
Authoritative Source: Identifies whether the data object is recognized as the official or trusted source. It means the data comes from a reliable system that is recognized as the correct version to use for reporting, analysis, and decision-making.
Has Lineage: It indicates whether the table/file has a lineage. Yes implies the presence of lineage; No indicates the absence of lineage.
Environment: It displays the instance from which the connector is established, such as development, production, or quality assurance (QA).
Has Relation: It indicates whether the table has relationships. Yes implies the presence of relationships; No indicates the absence of relationships.
Originating Source: Specifies where the data object originally came from or was generated. Ex: Manual/Crawl/Virtual.
Connector Description: Displays additional details about the connector used for crawling the object.
Row Count: It displays the total number of rows in that particular data object.
Importance Score: The Importance Score reflects how critical a data object is within the database. It is determined by analyzing the object's relationships and lineage specifically, how many downstream objects depend on it. For detailed information on how the score is calculated and used, refer to the Importance Score Calculation
Column Count: It displays the total number of columns present in the Table/File/Report.
Popularity Score: Popularity Score is a valuable metric for understanding how widely a data object is used within a group. It is a score calculated from the number of times the users interacted with the data object by viewing, endorsing, commenting, and adding tags. The table below lists actions and their respective impacts on the popularity score. Some actions increase popularity, some decrease it, and some may not affect it.
Refreshing the summary page
+1
Changing the Wiki of an object
+3
Add Published Term
The score improves by 3 if the Business Description is copied. Otherwise, it increases by 1.
Add Tag
+4
Adding a comment
+5
Endorsement Rating (5-star rating)
Based on the star rating, the Endorsement Rating increases by 1 for a one-star rating and 5 for a five-star rating.
Queries a data object
+3
Crawl & Profile Details
Profiling Status: It displays the status of data profiling.
Created Date & Created By: It displays the object's first crawl date and the user who initiated it.
Last Crawled Date: The Last Crawled Date field displays the date when the object was last crawled from the Data Source.
Last Meta Sync Date: It displays the date and time when data changes were last made to a data object at the remote data source.
Last Profiled Date: The Last Profiled Date field displays the date when the object was last profiled.
User Activities
Last Certified Date and Certified By: The Last Certified Date displays the date on which the data object was certified, and the Certified By displays the username who certified the data object.
Last Modified Date and Last Modified By: This displays the date and time for any meta-data changes to a data object in the application and the user who modified it.
Last Populated Date: It displays the date when the data object's metadata was last updated using APIs.
Reference Count: An object's reference count indicates how many times the object has been referenced.
Service Request Count: The Service Request Count displays the total number of service requests raised on the data object.
Custom Fields
Custom Fields are data fields created to capture specific information relevant to an organization's unique needs. They go beyond the standard fields displayed on the summary page of any data object or item, allowing users to add more context, which makes data analysis more meaningful and allows better categorization and tracking.
Ratings
Ratings help consumers build trust in an object based on the feedback. The overall rating reflects the average of all submitted ratings. A star rating from 1 to 5 can be assigned to endorse a data object.
Associated Policies
The Data Catalog now supports linking policies directly to specific data objects through the Policy Manager. This integration associates relevant governance or compliance policies with tables, files, reports, and other cataloged assets.
Right Section
Call To Action
This section provides the necessary actions related to viewing and accessing permissions.
View Access Permissions: Access permissions give a preview of the permissions a user(s) or role(s) has on the corresponding data object. The corresponding metadata permissions can be viewed via OvalEdge access. Similarly, the data permissions at the source level can be viewed via Remote access. A Producer (Author) can view all the permissions of various role(s) or user(s) that have on the object. In contrast, a Business user can only view the corresponding permissions one has on that data object.
Access Instructions: These are guidelines provided by the Integration Admin during the integration of a remote connector. They explain the necessary access permissions and steps required to connect with a specific system or connector.
Add to Project: “Add to Projects” assists in adding the selected Data Object to the default project.
Quality Score & View Dashboard: Displays the Data Quality score of the data object. Click "View Dashboard" to go to the dashboard and see all the score details.
Last Anomaly Detection On: Click the "Last Anomaly Detection" to view the most recent anomaly detection identified in a dataset.
Report Data Quality Issue: Click "Report Data Quality Issue" to raise a new service request on the data object.
Manage Table: Authors can edit the virtual table name, source description, and virtual table columns associated with the table.
View Data Changes: This directs to Advanced Tools > Data & Metadata Changes > Data Changes, where the profiling history and previously executed profile details are displayed. All Profiling statistics, including column names and values like null count, distinct values, top, minimum, and maximum values, are organized in a tabular list for easy comparison across different time points.
View Metadata Changes: This directs to the Advanced Tools > Data & Metadata Changes > Metadata Changes, which displays the list of changes that an object has undergone during crawling. It shows newly added, updated, or deleted data objects, including column name, size, position, and their addition and deletion status.
Request Missing Content: Flag missing or incomplete metadata on any data objects such as tables, files, reports, or APIs directly from the Summary Page.
Select the type of missing metadata like Descriptions, Tags, Terms, Custom Fields, or Others and suggest the content using a free-text field (up to 5000 characters).
Once submitted, a notification and email are sent to the assigned Steward, highlighting the details of the request. The associated object is automatically added to the Watchlist for easy tracking.
If the Steward updates the requested metadata, the user is notified via the Watchlist Notification, ensuring a complete feedback loop and improving collaborative metadata curation.
Call to Action
The Call To Action buttons can be configurable (View/Hide). For this, navigate to Administration > Custom Fields > select any Object Type > Global > Call To Action. Here, check or uncheck the Call To Action button(s) based on their requirement.
Metadata Curation Score
The metadata curation score assesses metadata quality, completeness, and accuracy for object types and terms.
The score is based on evaluations in areas like:
Meaningful Name
Starts with an Alphabet: +1 point if the name begins with a letter (not a number or special character).
Length: +2 points if the name is longer than five characters. Word Separation: +2 points if the name has at least two words separated by spaces or hyphens.
Capitalization: +2 points if each word starts with a capital letter and has at least two words.
Valid English Words: +3 points if the name contains recognizable English words separated by underscores, hyphens, or capital letters.
Business description
Maximum points: 20
Less than 50 words - 0
Contains 50-100 words - 10 points
Contains more than 100 words - 15 points
Technical description
Maximum points: 20
Less than 50 words - 0
Contains 50-100 words - 10 points
Contains more than 100 words - 15 points
Associated Terms
Maximum points: 15
There must be at least one Term associated with the object.
Associated Tags
Maximum points: 5
There must be at least one Tag associated with the object.
Governance Roles
Maximum Points: 10
Non-admins should be Owner and Steward
Custom Fields
Maximum Points: 20
All Custom Field values should be filled
The following are the thresholds range for color coding:
Red: <25%
Yellow: 25% - 75%
Green: >75%
For Reports and Files, the help for Column Scores is 'Weighted score of average curation score of attributes'
The following table provides a clearer understanding:
Table Column, File Column, Report Column, API Attribute, Codes, Databases
Tables, Files, Reports, APIs
Meaningful Name or title (OOTB) Check
10
5
Business Description availability Check
20
10
Technical Description availability Check
20
10
Governance Maturity Check
10
5
Custom fields metadata completeness Check
20
10
Term association Check
15
8
Tag association Check
5
2
Child elements maturity Check
-
50
TOTAL
100
100
For Reports, Table, and Files, the "Weighted score of average curation score of attributes" refers to calculating the overall curation score by combining two key parts:
Object-Level Metadata Score (50% weight): This part is based on the quality of the metadata directly associated with the object itself (e.g., report or file), scored according to specific criteria such as business/technical descriptions, custom fields, associated terms, tags, owner/steward roles, and the title.
Attribute-Level Metadata Score (50% weight): This part represents the average score of the individual attributes (like columns) that belong to the report, table, or file. Each attribute (e.g., a column in a table, report, or file) is scored separately based on its business and technical descriptions, custom field completion, etc. The scores of all the attributes are averaged to calculate the "attribute-level metadata score."
The formula then combines these two scores, applying a 50% weight to each, resulting in an overall "Weighted score of average curation score of attributes" for the report or file.
Users can now configure and customize weightages for different metadata attributes to align the scoring model with their internal governance standards and priorities. The system automatically ensures that the total weightage equals 100, maintaining scoring consistency and accuracy across evaluations.
To do this, users must navigate to Administration → Metadata Curation Score, select the required object from the Object Type dropdown list, and then customize the selected object attribute scores.
Data Consumption Score
Data Consumption Source indicates whether the object is eligible for direct data access.
If the object is a Data Consumption Source, it can be added directly to the Access Cart.
If an object is not a Data Consumption source, an alternate Data Consumption Source object can be added in its place.
Users can add alternate data sources by unselecting the ‘Data Consumption Source’ checkbox and later clicking on ‘Proceed’ in the popup.
When a user adds a non-data consumption source to the access cart, a pop-up is displayed suggesting the alternate consumption sources to be added to the access cart. The user can still go ahead and add the non-data consumption source object to access if they want to raise an access request for it.
Mark as Critical Data Element
A Critical Data Element (CDE) is important data like a table or column that impacts business decisions, reporting, or compliance.
Only SGAs and Governance Roles (such as Owners or Stewards) can use the Yes/No toggle beside "Mark as Critical Data Element" to easily update its status.
Change the status of an object between Critical Data Element and None.
Manually override the Recommended status.
Governance Roles
The Data Governance role identifies the members of the team who are accountable for governing an asset. Asset-related contacts become easily identifiable for quick query resolution. Authorized access allows adding and modifying Owners, Stewards, Custodians, and additional configured Governance Roles (4, 5, 6) using the dropdown list for enhanced control.
Top Users
Top Users shows the active users who have interacted with the data object, including their scores. The owner, steward, custodian, and governance roles (if set) are listed first. Other users are listed based on their activity. Each time a user accesses the data object summary, executes a query, or adds a comment, their score increases by one.
Manage sections
From the Custom Fields > Manage Sections, manage the left and right sections for all the cataloged objects, such as Schema, Table, Table Column, Report, Report Column, etc.
Manage Left and Right Section Layouts
Use Manage Section Layout to add, edit, or delete custom sections, drag the specified section name position, and hide any section name based on the requirement.
Data Access
Users with the capability of appropriate Data Access permissions (Data Read/Data Preview/Data Write) can view a sample set of profiled data (configurable in Connector Settings) for a specific data object in the Data Preview Page. This feature helps in understanding the data by providing a practical view of the object and its associated information.
Lineage
Understanding data lineage is crucial for effective data management. The application has tools to help users access and interpret this data. This overview will show how users can navigate and understand lineage data in the Data Catalog.
Users access lineage information at the object level in the Data Catalog. The lineage tab, available for every object, details how data objects are interconnected and flow through connected source systems.
Data Lineage Tracking
Data lineage involves tracking a data object's complete transition path, revealing its origins and destinations, and ensuring data traceability. This integrated Data Catalog feature allows organizations to improve data quality by identifying and addressing underlying issues, leading to more informed decision-making processes. Establish data lineage using a variety of available methods and techniques for greater flexibility and control. The blue lines represent auto lineage, and the orange lines represent manual lineage. A toggle option is available to switch between Summary Lineage View and Detailed Lineage View (Graphical View).
Graphical View
The Graphical View provides a visual overview of the lineage, showing connections and relationships between data objects. Here's a detailed breakdown of what the graphical view includes:
Lineage Nodes
Each object in the lineage diagram is represented by a circular node. These nodes aren't just visual elements but hubs of information that provide valuable insights at a glance. By looking at a node, users can immediately access the following essential information:
Root Object Details: The root object is the object for which we view the lineage. The tooltip in the diagram shows the object's connection, schema, and object type.
Upstream Objects: Upstream objects refer to all objects in the source data flow(left side), showing how data moves from its origins to the selected object.
Downstream Objects: Downstream objects include all objects in the destination, revealing how data is processed and delivered to its final destination.
Certification 
DQ Score: The object's overall Data Quality (DQ) score is shown at the top left of the node (if it's calculated within the application). Clicking on this DQ score lets users explore the DQ dashboard for that specific object, getting deeper insights into data quality.
Additional Info on Node: There's more information at the bottom right of the node. The application shows an icon representing the object's connector, quickly referencing the associated system. This visual cue helps users understand the object's origins and connections within the system.
Lineage View Types
Two types of lineage views are available:
Summary Lineage View
Detailed Lineage View
Steps to Change Lineage Views:
Navigate to the Lineage tab of a data object.
Use the toggle at the top left to switch between Summary View and Detailed View.
The interface will display the selected view instantly.
Summary Lineage View
The Summary Lineage View shows a simplified flow of data between core systems. It focuses on high-level connections important for business analysis.
Key Points:
Displays only essential data sources and endpoints
Excludes technical components such as:
Transformation logic
Datasets
Semantic tables
Intermediate processing layers
Provides a clear business-level view for quick validation and review.
Detailed Lineage View
The Detailed Lineage View shows the complete path of data from source to destination. It supports technical analysis and governance activities.
Key Points:
Includes all system-level components such as:
Transformation logic
Datasets
Semantic tables
Intermediate processing layers
Offers full traceability of data flow
Enables impact analysis, governance tracking, and audit preparation
Summary Lineage Configuration
The key (lineage.summary.view) in System Settings controls the availability of the Summary Lineage View. This configuration applies at the instance level and impacts all users within that instance.
Configuration details:
Click on the System settings.
Locate the key lineage.summary.view.
The default value for the key (lineage.summary.view) is False.
Set the value for the key (lineage.summary.view) to True.
This enables the Summary Lineage toggle in the lineage screen (data catalog).
The Summary Lineage View becomes the default view for the instance.
Set the value for the key (lineage.summary.view) to False.
The Summary Lineage toggle remains hidden in the lineage screen (data catalog).
After migration, or when the setting is enabled, a complete lineage rebuild is required to avoid incomplete or inconsistent display.
Lineage for Selected Nodes
In Detail Lineage, the Lineage for Selected Nodes feature enables precise control over the nodes displayed in the summary lineage view, allowing focus on specific data flows while maintaining an accurate representation of the underlying data relationships.
Key Capabilities
Focused Node Selection: Adds only the relevant crawled objects from the data catalog to the lineage view, ensuring that the visualization highlights the most important data elements.
Improved Clarity: Reduces unnecessary complexity in the lineage diagram, making it easier to trace data movement and dependencies.
Efficient Analysis: Supports quicker understanding of complex lineage scenarios by presenting a clean and contextually meaningful view.
Steps to Select Objects for Lineage:
Click on Lineage for Selected Nodes.
The Add Objects pop-up will appear, displaying crawled objects available in the data catalog.
Review the list and select the relevant objects by clicking the check box beside each object.
After selecting the desired objects, click Submit to include them in the lineage view.
3 Dots Options
Quick View: Users can view a brief summary of the dataset or object.
View Association (only for datasets): Users can view associated objects for datasets in the lineage.
View References: Users can view references associated with the data set or object.
Copy Name: Users can copy the object or dataset name to the clipboard.
Zoom in and out Functionality: Users can zoom in or out on the graphical lineage diagram to improve visualization.
Full screen: Users can click the full-screen option to view the graphical lineage in full-screen mode, which helps them better understand the data flow.
Lineage Differentiation
The platform uses line colors in the lineage diagram to indicate how nodes are connected.
Orange lines show Manual Lineage.
Dark blue lines show Auto Lineage.
Lineage Lines: The lines connecting two nodes in the graphical view show how data moves from one node to another node. Clicking these lines reveals column lineage info.
Column Mapping
This section shows how columns in the source and destination objects are mapped. This can also be mapped by users using lineage maintenance.
Graphical: This displays a graphical representation of the column mapping. It shows the columns of the source object on the left and those of the destination object on the right, along with the mappings.
Tabular: This section presents the column mapping in a table format, which the user can download for detailed analysis.
Summary: A brief view of the query that creates the lineage. This page appears when a query links two nodes.
Code/Query: The tab shows the transformation code with correct syntax and explains data processing.
Tabular View
Lineage data is presented in a structured table format, showing one upstream and one downstream lineage level. This clear representation helps users understand data flow easily, and they can download the table for detailed analysis.
Download
Users can download the tabular lineage representation for in-depth data lineage analysis. This empowers them to gain insights, make informed decisions, and ensure data integrity. The application lets users customize their download preferences, specifying what they want to download and the level of lineage data to include. These options ensure users get exactly the information they need for their analyses.
Process Upstream/Downstream Objects
Process Upstream and Downstream Objects allow updating three key parameters:
Applying Caution certification to downstream objects
Remove Caution certification to downstream objects
Copying Metadata using Lineage.
Caution for All Downstream Objects
The "Caution All Downstream Objects" feature allows users to apply caution to all downstream objects linked to the current data object, alerting them to be careful when interacting. Caution is added to downstream objects when the source object is certified as "cautioned." This promptly informs users about potential issues or sensitive data in related objects (Tables, Files, or Reports) and serves as a warning.
Remove Caution: All the Downstream Objects
The "Remove Caution" feature removes caution from downstream objects in the lineage to maintain data clarity and prevent unnecessary caution labels.
Copy Metadata using Lineage
The application allows copying metadata, such as Tags, Business Description, and Technical Description, from one data asset to another using lineage.
To copy metadata using lineage, Lineage must be built.
Steps to Copy Metadata Using Lineage:
Go to the Data Catalog and open any object summary page.
Click the 9-dot option at the top right corner and choose “Process Upstream / Downstream Objects.”
Select “Copy Metadata using Lineage.”
Turn on the Toggle button to copy metadata to the object columns.
Choose the direction - Upstream or Downstream.
Select the required metadata types to copy:
Tags
Business Description
Technical Description
For each selected type, choose how to copy:
Cascade When Empty – copy only if the target is empty.
Overwrite – replace the existing metadata.
Click the Submit button.
A pop-up will appear with a warning message asking for double confirmation.
“Are you sure? Copying metadata will permanently update all lineage objects. Once added, it cannot be reverted!"
Click the Submit button to confirm.
The system will run a job. If successful, the metadata will be copied.
To know more about Lineage and how to build them, please click here.
View and Build Entity Relationships
Entity Relationships provide a clear visual representation of how different tables in data sources connect and interact, helping to understand the dependencies within the data. The relationships are calculated based on Primary Key - Foreign Key relationships defined at the remote source.
To learn more about Entity Relationships and how to build them, please visit: Entity Relationships
Refer Objects & View References
With Meta-Read or Meta-Write access, refer or link to various Data Objects and users within text fields such as Collaboration Messages, Business Descriptions, and Technical Descriptions using the "@" annotation. Instances where a specific object is referenced are displayed in the References Tab of that respective object. This References functionality helps to trace links, providing insights into the interconnected relationships among data objects.
Rating & Certifying Data Objects
Ratings build trust in a data object by reflecting how others perceive it. The overall rating is the average of all the submitted ratings. Assign a star rating from 1 to 5 to endorse a data object.
Certification assures that data meets specific standards and is reliable for decision-making. Certification labels each object clearly, showing if it's reliable ("certified") or not ("violated" or "Cautioned") or not in use ("Inactive"). Use the ‘Process Upstream/Downstream Objects’ option in the 9 Dots menu of a root object to caution all connected upstream and downstream objects in its lineage.
To learn more about Certifications, please click here.
Conversations
Each data object's Summary Page in the Data Catalog includes a Conversations window for interacting, sharing insights, commenting, and holding real-time discussions with key stakeholders such as data owners, stewards, custodians, and prominent users.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA
Last updated
Was this helpful?