Hi, In the current version, in a data processing activity, you select a dataset, and the data fields from the dataset are automatically taken over. It would be handy here to have the possibility to deviate from the general rule in the processing activity, like it is possible for the retention period, and allow to change some data fields on the processing activity level, without changing the default from the configuration. F.e. I create a dataset called Personal Identifiers in the carthographie. I add name, adress, telephone number In a processing activity, I select the dataset Personal Identifiers. The fields name, adress and telephone number are automatically loaded In the processing activity, I delete telephone number from the dataset. In the carthographie however, my dataset Personal Identifiers remains unchanged Most of the time, the datafields in the dataset are identical in the processing activities, but sometimes there is some small difference on the processing activity level, now if I want the datafields correct I have to make a duplicate dataset with the minor changes, making that over time there will be too many datasets making it hard to have a clear overview

Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Data fields in datasets

julieDF

Hi,

In the current version, in a data processing activity, you select a dataset, and the data fields from the dataset are automatically taken over. It would be handy here to have the possibility to deviate from the general rule in the processing activity, like it is possible for the retention period, and allow to change some data fields on the processing activity level, without changing the default from the configuration.

F.e.

I create a dataset called Personal Identifiers in the carthographie. I add name, adress, telephone number
In a processing activity, I select the dataset Personal Identifiers. The fields name, adress and telephone number are automatically loaded
In the processing activity, I delete telephone number from the dataset. In the carthographie however, my dataset Personal Identifiers remains unchanged

Most of the time, the datafields in the dataset are identical in the processing activities, but sometimes there is some small difference on the processing activity level, now if I want the datafields correct I have to make a duplicate dataset with the minor changes, making that over time there will be too many datasets making it hard to have a clear overview

Jerome_Dastra

julieDF

Hello Julie,

Thank you for your request !

It will depend on how you use the datasets.

Indeed, datasets can be used in several ways:

1: by associating a dataset with a single asset. In this case, the dataset corresponds to the data of the asset and is not generic

2: by associating a dataset with data processing. This dataset can be specific to the data processing and is not reused in another data processing

3: by associating generic datasets to the data processing. In this case, the dataset can be reused in several data processing.

You are in the 3rd case. In this case, I recommend the following procedure:

- Open the dataset processing page

- Open a new tab on the datasets page in the cartography

- Select the dataset in the dataprocessing

- If the dataset has to be modified, you have to create another one: go to the other tab and duplicate the generic dataset by removing or adding the desired fields

- For more clarity, I recommend to use a tag for these datasets (this will allow you to distinguish them easily in the dataset selector). For example: a "generic" tag and a tag for the added or removed data

We don't have any other solution than this one for the moment. The long-term objective may be to limit the use of generic datasets and to move towards a more precise mapping either via data processing (case 2) or via assets (case 1).

Furthermore, you can also remain even more generic by not specifying the data associated with the dataset but by naming the dataset as a category of data (which is also valid in the sense of the RGPD for example)

Depending on the processing, you may have different approaches, depending on the sensitivity they present with regard to the rights and freedoms of the data subjects.

I hope this provides an answer to your question.