| ... | ... | @@ -86,14 +86,14 @@ PEP's Castor import is configured with a prefix that differs between Castor stud |
|
|
|
- Report data are imported into columns named just `<prefix>`.
|
|
|
|
- Survey step data are imported into columns named `<prefix>.<package>.<survey>.<step>`.
|
|
|
|
|
|
|
|
When surveys can be answered multiple times by participants, column names with further suffixes are used instead:
|
|
|
|
The described column naming for surveys is used when only a single survey is (answered and) imported into PEP. When participants answer surveys multiple times, and if PEP is configured to import all these data sets, column names with further suffixes are used instead:
|
|
|
|
|
|
|
|
- Survey step data are imported into columns named `<prefix>.<package>.<survey>.<step>.AnswerSet<nnn>`.
|
|
|
|
- The week number when the survey was sent is stored into columns named `<prefix>.<package>.<survey>.<step>.AnswerSet<nnn>.WeekNumber`.
|
|
|
|
|
|
|
|
The `nnn` in these column names is a zero-based index: the first survey's data are imported as `AnswerSet0`, the second survey's as `AnswerSet1`, and so on.
|
|
|
|
|
|
|
|
By convention, the import routine runs as a member of access group `PullCastor`, which is authorized to store data into a column group named `Castor`. Since the access group can store data but not create columns, Data Administrator must ensure that appropriate columns have been made available before the import is attempted. If Castor contains data that should be stored into a column (with a name) that does not exist, the import process will fail. Data Administrator can use the `pepcli castor` command to determine names of required columns, and to create those columns.
|
|
|
|
By convention, the import routine runs as a member of access group `PullCastor`, which is [authorized](https://gitlab.pep.cs.ru.nl/pep-public/user-docs/-/wikis/Access-control#data-access) to store data into a column group named `Castor`. Since the access group can store data but not create columns, Data Administrator must ensure that appropriate columns have been made available before the import is attempted. If Castor contains data that should be stored into a column (with a name) that does not exist, the import process will fail. Data Administrator can use the `pepcli castor` command to determine names of required columns, and to create those columns.
|
|
|
|
|
|
|
|
### Column name mappings
|
|
|
|
|
| ... | ... | |
