> 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/datasets.md).

# Datasets

Group data fields into coherent sets, with the retention rules that apply to their life cycle, and reuse them in your assets and processing activities.

A dataset groups data fields, sensitive or not, with the retention rules that apply to their life cycle. Paper pay slips or the customer records of a CRM are examples of datasets.

Define a dataset once in this repository, then reuse it in the assets that hold it and in your processing activities. This keeps the inventory of your data consistent and lets you find, for one asset, everything it contains.

## Add a dataset

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

* click **New dataset** to open the **Dataset creation wizard**, then choose **Empty dataset**, **AI Generated** (this option depends on the features enabled for your organization) or **Step by step guide**, which asks you to select the data fields of the dataset first. **From filerskeepers** appears when the [Filerskeepers](https://doc.dastra.eu/en/features/integrations/filerskeepers.md) integration is enabled;
* click the AI button to the left of **New dataset** to describe the dataset and let the assistant draft it;
* click the arrow next to **New dataset**, then **Create from library...** to copy a dataset of the library;
* import datasets, with their data fields, from a file: arrow next to **New dataset**, then **Import**. See [Import your data (Excel, Csv)](https://doc.dastra.eu/en/features/general/import.md).

<figure><img src="https://2697025545-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LvBxs22wUMicv9uWp6C-1972196547%2Fuploads%2Fgit-blob-f23156c117d1d2547d0077c5d29432d1158e37c9%2Frepositories-datasets-1.png?alt=media" alt="List of datasets with the Filters panel open"><figcaption><p>The list of datasets</p></figcaption></figure>

## Complete the dataset form

| Section                        | Field                                                            | Content                                                                                                                                                                                                         |
| ------------------------------ | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **General information**        | **Dataset name**                                                 | The name of the dataset, required.                                                                                                                                                                              |
|                                | **Linked asset**                                                 | The asset that holds the dataset. You can create an asset from this field. A dataset without an asset is an orphan.                                                                                             |
|                                | **Related subject categories**                                   | The [categories of data subjects](https://doc.dastra.eu/en/features/mapping/repositories/subject-categories.md) the data relates to. You can create a category from this field.                                 |
|                                | **Internal reference**, **Summary**                              | Your reference and a free description.                                                                                                                                                                          |
| **Data fields**                |                                                                  | The data fields of the dataset. Select a field in the list or create one, then fill in the **Remarks** and tick **Required** where the field is mandatory. Each field shows its sensitivity level and category. |
| **Default retention policies** | **Active database retention**, **Archived database retention**   | For each: the **Retention period**, the policy (**Describe the policy (duration, conditions...)**) and its **Justification**.                                                                                   |
|                                | **Data destruction policy**                                      | The description of the purge policy and its **Justification**.                                                                                                                                                  |
| **Data source origin**         | **Data source origin**, **Description of the collection source** | Where the data is collected from.                                                                                                                                                                               |

The [custom fields](https://doc.dastra.eu/en/features/general/custom-fields.md) defined for datasets and the [tags](https://doc.dastra.eu/en/features/general/tags.md) are added to the form.

The toolbar of the form gives access to the comments, questionnaires, tasks and AI systems linked to the dataset, depending on your permissions and the enabled features. It also contains:

* **Linked elements**: the [generic relationships](https://doc.dastra.eu/en/features/mapping/relationships.md) of the dataset;
* **Link a data processing**: the processing activities that use the dataset, and the link to add more.

The actions menu of the form offers **Create a copy**, **Merge** and **Delete**.

## Find datasets in the list

The filters of the list include **Assets**, **Types**, **Filter by tags**, **Cat. of data subject**, **Data cat.** and **Special categories of pers. data (sensitive)**. Turn on **View orphan** to list the datasets attached to no asset, then attach them from the **Linked asset** field.

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

## Where datasets are used

* In a processing activity, you add the datasets that the processing handles, and you can customize their retention period for this activity only. See [Datasets and retention](https://doc.dastra.eu/en/features/ropa/activity/datasets.md).
* In an asset, the **Datasets** section lists the datasets it holds. See [Assets](https://doc.dastra.eu/en/features/mapping/repositories/assets.md).
* In categories of data subjects: the form of a category lists its datasets. See [Categories of data subjects](https://doc.dastra.eu/en/features/mapping/repositories/subject-categories.md).
* In AI systems, through the **AI systems** tab of the dataset.

{% hint style="warning" %}
Deleting a dataset removes its links to data fields, attachments, processing activities and assets. The conversations and the processing of related requests to exercise rights are permanently deleted. Questionnaires and related tasks are kept.
{% 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/datasets.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.
