You map source record properties to Guided Search dimensions or properties in JSON documents. The JSON documents are composed of one or more attributes, each of which maps a source record property to a Guided Search property, derived property, dimension, or range dimension.

You must import the JSON document into the ECR before you run a record store merger. For information about how to import JSON documents, see Creating, modifying, viewing, and deleting index attribute configuration and Creating, modifying, viewing, and deleting index attribute configuration remotely.

When a record store merger is run, all properties in a source record that are mapped to Guided Search properties become properties of a corresponding Guided Search record. Unmapped source properties are not included in the Guided Search record.

The following except from a JSON document illustrates each type of attribute:

"camera.operating_temperature_range_t-t" : { 
    "propertyDataType" : "ALPHA", 
    "ecr:type" : "property", 
    "sourcePropertyNames" : ["camera.Operating temperature range (T-T)" ]
}, 
"product.min_price" : {
    "derivedPropertyFunction" : "MIN",
    "ecr:type" :  "derived-property",
    "derivedPropertySource" : "product.price"
},  
"camera.video_capability" : { 
    "displayOrder" : 7, 
    "ecr:type" :  "dimension",
    "isAutogen" : true, 
    "sourcePropertyNames" : [ "camera.Video capability" ]
}, 
"camera.megapixel_range" : { 
    "displayOrder" : 16,
    "ecr:type" : "dimension", 
    "rangeComparisonType" : "FLOAT", 
    "sourcePropertyNames" : [ "camera.Megapixel" ] 
}, 

These attributes configure:

For example, suppose that source data records in your product data record store have the following properties:

camera.sensor_megapixels
camera.lens_focal_length
camera_type
camera_weight

You want to produce Endeca records that have the following simplified names for these properties, omitting the property for the camera's weight:

megapixels
focal length 
type

To map these source record properties to Endeca properties, add the following attributes to the JSON document:

"megapixels" : { 
  "propertyDataType" : "ALPHA", 
  "ecr:type" : "property", 
  "sourcePropertyNames" : [ "camera.sensor_megapixels" ]
},
"focal length" :  { 
  "propertyDataType" : "ALPHA",
  "ecr:type" : "property", 
  "sourcePropertyNames" : [ "camera.lens_focal_length" ]
},
"type" : { 
  "propertyDataType" : "ALPHA",
  "ecr:type" : "property", 
  "sourcePropertyNames" : [ "camera_type" ]
},

Given this property mapping, indexing a source data record with the following properties and property values:

camera.sensor_megapixels: 24.2 
camera.lens_focal_length: 18-55mm 
camera_type: digital 
camera_weight: 450g

will produce an Endeca record with the following properties and property values:

megapixels: 24.2
focal length: 18-55mm  
type: digital