Data Domain
A Data Domain provides the business and governance context for a Data Product Manager to create and manage Data Products. The Data Product Manager registers Data Products under an assigned Data Domain. Each Data Product inherits the domain’s predefined governance roles, policies, and default access controls.
Within the domain context, the Data Product Manager curates metadata, associates supporting data objects, defines business descriptions, and manages delivery access modes in accordance with domain standards. Working within a Data Domain helps maintain consistent metadata, enforce governance requirements, and maintain clear ownership and accountability.
Create a Data Domain
The Data Product Manager creates a Data Domain to define a business or functional boundary for organizing and governing Data Products. During creation, the Data Product Manager assigns domain-level Owners, Stewards, Custodians, and default access roles.
All Data Products created in the domain inherit these governance settings. This maintains consistent access control and clear accountability.
To create a Data Domain, the Data Product Manager provides the following details:
Data Domain Name: The name of the business or functional domain. It serves as the primary identifier for grouping and managing related Data Products.
Choose an Avatar: Select a visual icon to represent the Data Domain for easier identification in listings and navigation.
Description: Describes the purpose and scope of the Data Domain, including the type of data covered and its business relevance.
Owner (Governance Role): The role responsible for the Data Domain, responsible for oversight and policy decisions.
Steward (Governance Role): The role responsible for maintaining metadata quality and standards within the domain.
Custodian (Governance Role): The role responsible for technical operations, including access, integrations, and system support.
Data Product Manager: The default role that manages Data Products in the domain, including metadata curation, object management, and governance settings.
Data Product Browser: The default role with browse or consumption access to Data Products, controlling visibility and access permissions.
Data Product Registry
The Data Product Registry is the central workspace for registering, curating, and managing Data Products before publication to the Marketplace. Data Product Managers use it to define metadata, assign governance roles, associate supporting data objects, configure delivery access modes, and start publishing workflows.
The Data Product Registry includes the following columns:
Data Domain: The business domain where the Data Product is categorized.
Parent Subdomain: The immediate subdomain hierarchy for the Data Product.
Data Product: The name of the registered Data Product.
Description: A brief summary of the Data Product’s purpose.
Detailed Description: An extended explanation of the Data Product’s scope and usage.
Tags: Classification or business tags used for search and discovery.
Status: The current lifecycle state of the Data Product (Draft, Published, and so on).
Delivery Access Mode: The level of access available (Data Preview or Data Read).
Data Objects: The number of data objects associated with the Data Product.
Popularity: A measure of usage based on subscriptions and interactions.
Owner: The governance role accountable for the Data Product.
Steward: The governance role responsible for metadata quality and standards.
Custodian: The governance role responsible for technical and operational management.
Governance Role (4,5,& 6): Assigned governance roles involved in approval and oversight workflows.
Data Product Manager: Users or roles responsible for managing and curating the Data Product.
Quick & Easy Data Discovery
Use Global Search to find data from any page in the application. Use the List View in the Registry page to refine results with filter, sort, and search options based on data object attributes.
Filter to narrow the search results based on a group of selected options from a drop-down with pre-defined filter options. Use the search bar in the filter window to refine your search and find the desired attributes. The Data Product Registry offers object filtering options based on Data Domain, Parent Subdomain, Tags, Status, Delivery Access Mode, and Governance Roles. 
Sort to arrange the results in a specific order, such as alphabetical, ascending, or descending. Based on the first-column sort results, the remaining columns can be further sorted. If a field contains both letters and numbers, sorting is based on the alphanumeric characters rather than the numeric values.
Search for specific data objects using keywords or phrases. It helps precisely identify data objects within the vast data ecosystem. Also, a Conditional search icon 
, represented by an eight-dot icon, is enabled next to the search field to further refine results by excluding/including keywords.
Global Search provides another way to discover Data Products across the platform. Users with Meta-Write privileges can configure search keywords for individual Data Products. Filters, sorting, and search options in Global Search allow Users to find data objects using configured keywords.
Configure View
Configure View lets Users choose how Data Product attributes appear in the List View. Users select attributes and set column order so important columns appear first.
In the left panel, select attributes. In the center panel, arrange column order. Then save the configuration. After saving, Users can access the view in the Views section.
Users can choose:
Set as my default (makes the view the user's default view)
Set as default for all users (sets the view as the default for other logged-in users)
Visible to all (displays the view to everyone in View options)
Register Data Product
Register Data Product lets Data Product Managers create and onboard a new Data Product. With the required access, the Data Product Manager defines the Data Product and ensures it aligns with domain governance standards before publication.
During registration, the Data Product Manager provides key metadata, including Data Domain, Data Product Name, Delivery Access Mode, Criticality, and Sensitivity. The Data Product Manager assigns governance roles such as Owner, Steward, Custodian, and other configured roles to establish accountability throughout the Data Product lifecycle.
The Data Product Manager also provides a Business Description to explain the purpose of the Data Product. Where permitted, the Data Product Manager can mark the Data Product as Instantly Available to allow immediate governed access for Data Browsers.
Data Product Registry Nine Dots
The following options are available in the Data Registry 9 Dot menu:
Manage My Watchlist: Add or remove selected Data Products from the User’s watchlist for tracking.
Manage Status: Update lifecycle status (Draft or Published) for selected Data Products in bulk.
Manage Tags: Add, remove, or update tags for selected Data Products.
Update Governance Roles: Assign or modify governance roles (Owner, Steward, Custodian) for selected Data Products in bulk.
Update Data Product Managers: Update users or roles responsible for managing selected Data Products.
Update Data Product Browsers: Update users or roles with browse or consumption access to selected Data Products.
Change Data Domain and Sub Domain: Move selected Data Products to a different Data Domain or subdomain.
Change Delivery Access Mode: Change the delivery access mode (Data Preview or Data Read) for selected Data Products.
Delete Data Products: Permanently remove selected Data Products from the registry, subject to authorization and governance rules.
Data Product Curation
Summary
After creating a Data Product, the Data Product Manager continues to curate and govern it for consumption. The Data Product Manager opens the Data Product Summary to add a Business Description and Detailed Description. These describe context and intended use.
The Data Product Manager assigns tags and associates required data objects, such as tables, files, APIs, and reports, that support the business use case.
The Data Product Manager defines related data objects and relationships. The Criticality and Sensitivity are updated to reflect business importance and data classification.
The Data Product Manager manages the Data Product lifecycle by requesting publication, publishing, or returning the Data Product to draft for updates. These actions maintain governance and accuracy.
Manage sections
From the Custom Fields > Manage Sections, manage the left and right sections for all the Data Products.
Manage Left and Right Section Layouts
Manage Section Layout lets Users add, edit, or delete custom sections, reorder section names, and hide sections as needed.
Data Contract
The Data Contract defines how a Data Product is structured, governed, refreshed, and consumed. The Data Product Manager curates and maintains Data Contract attributes, including business definitions, data quality expectations, refresh policies, service-level commitments, and usage guidelines.
The Data Product Manager can create, edit, manage, restore, and export the Data Contract. This includes defining Service Level Agreements, expected latency, retention policies, and access or compliance constraints. Maintaining these attributes supports alignment with domain governance standards and provides clear expectations for Data Browsers who use the Data Product.
Restore Empty Template
The Data Product Manager can reset the Data Contract to an empty template, removing all defined sections, fields, and values. This action permanently clears the contract configuration and is used when the contract must be rebuilt from scratch.
Manage Data Contract
Manage Data Contract lets the Data Product Manager define, maintain, and govern the Data Contract for a Data Product. The Data Product Manager can create, edit, and organize contract-specific fields that capture metadata, usage rules, service expectations, and governance requirements.
Selecting Manage Data Contract opens Custom Fields, where the Data Product Manager manages contract-specific fields either globally or for a specific Data Product.
Lineage & Relationships
Lineage & Relationships lets Data Product Managers curate and govern how a Data Product connects to upstream and downstream assets. With Meta-Write access, Data Product Managers can view, define, and maintain lineage and relationship information.
From a lineage perspective, Data Product Managers validate and curate upstream source objects and downstream dependent assets.
From a relationships perspective, Data Product Managers define and maintain logical relationships between the Data Product and related tables, files, reports, APIs, and other Data Products.
Related Objects
Related Objects help identify and manage synonymous and related Data Products, maintaining consistent business definitions and accurate relationships. By defining and maintaining these relationships, the Data Product Manager keeps related Data Products governed consistently.
Synonym Relationship
A synonym relationship signifies that two Data Products, For Example, "Medical Practitioner" and "Healthcare Provider," share the same meaning and are interchangeable. When users establish a synonym relationship, they can use either Data Product to refer to the same concept. Thus, data associated with "Medical Practitioner" or "Healthcare Provider" can be governed similarly because these Data Products represent identical concepts.
Related Relationship
A related relationship shows that two Data Products are connected but do not represent the same concept. For example, the Data Products Car and Gasoline are related because gasoline is used to operate a car, but they have different meanings and are not interchangeable. This relationship helps users understand how different Data Products are contextually linked within the data ecosystem.
Listed below are the different relation types that OvalEdge supports
Contains
"Contains" is a relational Data Product denoting that Data Product1 encompasses or includes Data Product2, indicating a hierarchical or compositional relationship between the two entities. This relationship implies that Data Product2 is a constituent or part of Data Product1. Example: Folder "Contains" Documents
Is Contained in
The “Is Contained In” relationship indicates that a Data Product’s data is included within a specific data object, such as a table, file, or dataset. It indicates that the data object stores or represents information about the Data Product, making the Data Product a logical subset of that object.
Example: ‘Customer Profile’ Data Product “Is contained in” ‘Customer_Master’ table
Is related to
Establishes a general connection between the Data Product and the data object, highlighting a shared association. Example: Customer "Is related to" Consumer
Is synonym to
Links the Data Product and data object as synonyms, signifying interchangeable usage and meaning. Example: Software Developer "Is synonym to" Programmer
Calculates
Depicts that the Data Product derives its value from a data object or another Data Product.
Example: Selling price calculates Profits
Calculates from
Denote a connection in which data or values are derived through systematic computations, enabling precise analysis and informed decision-making.
Example: Profit is calculated from the selling price and the cost price
Replaced by
Demonstrates that the Data Product has been
replaced by the referenced data object. Example: Traditional Hard Disk Drives (HDDs)
Replaced by Solid State Drives (SSDs)
Replaced from
Indicates that the Data Product has replaced the referenced data object in usage or significance. Examples: Manual Data Entry "Replaced from" Automated Data Integration
Filtered by
Specifies that the Data Product is influenced or affected by the filtering process of the data object. Example: Candidates "Filtered by" Qualifications
Filters
Specifies that the Data Product influences or filters another Data Product or a data object from a larger set.
Example: Patient "Filters" Healthcare Provider
Is before
Details the chronological or sequential relationships between the Data Product and the data object.
Example: Research "Is before" Publication
Is after
Details the chronological or sequential relationships between the Data Product and the data object.
Example: Launch "Is After" Development
duplicates
Highlights that the Data Product shares identical or overlapping content with the referenced data object.
Example: Customer Data duplicates Customer Info
defines
This indicates that the Data Product defines or is a component of another Data Product's or related object's definition.
Example: Algorithm defines a Step-by-step procedure
Contrasts with
This indicates that two Data Products represent opposing or mutually exclusive concepts within the same business context. It is used to highlight differences where understanding one Data Product requires awareness of another that represents an alternative or contrasting scenario.
Example: Profit “Contrasts with” Loss — both are related financial outcomes, but represent opposite business results
Is a type of
This indicates that a Data Product represents a specific category or subtype within a broader classification of related Data Products or data objects. It defines a hierarchical relationship where the Data Product inherits the general characteristics of the higher-level concept.
Example: Python “Is a type of” Programming Language
Has types
This indicates that a Data Product represents a broad concept that can be categorized into multiple specific types. The related Data Products represent distinct subtypes within the same overall category.
Example: Electronic device “Has types” Smartphone, Laptop, and Tablet.
Is of
This indicates that the Data Product is a member of another Data Product or a data object.
Example: iOS “is of” Apple
Qualifies
This indicates that the Data Product recognizes another Data Product or a data object based on specific criteria.
Example: Candidate "Qualifies" for a Job Position
Is qualified by
This indicates that the Data Product is recognized by another Data Product or data object based on specific criteria.
Example: Candidate "Is qualified by" Experience
Custom Relationships
OvalEdge provides predefined relationship types for defining Data Product relationships. If the predefined types are insufficient, an Admin can configure custom relationship types for Meta-Write users to use when curating a Data Product.
Authorized users configure custom relationships by navigating to Administration > System Settings > Data Product. When adding a custom relationship type, enter values in the Relation and Opposite Relation fields, then select Save.
The new relationship type appears in the Related Objects section of the Data Product Summary. Users can apply this relationship type to existing related objects linked to the Data Product.
Users control the visibility of system and custom relationship types in System Settings. In Administration > System Settings > Data Product, use the Viewable column to show or hide each relationship type. Hidden relationship types do not appear in the relationship edit search in the Data Product Summary. For example, ‘defines’ and ‘is synonym to’ are hidden when they are not selected.
Nine Dots Action Menu
The Nine Dots Action Menu provides the Data Product Manager with centralized control to govern, manage, and maintain a Data Product throughout its lifecycle. Through these actions, they can curate metadata, manage governance assignments, control access and subscriptions, maintain data contracts, and ensure the Data Product remains compliant with domain standards.
These actions are permission-controlled and role-dependent.
Add/Remove from Watchlist: Bookmark a Data Product for quick access and monitoring.
Custom Fields History: A chronological log of changes to custom fields, including additions, updates, and value changes with user and timestamp.
Update Governance Roles: Modify governance role assignments such as Owner, Steward, and Custodian.
Update Data Product Managers: Assign or modify users or roles responsible for managing the Data Product.
Update Data Product Browsers: Manage which users or roles can browse or access the Data Product.
Revoke Subscription: Remove a user’s access to a previously subscribed Data Product.
Change Data Domain and Sub Domain: Reassign the Data Product to a different Domain or Subdomain.
Remove All Associated Data Objects: Remove all linked data objects (tables, files, reports, APIs) from the Data Product.
Change Delivery Access Mode: Change the delivery access level between Data Preview and Data Read.
Make Product Instantly Available: Publish the Data Product for immediate access without approval. An expiry date must be set.
Publish Data Product
Publishing a Data Product is a governance step that verifies the Data Product meets governance, quality, and compliance standards before it becomes available for use.
After completing metadata curation, the Data Product Manager submits a publish request. The assigned governance role reviews and approves the request. This separation of responsibilities supports accountability and prevents publication of incomplete or unapproved Data Products.
The authorized Governance Role(s) have access to publish the Data Product directly.
Post-Publish Checklist
Visibility: Confirm the Data Product is published and visible in the Marketplace with the appropriate Data Domains and user roles.
Subscription Readiness: Verify subscription settings, delivery access mode, and expiration rules.
Contract Completeness: Ensure the Data Contract is complete, versioned, and reflects access rules, refresh policies, and usage guidelines.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?