> 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/advanced-tools/temp-lineage-correction/operations.md).
# Operations
Upon accessing the "Temp Lineage Correction" page, users can perform various actions using the "Nine Dots" menu:
### Change Schema
Users can change the schema for temp lineage correction by clicking the "Change Schema" button on the Temp Lineage Correction page beside the nine dots menu.
### Choose Table To Merge
This option lets users select a temp table and then choose a table from the application to merge with it.
### Run Recommendations with Schema
When users select **Run Recommendations with Schema**, it **triggers** a job that identifies all schemas in the application and merges them with the existing temporary schemas.
### Run Recommendations with Table
When users select **Run Recommendations with Table**, it **triggers** a job that identifies all relevant tables in the application and merges them with the existing temporary tables.
***
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 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/advanced-tools/temp-lineage-correction/operations.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.