| ... | ... | @@ -147,6 +147,6 @@ When PEP's import routine encounters Castor data, it simply attempts to store it |
|
|
|
|
|
|
|
# Limitations
|
|
|
|
|
|
|
|
When the configuration of the Castor study changes, different and/or additional columns may be needed when these data are imported into PEP. This requires Data Administrator to reconfigure import columns, i.e. perform the [column configuration steps](#column-configuration) again.
|
|
|
|
When the configuration of the Castor study changes, different and/or additional columns may be needed when data are imported into PEP. This requires Data Administrator to reconfigure import columns, i.e. perform the [column configuration steps](#column-configuration) again.
|
|
|
|
|
|
|
|
Note that PEP's import routine does not deal well with removals in the Castor study's configuration. For example, when a survey is removed from a survey package, the corresponding column names can no longer be listed or created by [the `pepcli castor` command](Using-pepcli#castor). But if data has been entered on the basis of the old configuration, the import process will still attempt to store it under the unlisted name. Castor and PEP administrators should take this into account when reconfiguring the Castor study and/or PEP's import columns. |
|
|
\ No newline at end of file |
