Ooops, I just realized that at some point java-user was removed from the CC :). Fixing that.
Shai On Fri, Jan 25, 2013 at 2:27 PM, Shai Erera <ser...@gmail.com> wrote: > Hi Nicola, > > Indeed, if it's a URL with parameters, it's not a UI trick :). I think > that you can do what you want with the package, but before I explain what I > think you should do, I'd like to use a concrete example, to better > understand: > > Suppose that you have facets A/1, A/2 ... A/6 associated with documents. A > document is associated with exactly one "A" facet, but the same facet may > be associated with many documents. > You query for X and it matches some documents that are collectively > associated with facets A/1, A/2, A/3 and A/4. So A/5 and A/6 are associated > with documents that do not match your query. > However, your FacetRequest sets its numResults (what we call top-K) to 2, > so you only get back A/1 and A/3, since they have the highest counts. > > So what we have now are: > * Facets A/1, A/3 returned to the user, since they belong to the result > set and have the highest counts > * Facets A/2, A/4 are not returned to the user, even though they belong to > the result set, but did not make it to the top-K > * Facets A/5, A/6 are not returned because they don't belong to the result > set at all. > > If this makes sense to you, and is similar to the scenario that you have, > which of these facets would u like to show in addition to A/1 and A/2? > > Shai > > > On Fri, Jan 25, 2013 at 11:39 AM, Nicola Buso <nb...@ebi.ac.uk> wrote: > >> Hi Shai, >> >> thanks, again you are helping me a lot introducing faceted search. >> >> I'm not sure it's a UI trick. Suppose you have a URL with query params >> that lead you to: >> - the electronic department >> - query on "hi-fi" >> - brand facet selection on "A" >> >> which trick should the UI use? As a trick I should immagine: >> - don't filter on facet with lucene but do it in the UI (now is tricky >> to do the facet counting without lucene) >> - execute 2 query one filtered and one not; pick the selected facets >> from the filtered query and the other from the non filtered one >> (filtered = filtered by facet selection, we can argue here) >> >> Note also I have some services that should return the results together >> the facets if needed. >> >> >> >> Nicola. >> >> On Thu, 2013-01-24 at 22:47 +0200, Shai Erera wrote: >> > That's sounds more like a UI trick to me. When I do that, I don't >> > modify the brand facet (in the UI). I.e., continue to display it, with >> > the original counts and if the user now wants to filter by A + D, then >> > your UI somehow allows that (maybe checkboxes). Of if the user wants >> > to quickly switch from brand A to D, he can do so w/ a single click, >> > without running the original query again. >> > >> > >> > Shai >> > >> > >> > >> > On Thu, Jan 24, 2013 at 10:28 PM, Nicola Buso <nb...@ebi.ac.uk> wrote: >> > Hi Shai, >> > >> > the use case is simple. Suppose you want to buy an hi-fi on a >> > online >> > shop. Go in the website in the Electronic department and write >> > "hi-fi" >> > in the search box, the interface return you lots of results >> > and a facet >> > on brands (10 brands values). >> > You select brand A and the results are filtered accordingly; >> > suppose now >> > you want to filter adding to the results the brand D, you >> > can't because >> > the filtered results by A don't contain values D for the brand >> > facet. >> > >> > Than how can I retrieve also the facets for the results not >> > filtered? >> > I think it's a common use case when you permit to the user to >> > filter in >> > OR by facets. >> > >> > >> > Nicola. >> > >> > On Thu, 2013-01-24 at 19:36 +0200, Shai Erera wrote: >> > > Hi Nicola, >> > > >> > > >> > > Regarding the OR drill-down, yes you can construct your own >> > > BooleanQuery, passing Occur.SHOULD instead of MUST. >> > Currently >> > > DrillDown does not help you do that, so you can copy the >> > code from >> > > DrillDown.query and change SHOULD to MUST. I opened >> > LUCENE-4716 to add >> > > this support to DrillDown. >> > > >> > > >> > > >> > > Not sure that I understand your second question. If you want >> > to >> > > retrieve counts for all descendants of A, then set your >> > > FR.setNumResults to Integer.MAX_VALUE. But note, it's going >> > to be >> > > costly, i.e. you'd get a FacetResultNode per child of A, so >> > depending >> > > how "wide" A is, this may have some impact on RAM >> > consumption. >> > > >> > > If that's not what you meant, could you please clarify? >> > > >> > > >> > > Shai >> > > >> > > >> > > >> > > On Thu, Jan 24, 2013 at 7:22 PM, Nicola Buso >> > <nb...@ebi.ac.uk> wrote: >> > > Hi all, >> > > >> > > I'm introducing Lucene faceted search in our project >> > and I >> > > need some >> > > hints to achieve some functionalities: >> > > - I want facet filtering in OR, how to? >> > > - obtain facets for the filtered results but also >> > for the >> > > non filtered >> > > one. i.e. I have facet A with values A/V1, A/V2, >> > A/V3 and >> > > these values >> > > are disjunct each other, than a document having >> > field with >> > > value V1 >> > > can't have also value V2 and so on; I would like to >> > let the >> > > user select >> > > more of these facet values in OR; how can I >> > accumulate all the >> > > facets >> > > values also filtering by facet selection? Should it >> > work in a >> > > way >> > > similar to ComplementCountingAggregator? >> > > - Can I use DrillDown class to obtain the OR facet >> > filtering >> > > or have I >> > > to rewrite a similar class using the BooleanQuery in >> > OR. It's >> > > not clear >> > > to me by this comment in the API: >> > > Wraps a given Query as a drill-down query over the >> > given >> > > categories, >> > > assuming all are required (e.g. AND). You can >> > construct a >> > > query with >> > > different modes (such as OR or AND of ORs) by >> > creating a >> > > BooleanQuery >> > > and call this method several times. Make sure to >> > wrap the >> > > query in that >> > > case by ConstantScoreQuery and set the boost to >> > 0.0f, so that >> > > it doesn't >> > > affect scoring. >> > > >> > > >> > > Do you have any examples doing this? >> > > >> > > Regards >> > > >> > > Nicola. >> > > >> > > >> > > >> > > >> > > >> > > >> > >> --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: >> > > java-user-unsubscr...@lucene.apache.org >> > > For additional commands, e-mail: >> > > java-user-h...@lucene.apache.org >> > > >> > > >> > > >> > >> > >> > >> > >> >> >> >
