> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/business-glossary/change-management-on-terms.md). # Change Management on Terms ## Who can perform change management? Governance stakeholders \[Owner, Custodian, Owner, Governance Roles 4,5,6 (if configured)] and the authorised users with Meta-Write privileges on the domain can change the Term details within the Business Glossary. Business users with Meta-Read permissions can initiate the creation of new terms and the deletion of existing terms by submitting a service request that undergoes an approval workflow. Once approved, the terms are created and integrated into the glossary. Furthermore, suppose Viewer users wish to suggest changes to content for a term. In that case, content change requests can be raised that follow an approval workflow, ensuring that modifications are carried out if they meet the validation criteria. ## Term Domain Change Changing the domain for a term enables users to keep the Business Glossary terms up to date and aligned with evolving business dynamics. Moreover, it significantly improves the findability of terms, allowing users to quickly locate relevant terms based on their specific areas of interest and focus. ## Update Governance Roles at Term Level The default governance roles set at the domain level automatically apply to the terms created within that domain. Additionally, users can modify the governance roles at the term level, ensuring that individuals with the right expertise handle each term appropriately. The advantage here is that users can update governance roles for individual terms without affecting the broader domain configuration. ## Term Deletion In a specific domain where terms are created, the Stewards have the authority to delete terms. Deleting a term involves removing all connections between the term and associated data objects. When a term is deleted, the initial link between the term and the data becomes void, and associated properties, such as classifications, descriptions, titles, and governance roles, are also removed from the data objects. ## Change Management through LMDF & APIs ### **Load Metadata from Files - Business Glossary** Load Metadata from Files is another essential feature in OvalEdge, allowing users to manually create and perform bulk updates on terms within any domain. This includes modifying term descriptions, associations with data objects, term relationships, and Glossary-Catalog Sync Options, such as applying masking, restriction, updating governance roles, and more. Users can achieve this by downloading a template, making the necessary updates, and then uploading it back into the application. The automated process ensures that the business glossary terms are updated with all the required changes. ### **APIs- Business Glossary** OvalEdge offers a set of API services for managing business glossary terms. Below are some of the business glossary API services provided by OvalEdge. * **POST API -** Allows adding new terms to the business glossary and associating terms with data objects. * **GET API -** To retrieve and view term or domain details and associated object details, enabling access to critical information for better decision-making and understanding. * **DELETE API -** To delete terms or remove data objects associated with a term. *** Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA, USA. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.2/business-glossary/change-management-on-terms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.