... | ... | @@ -80,7 +80,20 @@ The import of standalone reports produces an equivalent JSON structure to keep t |
|
|
|
|
|
## Column naming
|
|
|
|
|
|
@@@ more here @@@
|
|
|
PEP's Castor import is configured with a prefix that differs between Castor studies and between the type(s) of data that are imported from each Castor study. The import routine then stores Castor data into columns whose names start with the configured prefix. The remaining part of the column name is derived from the Castor entity, as follows:
|
|
|
|
|
|
- CRF step data are imported into columns named `<prefix>.<phase>.<step>`.
|
|
|
- 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:
|
|
|
|
|
|
- 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.
|
|
|
|
|
|
Since the import routine is authorized to store data but not to create them, Data Administrator must ensure that appropriate columns have been made available before the import is attempted. If the import process encounters data that should be stored into a column (with a name) that does not exist, the import run will fail. Data Administrator can use the `pepcli castor` command to determine names of required columns, and to create those columns.
|
|
|
|
|
|
### Column name mappings
|
|
|
|
... | ... | |