> For the complete documentation index, see [llms.txt](https://docs.rhinofcp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rhinofcp.com/getting-started/quick-start-guide/extra-data-in-the-fcp.md).

# Extra Data in the FCP

***

## Overview

The Rhino FCP supports **Extra Data** fields for the following resources:

* **Data Schemas**
* **Datasets**
* **Code Objects**

The **Extra Data** field allows you to associate custom metadata with these resources in the form of a **JSON object**. This provides a flexible way to store additional information that may not be captured by the resource's standard fields.

***

## Where to Find Extra Data

When creating a supported resource, the **Extra Data** field can typically be found:

* At the bottom of the resource's **Create** modal, or
* Under the **Additional Parameters** section of the **Create** modal.

<figure><img src="https://2949362692-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FydySyCBmy6F7NnGn4bPa%2Fuploads%2Fj3xMU4TbRXIMNm9PRRzT%2Fimage.png?alt=media&amp;token=1f5b6ba6-fb2c-4abf-9c5e-0a78bdf5d94a" alt=""><figcaption></figcaption></figure>

It is not required to populate this section and is empty by default: `{}`

***

## How to Use Extra Data

Extra Data accepts a JSON object containing custom key-value pairs. You can use it to store supplementary metadata relevant to a resource, such as:

* **Descriptions or annotations:** Additional context about a Dataset, Data Schema, or Code Object.
* **Source information:** Details about data provenance, origin, or versioning.
* **Custom identifiers:** Internal reference IDs or labels used by your organization.
* **Organizational metadata:** Project-specific tags, classifications, or other attributes.

For example, a Dataset's Extra Data might look like this:

```json
{
  "source_system": "Hospital EHR",
  "data_version": "1.2",
  "department": "Radiology",
  "notes": "De-identified imaging metadata"
}
```

Because Extra Data is stored as JSON, it can accommodate different types of metadata depending on your use case. Ensure that the content follows valid JSON syntax.

***

## Extra Data vs. Runtime Files

**Extra Data is intended for storing resource metadata, not for passing inputs to Code Object executions.**

Currently, Rhino FCP does not support directly passing values from a resource's Extra Data field into a Code Object at runtime.

If you need to provide additional files or configuration information to a Code Object during execution, use [**Runtime Files**](https://docs.rhinofcp.com/creating-and-running-code-objects/using-external-files-at-runtime.md) instead.

| Feature                                          | Extra Data                                     | Runtime Files                                        |
| ------------------------------------------------ | ---------------------------------------------- | ---------------------------------------------------- |
| Primary purpose                                  | Store custom resource metadata                 | Provide files to Code Object executions              |
| Associated with                                  | Data Schemas, Datasets, Code Objects           | Code Object runs                                     |
| Format                                           | JSON object                                    | Supported file formats                               |
| Accessible directly during Code Object execution | No                                             | Yes, when configured as runtime inputs               |
| Example use cases                                | Source identifiers, annotations, custom labels | Configuration files, lookup tables, auxiliary inputs |

**Recommendation:** Use Extra Data to document or organize information about a resource. Use Runtime Files when a Code Object needs to consume additional information during execution.


---

# 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.rhinofcp.com/getting-started/quick-start-guide/extra-data-in-the-fcp.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.
