On Tue, Dec 16, 2008 at 12:49 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > > : Subject: support for multi-select facets > > I'm confused by something ... is the issue here really "multi-select > facets"? ... that can be dealt with "OR" queries. What it seems you are > trying to tackle isn't so much about UIs that want to allow a multi-select > when faceting on a given field, but when the UI wants to display > facet counts for one field which are not constrained by existing filters > on another field. correct?
multi-select in a single request requires getting facets that are constrained differently per-facet (and may be constrained differently than for the top N docs returned.) > that seems orthoginal to doing "multi-select" > > : Option #1: ability to specify the query/filters per-facet: > ... > : Option #2: ability to specify as a "local param" (meta-data on a parameter) > ... > : Option #3: tag parts of a request using "local params" > > Wouldn't the simplest solution just be to have a new variant of the "fq" > param that is utilized by the QueryComponent but ignored by the > FacetComponent? That would work for a single facet, but not for multiple facets. Going back to the original example: ---------- type ---------- x pdf (32) word (17) x html(46) excel(11) -------- author -------- erik (31) grant (27) yonik (14) The normal case would be that you only want to remove constraints related to what you are faceting on. So when faceting on type, disregard any type related filters. When faceting on author, disregard any author related filters. If I click on "word" docs above, I'd want to see all other constraint counts change except for those under 'type". A simpler way to think about this multi-select scenario is at the GUI level: you want faceting to work exactly as it did before, but you don't want the multi-select facet to "disappear" when you click on one of the items. -Yonik
