> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdc-use/book-abstract-for-use-pdc.md).

# Use Pentaho Data Catalog

Learn how to use Pentaho Data Catalog to ingest, profile, and curate structured and unstructured data through a combination of automation and machine learning. Whether you are a business user, data steward, developer, or administrator, this guide helps you get the most out of Data Catalog’s powerful capabilities to unlock the value of your data.

Pentaho Data Catalog enables you to ingest, profile, and curate structured and unstructured data at scale using automation and machine learning. It builds a secure and comprehensive inventory of your data assets, making them accessible, trustworthy, and aligned with your business needs.

With Data Catalog, you can:

* Discover and inventory data assets from diverse sources — databases, filesystems, cloud storage, and more.
* Automatically profile data quality and identify sensitive information.
* Organize data with business terms, policies, labels, and lineage to improve governance.
* Empower self-service data exploration with robust search, filtering, and visualization tools.
* Collaborate effectively across teams with role-based access control and audit trails.


---

# 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.pentaho.com/pdc-use/book-abstract-for-use-pdc.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.