Format of the taxonomy input file

The input must contain four mandatory configuration properties and a corresponding set of managed value data.

The first line of a taxonomy input file must have these managed value header properties, and in this order:

MvalSpec|Displayname|ParentKey|Synonym

The actual names of the header properties in your input file can be different from the names used here (for example, you can use CategoryKey instead of MvalSpec). However, the order (positions) of the header properties and their values is crucial. For example, the third position signifies the managed value's parent ID, regardless of the name used for that header property.

The meanings of these header properties are as follows:

Property	Purpose
MvalSpec	A unique string identifier for the managed value. This is the managed value spec.
Displayname	The name for the managed value.
ParentKey	Specifies the parent ID for this managed value: If this is a root managed value, use a forward slash (/) as the ID. If this is a child managed value, specify the unique ID of the parent managed value.
Synonym	Optionally defines the name of a synonym. You can add synonyms to a managed value so that users can search for other text strings and still get the same records as a search for the original managed value name. Synonyms can be added to both root and child managed values. If you add multiple synonyms for a managed value, the synonyms are separated by a delimiter that you specify in the configuration of the Add Managed Values connector.

After the header row, the second and following rows in the input file contain managed value data for the managed value properties.

The following image shows the beginning lines of the ProductCategoryTaxonomy.csv input file for the taxonomy graph:

In this example:

Four root managed values are created. Their managed value specs are CAT_BIKES, CAT_COMPONENTS, CAT_CLOTHING, and CAT_ACCESSORIES and they all have a ParentKey of a forward slash (/) because they are root managed values. Their CategoryDisplayName values set the names that will be displayed in the application UI.
Seven child managed values are created. Three are children of the CAT_BIKES managed value and the other four are children of the CAT_COMPONENTS managed value.

Note that more child managed values are created from the ProductTaxonomy.csv specifications. In our example, the file is stored in the data-in folder of the project.