> 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/advanced-tools/temp-lineage-correction.md).
# Temp Lineage Correction
The connectors offer users two ways to build data lineage: using the "Build Auto Lineage" feature for automatic lineage creation or manually creating lineage from scripts. Associated objects play a crucial role in showing how data moves. When the original associated objects are unavailable, the application creates temporary associations called temporary tables to assist in creating lineage. Once the original schemas and tables are found, these temporary objects are replaced with the original ones. This replacement and merging of lineage happens seamlessly through the "Temp Lineage Correction" module, ensuring an accurate representation of the data's path.
### **What are Temp Objects:**
Temp objects act as temporary placeholders in the lineage. If the original table is not crawled, they are automatically created while parsing the source code.
### **Navigating to Temp Lineage Correction:**
To access the "**Temp Lineage Correction**" module, go to "**Advanced Tools**" and click on "**Temp Lineage Correction"**.
### Choose Temp Schema
The 'Choose Temp Schema' option appears by default when the Temp Lineage Correction module is opened. This opens a pop-up window where users can select the temporary schema from a drop-down menu listing all available temporary schemas in the application.
***
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/advanced-tools/temp-lineage-correction.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.