> 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/solution-analyst-path-sandbox/solution-analyst/metadata-editor.md).

# Metadata Editor

The third Solution Analyst course: Metadata Editor. 13 lessons in 6 modules: build, enrich, secure and publish the domains Interactive Reports use, ending in the Trailhead capstone.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** Built from `bi-developer-me-associate` 0.1.10 in Pentaho Content Manager. Module and lesson names, the reading-or-workshop kinds and the times come straight from each lab's manifest. Items marked REPLACE-ME need an owner's confirmation.
{% endhint %}

The third of the five courses on the Solution Analyst path. Build the business-friendly semantic models that Interactive Reports query: the physical layer, business models, relationships and business views, then properties, reusable concepts and row-level security, published as XMI domains for ad-hoc reporting. The capstone models a company's sales database from an empty domain to a published, secured data source.

{% columns %}
{% column %}

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i><br><strong>13 lessons</strong><br><em>across 6 modules</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-flask" style="color:orange;">:flask:</i><br><strong>7 workshops</strong><br><em>hands-on labs</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-clock" style="color:cyan;">:clock:</i><br><strong>~9h 15m</strong><br><em>two days, or a few evenings</em></p>
{% endcolumn %}
{% endcolumns %}

{% hint style="success" icon="cloud-arrow-up" %}
Every workshop is hands-on and runs on Pentaho's hosting platform. The Lab Guide is embedded in each lab and loads automatically when you open it — nothing to install.
{% endhint %}

***

<h3 align="center">Before you start</h3>

{% columns %}
{% column %}
{% hint style="success" icon="circle-check" %}
**What you'll need**

Business Analyst, or day-to-day use of Interactive Reports. The course models the SteelWheels SampleData schema and a MySQL sales database, so comfort with relational tables, keys and joins will make the labs quicker — but every step is shown.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="tag" %}
**Built against**

Pentaho Enterprise Edition **11.0.0.0-232**, the build every course on the Academy runs — the Pentaho Server and the Metadata Editor design tool that ships with it. The hosted labs run this exact release, so every screen, menu and dialog matches the guide step for step.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

{% hint style="info" icon="sitemap" %}

#### What you'll build

The prebuilt SteelWheels domain explored, then the OrdersME star-schema domain built from scratch and queried with the Query Builder, enriched with inherited properties on the OrderStarCustomer domain and reusable concepts, and secured with row-level constraints. The capstone is Trailhead Outfitters: their MySQL sales database modelled from an empty domain to a published, secured data source, proven with three users in Interactive Reports.
{% endhint %}

***

<h3 align="center">Skills you'll gain</h3>

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><i class="fa-database" style="color:blue;">:database:</i> <strong>Domains and the physical layer</strong></td><td>Domains · connections · the physical layer · the SteelWheels domain</td></tr><tr><td><i class="fa-sitemap" style="color:blue;">:sitemap:</i> <strong>Business models</strong></td><td>Business tables, relationships and business views · the OrdersME star schema · the Query Builder</td></tr><tr><td><i class="fa-sliders" style="color:blue;">:sliders:</i> <strong>Properties</strong></td><td>Friendly names, formats and aggregation · inheritance from physical to business to view</td></tr><tr><td><i class="fa-tags" style="color:blue;">:tags:</i> <strong>Concepts</strong></td><td>Reusable Number, Currency, ID, Hidden and Date concepts in the Concept Editor</td></tr><tr><td><i class="fa-shield-halved" style="color:blue;">:shield-halved:</i> <strong>Security</strong></td><td>Model and column security · row-level data constraints · different rows for different roles</td></tr><tr><td><i class="fa-trophy" style="color:blue;">:trophy:</i> <strong>Capstone — Trailhead Outfitters</strong></td><td>An empty domain to a published, secured data source · proven with three users in Interactive Reports</td></tr></tbody></table>

***

<h3 align="center">Course outline</h3>

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i> reading · <i class="fa-flask" style="color:orange;">:flask:</i> hands-on workshop</p>

{% hint style="info" icon="circle-info" %}
Full lessons unlock once you're enrolled — this is the outline only. Times are the lab guides' own estimates.
{% endhint %}

