> 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/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/read-metadata-pdi-step/options-read-metadata-step.md).

# Options

Use the Read Metadata step to search for data resources and associated metadata from the search criteria you specify. You can search for Data Catalog data resources in multiple ways:

* **Specific Resources**

  Searches Data Catalog using the unique resource ID that is associated with a data resource.
* **Search Criteria**

  Narrows Data Catalog searches for specific data resources using criteria that you select from lists of the existing metadata available in your instance of Data Catalog.
* **Advanced Search**

  Creates a JSON script that finds the Data Catalog tags for specific data resources. For more information, see the [Lumada Data Catalog REST API](https://docs2019.waterlinedata.com/2019.3/apidocs/).

**Note:** In some cases, if missing or incomplete search data is returned, you may need to change the default limit for returned results. See [Data Catalog searches returning incomplete or missing data](/pdia-data-integration/9.3-data-integration/data-integration-issues/lumada-data-catalog-searches-returning-incomplete-or-missing-data.md) for information.


---

# 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/pdia-data-integration/9.3-data-integration/pdi-transformation-steps-reference-overview/read-metadata-pdi-step/options-read-metadata-step.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.