... | ... | @@ -130,11 +130,11 @@ Configuring PEP's Castor integration functionality requires multiple administrat |
|
|
1. Create and configure a Castor study, e.g. using the [Castor Web interface](https://data.castoredc.com/).
|
|
|
2. Grant appropriate access to the Castor study @@@ which privileges? to whom? @@@
|
|
|
3. Have the PEP (support) team configure a short pseudonym column for the Castor study.
|
|
|
4. Register new participants and/or use `pepAssessor` to open existing ones to generate short pseudonyms and create corresponding Castor records.
|
|
|
5. Enter data into the Castor record.
|
|
|
4. Register new participants and/or use `pepAssessor` to open existing ones to generate short pseudonyms and create corresponding records in Castor.
|
|
|
5. Have assessors and/or participants enter data into Castor records.
|
|
|
6. Have the PEP (support) team configure the data type(s) to be imported from the Castor study.
|
|
|
7. Have Data Administrator [configure PEP columns](#column-configuration) required for the import.
|
|
|
8. Perform an import run.
|
|
|
7. Have Data Administrator configure PEP columns (details [below](#column-configuration)) required for the import.
|
|
|
8. Have the PEP (support) team perform an import run and/or schedule imports to be performed periodically.
|
|
|
|
|
|
## Column configuration
|
|
|
|
... | ... | @@ -143,4 +143,6 @@ When PEP's import routine encounters Castor data, it simply attempts to store it |
|
|
1. Use [the `pepcli castor list-sp-columns` command](Using-pepcli#castor-list-sp-columns) with its `--imported-only` switch to determine the name(s) of short pseudonym columns bound to Castor studies.
|
|
|
2. Use [the `pepcli castor list-import-columns` command](Using-pepcli#castor-list-import-columns) to determine the [names of columns](#column-naming) required to import data from Castor.
|
|
|
3. If the column names listed in step 2 are not to your liking, use [the `pepcli castor column-name-mapping` command](Using-pepcli#castor-column-name-mapping) to define [column name mappings](column-name-mappings). Repeat steps 2 and 3 until all column names are acceptable.
|
|
|
4. Use [the `pepcli castor create-import-columns` command](Using-pepcli#castor-create-import-columns) to add import columns that do not yet exist. The command automatically places newly created columns into the `Castor` column group, making them writable to the import process. (Alternatively, use the `pepcli ama column` command to create and group columns manually.) |
|
|
\ No newline at end of file |
|
|
4. Use [the `pepcli castor create-import-columns` command](Using-pepcli#castor-create-import-columns) to add import columns that do not yet exist. The command automatically places newly created columns into the `Castor` column group, making them writable to the import process. (Alternatively, use the `pepcli ama column` command to create and group columns manually.)
|
|
|
|
|
|
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 described steps again. |
|
|
\ No newline at end of file |