Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • U User docs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PEP Public
  • User docs
  • Wiki
  • Castor integration

Castor integration · Changes

Page history
Update Castor integration authored Mar 25, 2021 by Kai van Lopik's avatar Kai van Lopik
Hide whitespace changes
Inline Side-by-side
Castor-integration.md
View page @ b755464b
......@@ -145,4 +145,8 @@ When PEP's import routine encounters Castor data, it simply attempts to store it
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.)
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
# 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.
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
Clone repository
  • Access control
  • April 2022 migration
  • Castor integration
  • Data structure
  • Glossary
  • Pseudonymization
  • Uploading and downloading data
  • Using pepcli with docker
  • Using pepcli
  • Home