...
Key | Data Type | Description | |||||
---|---|---|---|---|---|---|---|
Data Source | |||||||
source_type | String | Which source type to connect to. Valid values:
A connection string for where to find the original data. At the moment, only the Example: | |||||
source_script | String | The Data Loader Plugin to load. This and the source_type are mutually exclusive. | |||||
... | Additional connection options are specified as key/value pairs as well. Use the same options as for the data loader, with the dashes replaced with underscores. For example if the data loader is invoked with
Check the Data Loader Reference for all the possible options. Plugin-specific options are documented in each plugin. | ||||||
KEE Configuration | |||||||
strategy | String | The name of the strategy to use for matching on this data source. This needs to reference to a strategy key that has been defined in the Strategies section of the config file. | |||||
field_id | String | The name of the column in the input data which is the unique identifier of a row. | |||||
generate_id | Boolean | Automatically generate unique identifiers for rows. Can be used if (and only if) field_id is not specified. | |||||
field_matching | List | Names of the columns of the input data that contain the object names used for the KEE matching. This is generally the primary name and often an alias column. | |||||
hierarchy | String | Specifies a hierarchy in the data. This hierarchy can be used in the tagging for example to tag an item with the matching company and all of the parent companies as well. The format of this configuration is See the hierarchy section for examples. | |||||
multivalue | List | A list of column names that can contain multiple values. This is commonly used for the alias column. The default separator for multiple values in the source data is the pipe ( Example:
|
...