> For the complete documentation index, see [llms.txt](https://doc.dastra.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.dastra.eu/en/features/mapping/repositories/data-glossary.md).

# Data glossary

Maintain the list of data fields, the most atomic level of the data mapping, with their category and sensitivity level.

A data field is a piece of information, such as a name, an email address or a health record number. It is the most atomic level of the mapping: [datasets](https://doc.dastra.eu/en/features/mapping/repositories/datasets.md) are made of data fields.

List each field once in this glossary, so that every dataset describes the same data in the same way.

## Add a data field

Open **Data inventory** > **Repositories** > **Data glossary**. You can:

* click **Create a data field** to open an empty form;
* click the arrow next to **Create a data field**, then **Create from library...** to copy fields of the library;
* import fields from a file: arrow next to **Create a data field**, then **Import**. See [Import your data (Excel, Csv)](https://doc.dastra.eu/en/features/general/import.md).

You can also create a field directly from the **Data fields** section of a dataset.

## Complete the data field form

| Field                                                                                     | Content                                                                                                                                                                                                                                                   |
| ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name**                                                                                  | The name of the field, required.                                                                                                                                                                                                                          |
| **Internal reference**                                                                    | Your reference.                                                                                                                                                                                                                                           |
| **Category of data**                                                                      | The category of personal data the field belongs to.                                                                                                                                                                                                       |
| **Sentivity level**                                                                       | **Standard** (name, first name, phone number), **Data of a highly personal nature** (financial data, location, communications) or **Special categories (sensitive)** (racial or ethnic origin, political opinions, religion, health, sexual orientation). |
| **Lawful basis for collection**, **Justification for collecting sensitive personal data** | Displayed for the **Special categories (sensitive)** level only: the lawful basis chosen in the list, and your justification.                                                                                                                             |
| **Description of the data**, **Technical description**                                    | A free description, and the technical definition of the field.                                                                                                                                                                                            |
| **Data type**                                                                             | The generic type of the data.                                                                                                                                                                                                                             |

The [custom fields](https://doc.dastra.eu/en/features/general/custom-fields.md) defined for data fields are added to the form. The toolbar gives access to the comments and tasks linked to the field, to the activity history and, when workflow steps are defined, to the workflow step. The button with the database icon lists the datasets that contain the field.

The actions menu of the form offers **Merge** and **Delete**.

## Find data fields in the list

The filters are **Category of data** and **Data types**. The **Datasets** column, hidden by default in **Customize columns**, can be filtered with **Is empty** or **Is not empty**: use it to find the fields that belong to no dataset.

From a selection, you can **Switch workflow stage**, **Edit fields...**, **Merge**, **Export** and **Delete**. **Data quality tool**, in the menu of **Create a data field**, detects duplicates. See [Merging elements](https://doc.dastra.eu/en/features/general/merge.md).

## Where data fields are used

Data fields reach your processing activities through datasets. See [Datasets and retention](https://doc.dastra.eu/en/features/ropa/activity/datasets.md), where you can also add the fields of a dataset to a processing activity.

{% hint style="warning" %}
Deleting a data field permanently removes all its references to datasets. The linked conversations are deleted.
{% endhint %}


---

# 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://doc.dastra.eu/en/features/mapping/repositories/data-glossary.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.
