> 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.3/advanced-tools/data-and-metadata-changes.md).

# Data & Metadata Changes

OvalEdge provides a comprehensive view of how the data ecosystem evolves, including data and metadata changes. This document explains the functionalities within the Data & Metadata Changes section, empowering users to understand these transformations effectively.

Here's a quick overview of what users will find:

* **Track Data Changes**\
  The Data Changes section shows all tables and their columns with recent modifications. This allows users to see how data statistics and summaries have changed over time, ensuring data integrity in OvalEdge.
* **Track Metadata Changes** \
  The Metadata Changes track updates to tables, columns, codes, reports, APIs, and their attributes. This allows users to see changes and understand how their data landscape evolves. This transparency improves data management within OvalEdge.
* **Search for Data & Metadata Changes** \
  OvalEdge makes it easy for users to find what they're looking for in the Data & Metadata Changes view.

**User-Friendly List View:**

* **Filters:** Users can narrow down results by specific criteria using predefined filters.
* **Search Bar:** Users can find data objects using keywords.
* **Sort:** Users can organize data by clicking column headers (ascending/descending).


---

# 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/release8.3/advanced-tools/data-and-metadata-changes.md?ask=<question>&goal=<user_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.