> 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-admin/pdc-10.2-admin/pdc-manage-rules-cp-ag/pdc-manage-metadata-rules-cp.md).

# Manage metadata rules

With Data Catalog metadata rules, you can assign business terms, tags, or properties to, or remove them from, already-scanned or ingested metadata. By doing so, you can streamline the process of searching for data while minimizing the potential for errors.

If your assigned role allows it, you see a Metadata Rules card on the Data Catalog Data Operations page. If you have a license for Pentaho Data Optimizer and your assigned role allows it, you can perform additional optimization actions within metadata rules.

Leveraging the Data Optimizer metadata rule engine capabilities, you can simplify data management by setting up rules to automate your data tiering, purging, and rehydration operations. You can use a rule definition on any data source type because rule definitions are data source agnostic, and you can use a single rule to both identify and move data.

The rules engine in Data Optimizer runs within a framework you can use to set the scope and action of rule-performed operations. Use the following workflow when creating metadata rules:

1. Create a rule definition. A rule definition sets the criteria and the action of the rule, which is translated and evaluated into a query for execution against the metadata of any scanned resource.
2. Create a metadata rule. A metadata rule can perform an array of tasks on a selected data source.

You can use the Manage Metadata Rules page to view, create, edit, and delete rule definitions and metadata rules.

**Note:** To perform rules-governed data operations, you may also need to perform some workflow tasks.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/pdc-admin/pdc-10.2-admin/pdc-manage-rules-cp-ag/pdc-manage-metadata-rules-cp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.