<table data-search="false"><thead><tr><th width="382">Module</th><th width="115" align="center">Reading</th><th width="132" align="center">Workshops</th><th width="100" align="right">Time</th></tr></thead><tbody><tr><td>Getting Started</td><td align="center">2</td><td align="center">—</td><td align="right">~35m</td></tr><tr><td>Domains &#x26; Models</td><td align="center">1</td><td align="center">3</td><td align="right">~2h 50m</td></tr><tr><td>Properties</td><td align="center">1</td><td align="center">1</td><td align="right">~55m</td></tr><tr><td>Concepts</td><td align="center">1</td><td align="center">1</td><td align="right">~1h 20m</td></tr><tr><td>Security &#x26; Data Access</td><td align="center">1</td><td align="center">1</td><td align="right">~1h 35m</td></tr><tr><td>Capstone Project</td><td align="center">—</td><td align="center">1</td><td align="right">~2h</td></tr><tr><td><strong>Total</strong></td><td align="center"><strong>6</strong></td><td align="center"><strong>7</strong></td><td align="right"><strong>~9h 15m</strong></td></tr></tbody></table>

{% stepper %}
{% step %}

### <i class="fa-rocket" style="color:blue;">:rocket:</i> Getting Started

`2 readings · ~35m`

Meet Pentaho Metadata Editor (PME) and the metadata domain — the physical layer and business model layer that turn raw database tables into a business-friendly semantic layer for ad-hoc reporting.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FHoWKhr5Im3161tH4tZAL%2Fme-lab-setup.svg?alt=media" alt="Metadata Editor reads tables and columns from the SampleData HSQLDB database on port 9001 through its hsqldb:sampledata connection and publishes domains to the metadata engine on the server; Interactive Reports sends each query to the engine, which sends SQL to SampleData; the server keeps its repository in PostgreSQL on port 5432, and MySQL on port 3306 holds the capstone&#x27;s trailhead database"><figcaption><p>Metadata Editor, the Pentaho Server and the sample data</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Before You Start</td><td>~25m</td></tr><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Components</td><td>~10m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-sitemap" style="color:blue;">:sitemap:</i> Domains & Models

`1 reading · 3 workshops · ~2h 50m`

The anatomy of a metadata domain, then three guided builds against the SteelWheels SampleData: explore the prebuilt SteelWheels domain, build the OrdersME star-schema domain from scratch, and assemble queries with the Query Builder.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FwdL6W6BTzirx5xBkco6w%2Fdomain-layers.svg?alt=media" alt="A diagram of the three layers: Table1 and CUST_TBL in the Physical Layer map to Business Table1 and Customers in the Abstract Business Layer, which feed Category1, Category2, Customers East and Customers West in the Business View"><figcaption><p>The three layers of a metadata domain</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FoUASTLwZV0ViwvipMygW%2Fdomain-build-stages.svg?alt=media" alt="The six stages of building a domain, numbered in two rows: 1 connect to a data source, 2 import physical tables and columns, 3 define the business model, then down to 4 define relationships, 5 build business views, 6 publish to the Pentaho Server"><figcaption><p>The stages of building a domain</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FUnQXhTiKxEJl0LsAdmiI%2Fmql-to-sql.svg?alt=media" alt="From query to SQL: Product Name and Order Number from two categories meet the N:1 inner relationship on PRODUCTCODE and become a WHERE condition; Price Sold meets its Default Aggregation Sum and becomes SUM, with GROUP BY the other columns; Total&#x27;s formula becomes SUM(ORDERFACT.QUANTITYORDERED * ORDERFACT.PRICEEACH); the user&#x27;s role&#x27;s Data Constraint entry becomes a WHERE filter"><figcaption><p>What the engine writes for each part of a query</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Domains &#x26; Models</td><td>~20m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>SteelWheels</td><td>~45m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>OrdersME</td><td>~1h 30m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Query Builder</td><td>~15m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-sliders" style="color:blue;">:sliders:</i> Properties

`1 reading · 1 workshop · ~55m`

