... | @@ -115,7 +115,7 @@ To ensure that generated column names use the period `.` character exclusively a |
... | @@ -115,7 +115,7 @@ To ensure that generated column names use the period `.` character exclusively a |
|
|
|
|
|
### Column name mappings
|
|
### 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 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.
|
|
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/or 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 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.
|
|
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.
|
|
|
|
|
... | | ... | |