All Endeca records exists in a common store and contains reference to the dimension lookup table
property
mapped to a fairly unique source property
typically ID field, long text field
dimension
mapped to a source property has value shared across multiple records
Data Design
roll detail into master
total denormalized record
may lose precision
one record for tuscon that has color (multi- value). How to handle number of cars per color ?
roll master into detail
have primary key into each detail. composite PK
many different records (nXn)
one record for blue tuscon, one for red, one for green etc...
Rollup - Aggregation
During navigation, result can be rollup based on a common property/dimension
detail can show the non-aggregated records
Heterogeneous Records
each record should have a "type" property to allow for filtering
language should store in Endeca.Document.Language