> 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/release7.2/administration/audit-trails/reference-data-management.md).
# Reference Data Management
The "Reference Data Management" tab tracks changes to reference data units and their attributes within OvalEdge. This includes actions performed by:
* **Reference Data Admin (RD Admin):** Creates or deletes reference data units.
* **Steward of a Specific RD Unit:** Updates the unit's attributes.
The audit log captures the following details:
* **Reference Data Unit:** Name of the unit affected
* **Connector:** Connector associated with the reference data
* **Object Type:** Type of object linked to the unit (e.g., Table Column)
* **Attribute Name:** Name of the specific attribute (e.g., table column name)
* **Action:** ‘Add’, ‘Update’, or ‘Delete’ (for Stewards, ‘Updated’ refers to attribute changes)
* **Changes:**
* From: Previous value of the attribute or unit
* To: New value of the attribute or unit
* **Updated By:** The user who made the change
* **Updated On:** Timestamp of the action
**Sorting and Filtering:** Audit details can be sorted/filtered by RD Unit, Connector, Action, and Updated On.
Sample screenshot featuring Audit Trails > Governance Catalog > Referencing Data Management information.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ovaledge.com/release7.2/administration/audit-trails/reference-data-management.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
