schema-<name> Section
The schema-<name> section is used to define the schema for the dataset with the matching <name>. That is, the schema-mydataset section contains options describing the data schema to be used in the dataset configured in the dataset-mydataset section.
The options in the schema-<name> sections depend on the requirements for the specific dataset. Each option name is a dataset column name. The option values are the value for the field (which might be the joined schema from which the value is obtained), the datatype, and, if the field contains sensitive or PII data, the value anon.
Special Schema Names and Configuration
The following section names are reserved for the Agent Profile schema and Customer Profile schema, and cannot be used for any other purpose.
- schema-agents-gim
- schema-customers
See Configure Data Loader to Upload Data for the options required for each type of reserved schema configuration section.
How to configure options in this section
The value for this option should be constructed using the following format:
<dict|string|integer...>[,id|created_at][,asis|anon]
- The first part of the option value specifies the data type for this field: dict, string, integer, and so on.
- The second part specifies one of two different values, depending on whether you are configuring an interaction dataset or an Agent/Customer Profile dataset.
- For an Agent/Customer Profile dataset, enter the ID field name. This is normally the employee ID for an Agent Profile dataset and the customer ID for a Customer Profile dataset. This ID field is also typically used as the key for merging Agent/Customer data to an interaction dataset.
- For an interaction dataset, specify the column name of the field that should be set as the Created At timestamp field.
- The third part of the option value specifies whether the field contains sensitive or PII data and should be anonymized. Set this parameter to anon to anonymize the field values and asis to leave them plain; that is, not anonymized.
- The Created At timestamp field cannot be anonymized.
No public options in this section.