Enrich the business model: business tables, columns, and relationships, plus the metadata properties (friendly names, formats, aggregation) that inherit from physical → business → view. Built on the OrderStarCustomer domain.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FKBfoLwqekIymX5Ordaaw%2Frelationship-joins.svg?alt=media" alt="Relationship types and their joins: N:1, 1:N, 1:1 and N:N, with no 0 side, make an inner join written as a WHERE condition; 0:N and 0:1 a left outer join; N:0 and 1:0 a right outer join; 0:0 a full outer join. Below, a made-up example: fact rows 1, 2 and 3 with the keys A, B and C, joined to a dimension that holds A and B; the inner join drops row 3, and an outer join keeps it with no match"><figcaption><p>The join comes from the relationship type</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Properties</td><td>~10m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>OrderStarCustomer</td><td>~45m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-tags" style="color:blue;">:tags:</i> Concepts

`1 reading · 1 workshop · ~1h 20m`

Define reusable metadata Concepts (Number, Currency, ID, Hidden, Date) once in the Concept Editor and apply them across columns so formatting and behaviour stay consistent — then validate in an Interactive Report.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2Fax0nMKCxcblpLnLS65SG%2Fconcept-chain.svg?alt=media" alt="The concept tree: Base, with its font and Text Alignment Left, passes its properties to Number and Date; Number adds Text Alignment Right and the mask #,##0 and passes them to USCurrency and ID, which each override the mask; ID passes them to Hidden, which adds Hidden For the User?. A business column takes a property from its own override, then its concept chain, then its physical column"><figcaption><p>Five concepts below Base, and where a column's property comes from</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Concepts</td><td>~20m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Concept Editor</td><td>~1h</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-shield-halved" style="color:blue;">:shield-halved:</i> Security & Data Access

`1 reading · 1 workshop · ~1h 35m`

Lock the model down with metadata security and row-level data constraints, so different roles see different rows and columns from the same published domain.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FZxQA7I6WoetVi1LO4WKw%2Fsecurity-layers.svg?alt=media" alt="The three layers from Metadata Editor to the report: Metadata Security on the business model and on the Credit Limit column is checked on the server, so the model is offered to Power User and the column is left out of suzy&#x27;s field list; the role-based Data Constraint on the model becomes the SQL WHERE clause, with no admin bypass, so suzy gets EMEA only and a role with no entry gets no rows"><figcaption><p>Where each layer is set, and how the server enforces it</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Security &#x26; Data Access</td><td>~20m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Row-Level Security</td><td>~1h 15m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-trophy" style="color:blue;">:trophy:</i> Capstone Project

`1 workshop · ~2h`

Put it together end-to-end: model Trailhead Outfitters' MySQL sales database from an empty domain to a published, secured data source, and prove it with three users in Interactive Reports.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FZKNLc6dJBFg5bheRv1ML%2Fcapstone-trailhead.svg?alt=media" alt="The Trailhead domain: the business model Trailhead Sales on mysql:trailhead, with the categories Sales, Stores, Products, Customers and Calendar; the sales fact table joined N:1 to products, customers and calendar, and to stores on region_code and store_no; three calculated columns; admin sees every region with Email and Phone, suzy only WEST, pat only EAST, and tiffany no data source"><figcaption><p>What you build: the Trailhead domain, and who sees what</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Capstone: Trailhead Outfitters</td><td>~2h</td></tr></tbody></table>

</details>
{% endstep %}
{% endstepper %}

***

<h3 align="center">Exam &#x26; accreditation</h3>

{% columns %}
{% column %}
{% hint style="info" icon="clipboard-check" %}
**The course exam**

40 questions drawn at random from a pool of 46, covering the taught modules. The pass mark is 80%. It's open-book: browse any module or ask the AI assistant while you work.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="warning" icon="file-certificate" %}
**Course accreditation**

Finish the lessons and workshops, pass the exam and complete the capstone, and you'll automatically be able to download your course accreditation. It states your name, the course and the Pentaho version you studied against, and is valid for two years. The exam is self-paced and not proctored. REPLACE-ME — the course names the accreditation "Pentaho Metadata Editor"; confirm the name.

This course is the third step on the Certified Solution Analyst learning path: Business Analyst, then Schema Workbench, Metadata Editor, Report Designer and CTools, leading to the Certified Solution Analyst credential — which closes with a proctored exam delivered through Kryterion's Webassessor.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

<p align="center"><a href="https://academy.pentaho.com/solution-analyst-path-sandbox/solution-analyst.md" class="button secondary" data-icon="arrow-left">Back to the Solution Analyst path</a></p>


---

# 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/solution-analyst-path-sandbox/solution-analyst/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.
