Using-pepcli.md

@@ -173,7 +173,16 @@ The `castor` command's various sub-commands are used to interact with PEP's [Cas
 
 ### `castor column-name-mapping`
 
-@@@ more here @@@
+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>`.
+
+Manipulation of column name mappings requires enrollment as a `Data Administrator`:
+
+- `pepcli castor column-name-mapping create <castor> <pep>` 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 update <castor> <pep>` specifies a new `<pep>` replacement for an existing column name mapping for the specified `<castor>` name.
+- `pepcli castor column-name-mapping delete <castor>` removes an existing column name mapping for the specified `<castor>` name. Subsequent import runs will revert to using the Castor name to determine the name of the column where data will be stored.
 
 ### `castor create-import-columns`