> For the complete documentation index, see [llms.txt](https://documentation.immuta.com/2024.2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.immuta.com/2024.2/data-and-integrations/registering-metadata/data-source-settings/how-to-guides/manage-dictionary.md).

# Manage Data Dictionary Descriptions

The data dictionary provides information about the columns within the data source, including column names and value types.

As a data owner, you can manage data dictionary [descriptions](#manage-data-dictionary-descriptions) and column tags. For other guides related to the data dictionary, see the [Related guides section](#related-guides).

## Manage data dictionary descriptions

1. Navigate to the **Data Dictionary** tab.
2. To add or edit column descriptions, click the **menu** icon in the **Actions** column next to the entry you want to change and select **Edit**.
3. Complete the fields in the form that appears, and then click **Save**.

## Related guides

### Reference guide

For information about the data dictionary, see the [Data sources in Immuta overview](/2024.2/data-and-integrations/registering-metadata/data-source-overview.md#data-dictionary).

### How-to guide

In addition to managing data dictionary descriptions as outlined above, data owners or experts can also manage [column tags](/2024.2/data-and-integrations/tags/how-to-guides/managing-tags.md).


---

# 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://documentation.immuta.com/2024.2/data-and-integrations/registering-metadata/data-source-settings/how-to-guides/manage-dictionary.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.