Hello folks!
I have a small dilemma, and was wondering if anyone would lend some
guidance. I have a field, called "attributeFacet", and it has lots of
things like...
Upper Materials/Finishes - Suede
Upper Materials/Finishes - Canvas
Upper Materials/Finishes - Synthetic
Upper Materials/Finishes - Synthetic Leather
Upper Materials/Finishes - Synthetic Nubuck
Lining - Leather
Lining - Canvas
Lining - Mesh
...etc...etc... (there is a totally arbitrary number of these, and
they're added to all the time).
From my index, these are currently stored as "Lining::Leather" or
"Upper Materials/Finishes::Canvas" under an "attribute" field.
I found that this works quite well, but it's something I must change.
Namely, I cannot facet on "Lining" to get a list of the various
linings available in a result set, and that is something that I need
to be able to do.
I've thought that I could use a dynamic field for this, something like
attribute_<something>. I could strip off the attribute_ part in the
display easy enough, but I'm not sure how I can facet on all these
fields. There could be 100s of them in the long term timeframe. I'm
not sure that addFacetField("attribute_*") would work... but I really
have no way of knowing exactly what the fields are in advance without
doing an ugly database call and a loop to add in the facets.
Worst case: I do a "select name from attribute;" and loop through to
add alllll these facet fields to my query.
Best case: I can do some sort of "addFacetField("attribute_*") magic.
Thanks!
Matthew Runo
Software Developer
Zappos.com
702.943.7833
