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

# Input tab

Use the **Input** tab to describe where a data resource ID (Data Catalog’s identification key) originates as input from within your transformation.

If your transformation only needs a specific data resource, type the ID into the **Resource ID** field. The Write Metadata step then adds new tags only to that specific data resource.

![Input tab](/files/f3YtlOkTrUbZaM7E5AdQ)

If the transformation is designed to work with multiple resource IDs, they can be supplied as input from a previous step in the transformation, for example, with the Read metadata step. Specify one of the following options.

| Resource ID option                           | Description                                                                                                                         |
| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Accept resource ids from previous step**   | Select this option if the exact resource IDs are the incoming data from a previous step in the transformation.                      |
| **Pass through fields from previous step**   | Select this option if the resource IDs are located in a specific field that is incoming from a previous step in the transformation. |
| **Field in the input to use as resource id** | If you select **Pass through fields from previous step**, enter the name of the field that contains the resource IDs.               |


---

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