Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dcc:pdpsol:dataminimization [2026/02/24 09:46] – [Social media data] marlon | dcc:pdpsol:dataminimization [2026/03/03 14:18] (current) – text editing marlon | ||
|---|---|---|---|
| Line 18: | Line 18: | ||
| ==== Take into account the effort of research participation ==== | ==== Take into account the effort of research participation ==== | ||
| Although it is important to consider what personal data you need for your research, it is also important to be mindful of the effort and strain participation may place on data subjects. This means you should limit the collection of personal data to what you need for your research. However, you should also respect participants’ time and effort, and avoid designing studies that require participants to take part multiple times due to narrowly defined research questions. This is particularly important when working with vulnerable or hard-to-reach groups. In such cases, it is advisable to design studies that can address several relevant questions at once, thereby maximizing the value of participants’ contributions while minimizing their strain. | Although it is important to consider what personal data you need for your research, it is also important to be mindful of the effort and strain participation may place on data subjects. This means you should limit the collection of personal data to what you need for your research. However, you should also respect participants’ time and effort, and avoid designing studies that require participants to take part multiple times due to narrowly defined research questions. This is particularly important when working with vulnerable or hard-to-reach groups. In such cases, it is advisable to design studies that can address several relevant questions at once, thereby maximizing the value of participants’ contributions while minimizing their strain. | ||
| + | |||
| + | ==== Use consistent file naming and version control ==== | ||
| + | Organize your data consistently by using a file naming strategy and good folder structure. The [[https:// | ||
| + | * Do not include contact information or other personal data in the naming of your files. | ||
| + | * Incorporate version numbers in file names. By adding version numbers to your file names, it allows you to easily access and delete different versions of files, over time. | ||
| + | * It is good practice to create a version control table to keep track of different versions. The version control table can include information on different version numbers, authors, notes, and when the file was last updated. The table can also include a summary of the differences between the current version and previous versions. The version control table can be an independent text file, or it can be included at the top of your document, scripts, or other files. See Table 2 for an example of a version control table. ([[https:// | ||
| + | * Refer to the DCC website for more information on [[https:// | ||
| + | |||
| + | **Table 2: Example of a version control table ** | ||
| + | |||
| + | ---- | ||
| + | {{: | ||
| + | |||
| + | |||