When the
isAutoGen property of an attribute defined in
index-config.json is set to true ("isAutoGen" :
true), the name of the attribute becomes the name of an the
automatically generated dimension. This rule applies only to attributes with
the parameter
"jcr:primaryType" : "endeca:dimension".
Dimension values for flat dimensions,
however, are not named explicitly in
index-config.json. Instead, the
"sourcePropertyNames" attribute parameter specifies the name
of a source record property whose value will be used as a dimension value in
the flat dimension.
For example, the following attribute in
index-config.json specifies that the value of every
property in your source records named
video_capability will become a dimension value of a
flat dimension named
camera.video_capability:
"camera.video_capability" : {
"displayOrder" : 7,
"jcr:primaryType" : "endeca:dimension",
"isAutogen" : true,
"sourcePropertyNames" : [ "video_capability" ]
},Thus, if three different source records each have a property named
video_capability, set to
Slow,
Regular, and
Fast respectively, the flat dimension named
camera.video_capability will contain dimension values
named
Slow,
Regular, and
Fast.
Also note that a source record can have different properties, each of
which matches the
sourcePropertyNames value in a different dimension.
Thus, a single Endeca record might be tagged to the dimension value
green in the dimension
Color, to
Camera in the dimension
category, and to $150 - $200 in the dimension
Prices.
Note
The attribute definitions in
index-config.json do not define hierarchic
relationships among the dimension values. That is, these attribute definitions
cannot specify which dimension values are parents or children of other
dimension values. You must specify these relationships among dimensions values
in
rs_baseline_dimvals.xml.
For more information, see
Configuring dimension values for hierarchical dimensions.

