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 24, 2021 by Kai van Lopik's avatar Kai van Lopik
Hide whitespace changes
Inline Side-by-side
Castor-integration.md
View page @ abc92d91
......@@ -86,14 +86,14 @@ PEP's Castor import is configured with a prefix that differs between Castor stud
- Report data are imported into columns named just `<prefix>`.
- Survey step data are imported into columns named `<prefix>.<package>.<survey>.<step>`.
When surveys can be answered multiple times by participants, column names with further suffixes are used instead:
The described column naming for surveys is used when only a single survey is (answered and) imported into PEP. When participants answer surveys multiple times, and if PEP is configured to import all these data sets, column names with further suffixes are used instead:
- Survey step data are imported into columns named `<prefix>.<package>.<survey>.<step>.AnswerSet<nnn>`.
- The week number when the survey was sent is stored into columns named `<prefix>.<package>.<survey>.<step>.AnswerSet<nnn>.WeekNumber`.
The `nnn` in these column names is a zero-based index: the first survey's data are imported as `AnswerSet0`, the second survey's as `AnswerSet1`, and so on.
By convention, the import routine runs as a member of access group `PullCastor`, which is authorized to store data into a column group named `Castor`. Since the access group can store data but not create columns, Data Administrator must ensure that appropriate columns have been made available before the import is attempted. If Castor contains data that should be stored into a column (with a name) that does not exist, the import process will fail. Data Administrator can use the `pepcli castor` command to determine names of required columns, and to create those columns.
By convention, the import routine runs as a member of access group `PullCastor`, which is [authorized](https://gitlab.pep.cs.ru.nl/pep-public/user-docs/-/wikis/Access-control#data-access) to store data into a column group named `Castor`. Since the access group can store data but not create columns, Data Administrator must ensure that appropriate columns have been made available before the import is attempted. If Castor contains data that should be stored into a column (with a name) that does not exist, the import process will fail. Data Administrator can use the `pepcli castor` command to determine names of required columns, and to create those columns.
### Column name mappings
......
Clone repository
  • Access control
  • April 2022 migration
  • Castor integration
  • Data structure
  • Glossary
  • Pseudonymization
  • Uploading and downloading data
  • Using pepcli with docker
  • Using pepcli
  • Home