> 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/connectors/introduction-to-connectors/connector-features.md).

# Connector Features

Once the connection is established, the connector performs three key tasks:

* Crawling: Fetches metadata from the data source.
* Profiling: Analyzes the data to generate statistics and quality metrics.
* Lineage Building: Maps the data flow and transformations across systems.

Below is an example of crawling and profiling.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdtsvpd5LqwjJ6OzdsTXQ7qJS4IvmzYsUDn1KMVMEkC8YWkvn1-D8qiUhcRYhZ05zvnGzhoRLz3mXt4MLbN0WC364uWrWGCBox-vDKOdcaS6xZyuL47y2ovDrH9ZVhtJPBINr8m?key=kU5fqtI4eAzquyCyuBsp-g" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Crawling, Profiling, and Lineage building vary depending on the connector type.
{% endhint %}

### Connection, Crawling, Profiling & Lineage Workflow

1. **Set Up Connection**
   1. Users connect to the source system using supported protocols such as JDBC or REST APIs. The system establishes a connection to the data source.
2. **Metadata Crawl**
   1. The system fetches metadata from the connected source. It collects information such as tables, columns, reports, and file structures.
   2. Fetched metadata appears in the data catalog.
3. **Data Profiling (If Applicable)**
   1. The system builds statistics for data objects.
   2. Profiled data appears in the data catalog to support analysis.
4. **Build Lineage (If Applicable)**
   1. The system builds lineage to show the flow of data across systems.
   2. Lineage helps users trace the origin of data, understand transformations, and analyze downstream impact.

<figure><img src="/files/Y2zH5RoVXT6FHJ1iyGCu" alt=""><figcaption></figcaption></figure>

***

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/connectors/introduction-to-connectors/connector-features.md?ask=<question>&goal=<endgoal>
```

`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.