... | @@ -93,8 +93,16 @@ The described column naming for surveys is used when only a single survey is (an |
... | @@ -93,8 +93,16 @@ The described column naming for surveys is used when only a single survey is (an |
|
|
|
|
|
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.
|
|
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](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.
|
|
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](https://gitlab.pep.cs.ru.nl/pep-public/user-docs/-/wikis/Using-pepcli#castor) to determine names of required columns, and to create those columns.
|
|
|
|
|
|
|
|
### Character mangling
|
|
|
|
|
|
|
|
@@@ more here @@@
|
|
|
|
|
|
### Column name mappings
|
|
### Column name mappings
|
|
|
|
|
|
@@@ more here @@@ |
|
PEP imports Castor data into columns based on the names of Castor entities. But Castor is configured for human consumption, causing configured names to be long and descriptive, and localized to the culture of the person that enters the data. This results in PEP column names often becoming cumbersomely long and difficult to interpret. PEP offers Data Administrator the ability to configure column name mappings as a way to have PEP and its import process use different column names.
|
|
\ No newline at end of file |
|
|
|
|
|
Mappings apply to the individual sections of Castor import column names. If PEP encounters a mapped Castor name during import, it bases the column name on the configured replacement instead of the raw Castor name. For example, a Castor survey step might be called `01. Demografische vragen voor de mantelzorger` (which translates to "01. Demographic questions for the caregiver"). Data Administrator could use [the `pepcli castor column-name-mapping` command](https://gitlab.pep.cs.ru.nl/pep-public/user-docs/-/wikis/Using-pepcli#castor-column-name-mapping) to introduce a mapping to use the `CgDemog` moniker instead of the long and descriptive Dutch original.
|
|
|
|
|
|
|
|
Note that if a mapping is configured, it applies to all Castor entities with the same ([mangled](#character-mangling)) name. For example, when Data Administrator introduces a mapping for a survey step named `Stap 2`, the mapping will also be applied to all other entities (surveys, phases, steps etc.) with that same name. |
|
|
|
\ No newline at end of file |