> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/metadata-editor/overview/metadata-editor.md).

# Metadata Editor

Business Analytics ..

{% hint style="info" %}

#### Introduction

Pentaho Business Analytics, is an enterprise-level business intelligence and data analytics platform that helps organizations transform raw data into actionable insights. The platform combines data integration, OLAP services, reporting, dashboarding, and data mining capabilities in a unified suite. 

Notable for its open-source foundations and commercial enterprise edition, Pentaho enables organizations to perform complex data analysis, create interactive visualizations, and generate detailed reports through both traditional and modern big data sources. 

The platform supports various data sources and can integrate with popular databases and big data technologies like Hadoop, offering both on-premises and cloud deployment options.

By the end of the workshops, you will have a comprehensive understanding of:
{% endhint %}

<details>

<summary>Metadata Editor</summary>

The [Pentaho Metadata Editor](/metadata-editor/metadata-editor/components.md) is a graphical modeling tool that allows business analysts and IT developers to create and manage semantic business models on top of physical data sources. It abstracts the complexity of underlying database structures by creating a business-friendly metadata layer that defines relationships, calculations, and business terminology.&#x20;

Users can build logical models that map physical tables and columns to intuitive business concepts, establish joins between tables, create calculated fields, and define security rules - all without writing SQL. The resulting metadata models are then consumed by Pentaho reporting tools, enabling business users to create ad-hoc reports and analyses using familiar business terms rather than technical database nomenclature.&#x20;

This abstraction layer promotes consistency across reports, simplifies report development, and allows changes to underlying data structures without breaking existing reports, as long as the business layer remains consistent.

</details>

***

***


---

# 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://academy.pentaho.com/metadata-editor/overview/metadata-editor.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.