> 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/write-metadata/options-write-metadata-step/metadata-tab-write-metadata-step.md).

# Metadata tab

In this tab, specify any of the existing metadata tags you want to associate with the data resources identified in the **Input** tab. This PDI option matches the **Add a tag** feature for a data resource in the Data Catalog.

For example, if your transformation uses the Catalog Input step to create or update a data resource in Data Catalog, you could use this step to inject resource IDs into your transformation and add tags to those data resources.

![Metadata tab](https://3411831820-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAYwCj9fPr1B2pjC11IOQ%2Fuploads%2Fgit-blob-39cb54ddb2e70b863acc47be5dd88b0462162efe%2Fpdi_write_catalog_metadata_step_metadata_tab_populated_02.png?alt=media)

Use the drop-down menu to select a tag, or several tags, from the existing tags that are available through your Data Catalog connection. Enter a description for this tag or group of tags in the **Description** field, or edit the existing description.

| Field           | Description                                                                                            |
| --------------- | ------------------------------------------------------------------------------------------------------ |
| **Description** | Type or revise the description for the tag or group of tags you selected with the **Tags** option.     |
| **Tags**        | Select any existing tags you want associated with, and assigned to, the resource ID and click **ADD**. |

**Note:** If missing or incomplete 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/write-metadata/options-write-metadata-step/metadata-tab-write-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.