Norwegian version of this page

Storage

Before data collection, you need to clarify how the data will be stored. This information should also be included in the informational letter/consent form to participants. How the data is stored depends on how the data is classified. More information can be found here: Classification of data and information. If you are unsure, always choose the stricter level of the two.

Once you know the color code of the data, you need to find suitable storage solutions. You can find this information here: Data Storage guide - University of Oslo (uio.no), or by reading further. The storage solutions we will go through are: TSD (red and black data), EduCloud (up to red data), Storage Hotel (up to red data), UiO OneDrive (up to yellow data), and Nettskjema (up to yellow data).

At PSI, TSD is used as the default solution for red and black data, but it is worth noting that many find the platform cumbersome to work with and that there are other approved platforms. Feel free to consult your supervisor for recommendations on storage platforms.

Additional Information on Qualitative Data Storage

When dealing with qualitative interview data, it is common to assume that the data is classified as red. If you are conducting interviews, you can collect the data using an encrypted voice recorder (recommended: Nettskjema mobile app dictaphone) and store the data in a location approved for red data storage (e.g., TSD, storage hotel, encrypted disk, or EduCloud).

After the data collection, you will know the content and thus understand the type of data you possess. If it turns out that the data you have falls under the yellow category rather than red, it can be moved to another storage location approved for yellow data, such as UiO OneDrive. The advantage of this is that it may be easier to process the data there compared to platforms with higher security levels like TSD (the need for relocation will be lower when using EduCloud, as it is more user-friendly to work in). You can also move the data after transcription, and all data falling under specific categories has been removed. As long as it contains data under the red category, it MUST be kept on a platform approved for red data storage.

One way to avoid storing red data in TSD is to conduct a highly structured interview (to avoid the collection of red data). In this case, you should inform the participant not to discuss specific topics that would classify as red and actively steer the participants away from sensitive subjects. However, be aware that this approach could potentially limit the research in an undesirable way.

 

Link Key for Data Storage

A linking key (also known as a code key) is a document that enables the identification of study participants through de-identified data.

For example, in an interview study with 10 participants, you can assign each participant a number between 1 and 10 to de-identify/anonymize the data. This numbering system can be used to identify who said what without using their real names. At the same time, you have another document that shows which number corresponds to each participant (with real names), for example, "Participant 1 = John Doe, Participant 2 = Jane Smith". This document represents your linking key. By having access to both of these documents, one can easily identify the individuals who participated in the study.

It is sufficient to store the linking key in a separate folder in TSD (not in the same folder as the interviews and transcriptions), since TSD is approved for storing up to black data. If you desire stricter security, you can save the linking key in a password-protected Word document in a separate folder in TSD. Alternatively, you can use an encrypted external memory stick to store the linking key.

Another approach is not to create a linking key, but let the participants be their own linking key: each participant is assigned a unique code (number, pseudonym, letter, etc.). It is important that participants remember this code. Consent must be obtained without the participant sharing identifying information (e.g., verbal consent). No linking key is created, and contact information is stored in a separate folder in TSD. All data is linked to the participants' codes, but the contact information is not. If participants want access to their own information, they must provide their code since you have not stored a linking key. This can be particularly advantageous in more sensitive projects where participants remain anonymous throughout the process, such as when interviews are conducted anonymously online.

 

Published May 22, 2024 2:11 PM - Last modified June 13, 2024 11:53 AM