> 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/data-catalog/data-catalog-overview.md).

# Data Catalog Overview

A **Data Catalog** is a centralized inventory that helps organize, manage, and search metadata (data about data) across an organization’s data ecosystem. It enables teams to discover, understand, and govern their data assets more effectively.

OvalEdge provides a complete data governance solution with an advanced Data Catalog and self-service tools. This enables monitoring of data behavior for analytics, understanding its origin, and identifying its relationships with other data.

The **Data Catalog** connects to various source systems, such as transactional databases, NoSQL databases, and data warehouses. It crawls all the organizations’ metadata, consolidating them into a single reference source. The established connection remains continuously active to fetch new updates on metadata and data whenever needed.

It catalogs metadata, which is data about data (name, type, length, and description). The cataloged metadata can be curated (edited, added, and managed) to extract maximum value from the data and consume relevant information quickly and efficiently, saving valuable time and resources.

### Build Data Catalog&#x20;

The Data Catalog connects with various data sources using connectors to crawl and profile the metadata details of the remote data sources into the Data Catalog.&#x20;

* **Connector Integration and Setup:** It enables seamless integration with a wide range of connectors, allowing businesses to connect many data sources and parse metadata from various data objects such as Tables, Files, Reports, and APIs.
* **Automated Crawling of Data Objects:** The Connectors automate data crawling to retrieve metadata (object name, source description) from source systems, ensuring systematic collection and storage of relevant data in the Data Catalog.
* **Comprehensive Data Profiling Capabilities:** It offers data profiling capabilities, enabling a thorough understanding of the attributes and quality of the data objects. This process allows proper decision-making and data-centric analytics by offering insights like Row Count, Column Count, Density, Null Density, and other relevant information.

The image below shows the Administration Connectors page's customizable data crawling and profiling settings. These settings allow businesses to set up the process based on specific requirements and preferences.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXe3nJTN-oOmPOrAqGtSGxiqNY0KQGjLbuFXhVmDvYtMjCLmVuBZip2zdyOgebmzIad5-A05JZauiAw4PnW8BZbU49OuJUwquhwbq0b2GqGad2ikeC8-9J1o3Q62hRLoAR8vWA2A?key=eh27jyUTYPq1_oVnDl43yA" 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 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/data-catalog/data-catalog-overview.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.
