Term Summary Page
The Term Summary provides a consolidated view of all key details and metadata associated with a glossary term. These include the Term Descriptions, Term Details, Tags, Related Objects, Classifications, Manage Data Association Preferences, Additional Information, Custom Fields, and Ratings.
Anchor Menu
An Anchor Menu allows users to jump to specific sections of a webpage. Each item in the anchor menu links to a specific point (an anchor) on the same page, enabling users to quickly navigate to different parts of the content without having to scroll through the entire page manually.
Term Description
Each term has two key descriptions that help users understand the term's meaning and purpose.
Business Description: This provides the core definition or context of the term.
Detailed Description: This section provides an extension of the Business Description, offering additional information about the term, including formulas, technical details, images, and other relevant content.
Term Status
A new term will initially be in draft status. In the draft status, term details, including properties, object associations, classifications, and term relationships, can be curated and edited by users with domain privileges (Meta-Write access). Once the term is published, the details are fixed and cannot be edited. The term must be published for the term properties (Data Association Preferences) to be applied to the associated data objects.
Actions
Actions help users change the Term status from Draft to Published. Here, users can request to publish a specific term or publish it directly.
Viewer license users can “Request to Publish” or “Request content change.”
Publish a Term
By default, all Governance Roles (Owner, Custodian, Steward, and Governance Roles 4, 5, & 6) have the authority to publish a term. However, the admin can now configure the system setting businessglossary.term.publish to specify which Governance Role(s) have the authority to publish terms.
Navigate to Administration > System Settings > Business Glossary > Business Glossary Settings and search with the key (businessglossary.term.publish). Select the Value (Governance Role(s)) and click Save to update the configuration.
Add to Project
Users can choose to include terms in a default project, transforming it into a collaborative workspace where teams or groups collaborate to enhance term content and quality according to evolving business needs. This space facilitates tracking activity progress and managing tasks efficiently.
Governance Roles
The governance role identifies the team members accountable for governing a Term. Users would quickly know who to contact for term-related queries.
Governance stakeholders play a crucial role in ensuring the quality and consistency of term attributes within the Business Glossary. They are the subject matter experts in their respective domains and are responsible for curating the terms and addressing any concerns that arise as our business evolves and undergoes changes.
By default, each term at the domain level will have governance roles, including Owner, Steward, Custodian, and additional Governance Roles 4, 5, and 6 (if configured). At the term level, stewards have the ability to modify/update the governance roles, ensuring that individuals with the right expertise handle each term appropriately. The significant advantage here is that users can update governance roles for individual terms without affecting the broader domain configuration.
Cascade Governance Roles to all Terms (Publish & Draft)
Users can choose an option to cascade governance roles to all Terms, both published and draft, within a selected category or subcategory. This feature enables administrators to efficiently update governance roles across all Terms in a specific category or subcategory, ensuring consistent role management without the need to update each Term individually.
Click ‘Responsibilities’ icon.
Update the Governance Roles and click ‘Cascade to all Terms (Publish & Draft) within the category’ to cascade the updated governance roles to both published and Draft Terms.
Metadata Curation Score
The metadata curation score evaluates the quality, completeness, and accuracy of metadata for object types and terms. For Terms, the Metadata Curation score will be calculated based on:
Business description
Max points: 15
Less than 50 words - 0
Contains 50-100 words - 10 points
Contains more than 100 words - 15 points
Detailed description
Max points - 15
Less than 50 words - 0
Contains 50-100 words - 10 points
Contains more than 100 words - 15 points
Custom Fields are not null - 15 points
If custom fields are not configured - 15 points
Owner and Steward are not system administrators - 5 points Note: The Governance Roles score within the Metadata Curation score remains unaffected if the Steward, Owner, or Custodian assigned to a term is a default Admin.
Has at least one Associated Data - 10 points
Has at least one Related Object - 10 points
Has at least one Manage Associations - 10 points
Has at least one classification selected - 10 points
Has it been published at least once - 10 points
The following are the thresholds range for color coding:
Red: <25%
Yellow: 25% - 75%
Green: >75%
To customize weightages, navigate to Administration → Metadata Curation Score, select the required object from the Object Type dropdown list, and then customize the selected object attribute scores as per the requirement.
Term Details
Popularity
The Popularity Score can be a useful metric for understanding how widely a term is used among a group of users. It is a score calculated based on the number of times users interact with the term by viewing, endorsing, commenting, and adding tags to it. The table below displays the listed actions and their respective impacts on the popularity score. Some actions increase popularity, while others decrease it, and some have no effect.
Navigate to the term summary page
+ 1
Add a comment
+ 1
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.
Add Tag
+ 4
Version
Versioning refers to the number of times the term is revised from the initial draft to its publication. Every time it gets published, the version number increments by 1.
Published By
It displays the username of the user who has published the term from draft status to publish status.
Published On
It displays the Term's published date and time.
Service Request Count
It displays the total number of service requests raised on the term.
Tags
Tags serve as a systematic and logical method for grouping relevant terms. This grouping makes it easy to find and locate terms. Users can utilize tags to filter and narrow down their search, making it easier to identify relevant terms.
Related Objects
Term Relationships are links a specific term has with other terms and data objects in the ecosystem. These relationships serve as a road map for understanding how a term is connected to other terms or data objects. This makes it easy for users to find relevant information, explore and understand the related terms, and gain valuable insights into the interconnections within the data and business concepts.
It helps identify synonymous or related terms, which is crucial for maintaining data quality and tracking lineage.
Synonym Relationship
A synonym relationship signifies that two terms, Eg, "Medical Practitioner" and "Healthcare Provider," share the same meaning and are interchangeable. When users establish a synonym relationship, they can use either term to refer to the same concept. Thus, data associated with "Medical Practitioner" or "Healthcare Provider" can be governed similarly because these terms represent identical concepts.
Related Relationship
Conversely, a related relationship, such as the one between "Car" and "Gasoline," indicates that these terms are connected or associated in some way, but they are not synonyms. When users explore the "Car" term, they might want to understand its connection to "Gasoline" because cars often use gasoline as fuel. However, it is crucial to note that "Car" and "Gasoline" have distinct meanings and are not interchangeable. The interconnected relationship helps users grasp the associations between different concepts for a more comprehensive understanding.
Listed below are the different relation types that OvalEdge supports
Contains
"Contains" is a relational term denoting that Term1 encompasses or includes Term2, indicating a hierarchical or compositional relationship between the two entities. This relationship implies that Term2 is a constituent or part of Term1. Example: Folder "Contains" Documents
Is Contained in
The "Is Contained In" relationship between a term and a data object (table) signifies that the term is part of or included within the content of the table. In other words, the table holds data or information that involves or relates to the specified term. Example: Folder "Is Contained in" Drive
Is related to
Establishes a general connection between the term and the data object, highlighting a shared association. Example: Customer "Is related to" Consumer
Is synonym to
Links the term and data object as synonyms, signifying interchangeable usage and meaning. Example: Software Developer "Is synonym to" Programmer
Calculates
Depicts that the term derives the value for a data object or another term.
Example: Selling price calculates Profits
Calculates from
Denote a connection where data or values are derived through systematic computations, allowing for precise analysis and informed decision-making.
Example: Profit is calculated from the selling price and cost price
Replaced by
Demonstrates that the term 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 term has replaced the referenced data object in usage or significance. Examples: Manual Data Entry "Replaced from" Automated Data Integration
Filtered by
Specifies that the term is influenced or affected by the filtering process of the data object. Example: Candidates "Filtered by" Qualifications
Filters
Specifies that the term influences or filters another term or a data object from a larger set.
Example: Patient "Filters" Healthcare Provider
Is before
Details chronological or sequential relationships between the term and data object.
Example: Research "Is before" Publication
Is after
Details chronological or sequential relationships between the term and data object.
Example: Launch "Is After" Development
duplicates
Highlights that the term shares identical or overlapping content with the referenced data object.
Example: Customer Data duplicates Customer Info
defines
This indicates that the term defines or is a component of another term's or related object's definition.
Example: Algorithm defines Step-by-step procedure
Contrasts with
This indicates that the term has a different meaning, which is opposite to another term or data object.
Is a type of
This indicates that the term belongs to the same family as its related terms or data objects.
Example: Python "Is a type of" Programming Language
Has types
This indicates that the term has different types of itself, and those types are the related objects.
Example: Electronic Device "Has types" Smartphone, Laptop, Tablet
Is of
This indicates that the term is a member of another term or a data object.
Example: iOS is of Apple
Qualifies
This indicates that the term recognizes another term or a data object through certain criteria.
Example: Candidate "Qualifies" for a Job Position
Is qualified by
This indicates that the term is recognized by another term or a data object through certain criteria.
Example: Candidate "Is qualified by" Experience
Custom Relationships
OvalEdge has defined the above relationship types that can be used to define relationships. However, if the system-defined relationship types are insufficient, the admin can configure custom relationship types that the meta-write user can utilize while curating the term.
Admin can now configure custom relationships by navigating through Administration > System Settings > Business Glossary > Relationship Type Settings. When adding a custom relationship type, users must add the ‘Relation’ and ‘Opposite Relation’ text field options and later click the Save button to save the relationship type.
The added relationship type will be reflected in the term summary in the ‘Related Object’ section. Users can add this relationship type to the existing related objects added to the term.
Users can also control the visibility of specific relationship types (system and custom) from System Settings. Go to Administration > System Settings > Business Glossary > Relationship Type Settings and use the 'Viewable' column to show or hide each type. Disabled relationship types will not appear from the relationship edit search icon within the Term Summary. For example, 'defines' and 'is synonym to' will be hidden if they are unchecked.
Classification
Classifications categorise data objects based on their importance, ensuring that information is handled or protected appropriately. This helps users identify sensitive or restricted data. Security and Governance Admins can set classifications such as "PII," "Privacy," "Sensitive," "Internal," "Public," and others at the domain level.
These default classifications apply to all terms within the domain and inherit associated data objects. If the classifications are not set at the domain level, they won't appear at the term level.
Manage Data Association Preferences
A Term created within a specific domain automatically inherits all of the domain's properties, which can be customized on a term's detail page based on individual preferences.
The Association Preferences enhance the controllability of data objects by enabling:
Context Enhancement: It copies titles/descriptions to the catalog objects, giving more context.
Security Measures: It masks/restricts data, keeping it confidential.
Classification: It categorizes data based on confidentiality, sensitivity, or groups.
Governance Roles: It copies and overrides the existing Steward/Custodian/Owner on the catalog objects to supervise the term quality and content.
The data association options include:
Copy Title to Catalog: This replaces a data object's original title with the title of the associated term name, thereby simplifying data discovery and standardization.
Copy Business Description to Catalog: It replaces a data object's original business description with that of the associated term, providing more context for understanding.
Masked: This hides the real-time data in a table column or file column. The user can set masking schemes in the Term Summary Page. In the absence of masking, default masking will be applied to the data object.
Restricted: It can enhance overall data security by limiting access to data objects such as table columns, file columns, etc. Only authorized roles will have access to the data objects and can perform actions based on their assigned permissions.
Copy Steward / Custodian / Owner / Governance Role 4,5,6 to Catalog: It transfers the Governance role to the associated data object. The assigned Governance Role will oversee and maintain the content and quality of the data object, and assist data consumers in resolving any issues related to the respective data object.
Show Classification in Catalog: The classifications set at the term level will be applied to the catalog data objects associated with the term, and they will be displayed on the respective summary page of the data objects. This classification system helps categorize and find data objects based on classification, i.e., confidentiality or sensitivity.
Copy Tag to Catalog: This option automatically copies tag(s) from a Business Glossary term to its associated objects in the Data Catalog.
If a term has the same tags as the catalog object, only the unique tags will be copied; duplicates will not be added.
If a published term is changed to draft, any tags previously copied from it will be removed from the associated catalog object.
If a published term is deleted, any tags copied from it will be removed from the associated catalog object.
If tags are added later to a published term, the newly added tags won’t be directly copied to the objects until the term is drafted and published again.
Custom Fields
Custom fields offer a means to include extra term information or details not covered by standard term attributes on the Term details page. Users can create custom fields for text, code, numbers, and dates to enhance searchability and the usefulness of their data. These custom fields can be configured globally for all domains or specific domains.
When custom fields are created for a specific domain, terms linked to that domain will display the additional fields in the respective summary page within the Business Glossary.
No additional fields will be displayed in the absence of global or domain-specific custom fields.
Ratings
Ratings help consumers build trust in a Term based on how other users perceive it. The rating is the collective average of all the ratings given by different users. Users can endorse a Term by assigning a star rating, ranging from 1 to 5.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?