> 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/pba-metadata-editor/readme.md).

# Pentaho Metadata Editor 11.0

Pentaho Metadata Editor lets you build metadata models and domains. Pentaho includes sample data in the download so you can try Metadata Editor before you import your own data.

To use Pentaho Metadata Editor effectively, you need database administration (DBA) skills. You should be able to do the following: import tables, create relationships between tables, define aggregations, add categories, and assign security. You should also have extensive knowledge of your database and understand what data your business users need. These skills help you map a business model (logical model) to a complex relational database so users can create reports without DBA assistance.

## Get started with Pentaho Metadata Editor

To get started with Metadata Editor, see the following topics:

* [Tour of Pentaho Metadata Editor](https://docs.pentaho.com/pba-metadata-editor/readme/tour-of-pentaho-metadata-editor.md)
* [A conceptual overview of relational data modeling](https://docs.pentaho.com/pba-metadata-editor/readme/a-conceptual-overview-of-relational-data-modeling-get-started-with-pentaho-metadata-editor.md)
* [Importing and exporting domains](https://docs.pentaho.com/pba-metadata-editor/readme/importing-and-exporting-domains.md)


---

# 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/pba-metadata-editor/readme.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.
