... | ... | @@ -12,6 +12,8 @@ Each row represents a single entity or data subject. Data are stored in the same |
|
|
|
|
|
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.
|
|
|
|
|
|
A major difference with traditional data(base) storage systems is that no separate column should be used to store a [fixed row identifier](https://gitlab.pep.cs.ru.nl/pep-public/user-docs/-/wikis/Pseudonymization#traditional-fixed-identifiers). Rows are instead referred to by means of PEP's [polymorphic identifiers](https://gitlab.pep.cs.ru.nl/pep-public/user-docs/-/wikis/Pseudonymization#identifiers-in-pep).
|
|
|
|
|
|
The intersection of a row and column is called a cell. Cells do not have an identifier of their own. Instead, when storing or retrieving data, users can identify cells by specifying the associated column name and row identifier.
|
|
|
|
|
|
Access cannot be managed at the cell level: rows and columns are the smallest units for which access can be granted or revoked. Data Administrator should take this into account in their column management. If (at some point) data are to be disseminated separately, they must be stored in separate cells. Consequently, separate columns must be made available.
|
... | ... | |