... | ... | @@ -179,7 +179,7 @@ The `castor` command's various sub-commands are used to interact with PEP's [Cas |
|
|
To prevent the Castor import from using overly long and/or difficult to interpret column names, Data Administrator can use the `pepcli castor column-name-mapping` command to define [column name mappings](Castor-integration#column-name-mappings). PEP's import routine will then import Castor data into columns named after the mappings rather than after the raw Castor names. The command's subcommands provide basic CRUD operations. The "read" operations can be performed by any enrolled user:
|
|
|
|
|
|
- `pepcli castor column-name-mapping list` lists all configured column name mappings.
|
|
|
- `pepcli castor column-name-mapping read <castor>` creates a new column name mapping, causing PEP to use the specified `<pep>` replacement for Castor entities whose name matches `<castor>`.
|
|
|
- `pepcli castor column-name-mapping read <castor>` reports the mapping that is applied to Castor entities whose name matches `<castor>`. If no such mapping exists, the output will be empty.
|
|
|
|
|
|
Manipulation of column name mappings requires enrollment as a `Data Administrator`:
|
|
|
|
... | ... | |