... | ... | @@ -115,10 +115,10 @@ To ensure that the period `.` character only appears as a section delimiter in g |
|
|
|
|
|
### Column name mappings
|
|
|
|
|
|
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.
|
|
|
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 people entering the data. This results in PEP column names often becoming cumbersomely long and difficult to interpret by international users. To counteract, 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.
|
|
|
|
|
|
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.
|
|
|
Mappings apply to the individual sections of Castor import column names. If PEP encounters a mapped Castor name during import, it names the corresponding column name section after the configured replacement instead of the raw Castor name. For example, a Castor survey step might be called `01. Demografische vragen voor de mantelzorger` ("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 have PEP use the `CgDemog` moniker instead of the long and descriptive Dutch original.
|
|
|
|
|
|
If a mapping is configured, it applies to all Castor entities with the same 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. Data Administrator should be aware that, when a mapping is introduced, differently named columns may be needed for the import of multiple Castor studies and/or data types.
|
|
|
If a mapping is configured, it applies to all Castor entities with the same 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.) that are also named `Stap 2`. Data Administrator should be aware that, when a mapping is introduced, the import of multiple Castor studies and/or data types may require differently named columns.
|
|
|
|
|
|
Note that column name mappings are applied to [mangled](#name-mangling) names rather than raw names. Castor entities named `pésca` ("fishing") and `pèsca` ("peach") would therefore be subject to the same mapping, since both are mangled to `psca`. |
|
|
\ No newline at end of file |