... | ... | @@ -8,4 +8,10 @@ PEP allows for the storage and retrieval of tabular data. Conceptually, it provi |
|
|
| Eric | DK3650519625773963 | 2013-11-19 | ... |
|
|
|
| ... | ... | ... | ... |
|
|
|
|
|
|
Note that PEP does not provide an identifier column, nor should administrators introduce one. Instead rows are referred to by using one of PEP's [pseudonymous identifiers](Pseudonymization#identifiers-in-pep). |
|
|
\ No newline at end of file |
|
|
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 [pseudonymous identifiers](Pseudonymization#identifiers-in-pep).
|
|
|
|
|
|
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 management tasks on them.
|
|
|
|
|
|
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 being 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. |
|
|
\ No newline at end of file |