... | ... | @@ -8,7 +8,7 @@ PEP allows for the storage and retrieval of tabular data. Conceptually, PEP prov |
|
|
| Eric | crown | DK3650519625773963 | 2013-11-19 | 122/62 | ... |
|
|
|
| ... | ... | ... | ... | ... | ... |
|
|
|
|
|
|
Each row represents a single entity or data subject. Data are stored in the same row if they are associated with the same subject. Data for different subjects should be stored in separate rows. Rows are denoted by means of one of [PEP's identifiers](Pseudonymization#identifiers-in-pep).
|
|
|
Each row represents a single entity or data subject. Data are stored in the same row if they are associated with the same subject. Data for different subjects should be stored in separate rows. Rows are denoted by means of one of [PEP's identifiers](Pseudonymization#identifiers-in-pep). A new row is created by storing data into a row with a previously unused [participant identifier](https://gitlab.pep.cs.ru.nl/pep-public/user-docs/-/wikis/Pseudonymization#participant-identifier).
|
|
|
|
|
|
Columns are used to split data into conceptual units. Different types of data or different measurements should be stored in different columns. Columns are referred to by name, and the name is determined when the column is created. Only members of the "Data Administrator" role can create columns and perform other [administrative tasks](Administration) on them.
|
|
|
|
... | ... | @@ -22,4 +22,13 @@ Access cannot be managed at the cell level: rows and columns are the smallest un |
|
|
|
|
|
After data has been stored into a PEP cell, downloaders can retrieve that data from there. When new data are stored into the same cell, new downloads will receive the updated version instead. But the old data are never discarded: PEP retains a complete record of all data that has ever been stored into the system. This allows PEP to reconstruct its data set as it was at any time in the past. Such "snapshots" are intended to be made accessible to users for download (although the functionality has not yet been created). This allows the exact same data to be retrieved multiple times, which is usable e.g. for scientific replication studies.
|
|
|
|
|
|
A similar policy applies to column management. When a Data Administrator removes a column, the data stored in that column is retained for future use. Therefore (once the feature is available) when users retrieve an older snapshot, they will also receive the data from the "removed" column. Data Administrators should be aware that, if they remove and then re-add a column with the same name, the newly created column will immediately contain the previously stored data. |
|
|
\ No newline at end of file |
|
|
A similar policy applies to column management. When a Data Administrator removes a column, the data stored in that column is retained for future use. Therefore (once the feature is available) when users retrieve an older snapshot, they will also receive the data from the "removed" column. Data Administrators should be aware that, if they remove and then re-add a column with the same name, the newly created column will immediately contain the previously stored data.
|
|
|
|
|
|
# Grouping
|
|
|
|
|
|
Members of the `Data Administrator` role can
|
|
|
|
|
|
- group columns into column groups, and
|
|
|
- group rows into participant groups.
|
|
|
|
|
|
Such groups serve as a basis for PEP's [data access management](Access-Management#data-access). |
|
|
\ No newline at end of file |