Re: Facet behavior

Hi Guys, Could any of you tell me if I'm right? Thanks in advance. kr, Bast Forwarded Message Subject:Re: Facet behavior Date: Thu, 20 Oct 2016 14:45:23 +0200 From: Bastien Latard | MDPI AG <lat...@mdpi.com> To: solr-user@lucene.apache.org Hi

Re: Facet behavior

On Thu, Oct 20, 2016 at 8:45 AM, Bastien Latard | MDPI AG wrote: > Hi Yonik, > > Thanks for your answer! > I'm not quite I understood everything...please, see my comments below. > > >> On Wed, Oct 19, 2016 at 6:23 AM, Bastien Latard | MDPI AG >>

Re: Facet behavior

Hi Yonik, Thanks for your answer! I'm not quite I understood everything...please, see my comments below. On Wed, Oct 19, 2016 at 6:23 AM, Bastien Latard | MDPI AG wrote: I just had a question about facets. *==> Is the facet run on all documents (to pre-process/cache

Re: Facet behavior

On Wed, Oct 19, 2016 at 6:23 AM, Bastien Latard | MDPI AG wrote: > Hi everybody, > > I just had a question about facets. > *==> Is the facet run on all documents (to pre-process/cache the data) or > only on returned documents?* Yes ;-) There are sometimes per-field data

Facet behavior

Hi everybody, I just had a question about facets. *==> Is the facet run on all documents (to pre-process/cache the data) or only on returned documents?* Because I have exactly the same index locally and on the prod server.. (except that my dev. contains much less docs) When I make a query,

RE: MultiValued facet behavior question

Thanks Robert, your code helped me solve a problem I had! Saved me a lot of time headaches cheers, Nico -- View this message in context: http://lucene.472066.n3.nabble.com/MultiValued-facet-behavior-question-tp3093851p4022375.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: MultiValued facet behavior question

Let me give the full user case... There has been a little misunderstanding, but really some good discussions... 1. Some Cardiologists are also Family Doctors and Internal Medicine doctors (Internist). 2. The use case that confuses the users is the output of the query when using dismax across 2

Re: MultiValued facet behavior question

: And I click on B, does it make sense for the user to display : B : C : E : : after the selection ? Just because items in B are C and E items as well? : As A user I chose B because I'm interested in B items. I do not care if they : are also C and E items. : Technically this is correct, but

Re: MultiValued facet behavior question

Hi Bill, yes, you absolutely do make sense. I posted the exact same question to this mailing list (subject: faceting on multivalued fields), but got no response out of it. A friend of mine is now helping out. I hope someone on the list can give us some advice. I'll post our findings to this

Re: MultiValued facet behavior question

Can your front end app normalize the q parameter. Either with a drop down or a type a head derived from the values in the specialties field. that way q will match value(s) in your facet results. I'm not sure what you are trying to achieve though so maybe i'm off the mark. On 22 June 2011 04:37,

Re: MultiValued facet behavior question

Oh sorry forgot to also type: Often facet fields are not stemmed or heavily analysed. The facet values are from the index. On 22 June 2011 08:21, lee carroll lee.a.carr...@googlemail.com wrote: Can your front end app normalize the q parameter. Either with a drop down or a type a head derived

Re: MultiValued facet behavior question

Am 22.06.2011 05:37, schrieb Bill Bell: It can get more complicated. Here is another example: q=cardiologydefType=dismaxqf=specialties (Cardiology and cardiologist are stems)... But I don't really know which value in Cardiologist match perfectly. Again, I only want it to return:

Re: MultiValued facet behavior question

Here is an example using exampledocs and trunk 4.0: http://localhost:8983/solr/select/?q=cat:%22hard%20drive%22version=2.2sta rt=0rows=10indent=onfacet=truefacet.field=catfacet.query={!lucene}cat: %22hard%20drive%22facet.mincount=1 Results: result name=response numFound=2 start=0 Etc lst

Re: MultiValued facet behavior question

You can type q=cardiology and match on cardiologist. If stemming did not work you can just add a synonym: cardiology,cardiologist But that is not the issue. The issue is around multiValue fields and facets. You would expect a user Who is searching on the multiValued field to match on some values

Re: MultiValued facet behavior question

Hi Bill, can you explain a little bit more around why you need this. Knowing the motivation might suggest a different solution not just involving faceting. On 22 June 2011 08:49, Bill Bell billnb...@gmail.com wrote: You can type q=cardiology and match on cardiologist. If stemming did not work

Re: MultiValued facet behavior question

Hi Bill, as far as I understood now, with the help of my friend, you can't. Multivalued fields don't work that way. You can however always filter the facet results manually in the JSP. You knwo what the user chose as a facet. The issue I ran into is when you have additional facet fields. For

Re: MultiValued facet behavior question

Am 22.06.2011 09:49, schrieb Bill Bell: You can type q=cardiology and match on cardiologist. If stemming did not work you can just add a synonym: cardiology,cardiologist Okay, synonyms are the only way I can think of a realistic match. Stemming won't work on a facet field; you wouldn't get

Re: MultiValued facet behavior question

Hi Bill, So that part works. Then when I output the facet, I need a different behavior than the default. I need The facet to only output the value that matches (scored) - NOT ALL VALUES in the multiValued field. I think it makes sense? Why do you need this ? If your use case is faceted

Re: MultiValued facet behavior question

Hi Lee, since I have the same problem, I might as well try to answer this question. You want this behaviour to make things clear for your users. If they select cardiologists, does it make sense to also show family doctors as a facetvalue to the user. The same thing goed for the facets that are

Re: MultiValued facet behavior question

On 06/22/2011 04:01 AM, Dennis de Boer wrote: Hi Bill, as far as I understood now, with the help of my friend, you can't. Multivalued fields don't work that way. You can however always filter the facet results manually in the JSP. You knwo what the user chose as a facet. Yes - that is the

Re: MultiValued facet behavior question

Hi Dennis, I think maybe I just disagree. Your not showing facet counts for cardiologists and Family Doctors independently. The Family Doctor count will be all Family Doctors who are also Cardiologists. This allows users to further filter Cardiologists who are also family Doctors. (this could be

Re: MultiValued facet behavior question

Well, the use case is rather simple. It is not a use case but more auser experience. If I have a list of values I can facet on, for example : A B C D E And I click on B, does it make sense for the user to display B C E after the selection ? Just because items in B are C and E items as well? As

RE: MultiValued facet behavior question

-Original Message- From: Bill Bell [mailto:billnb...@gmail.com] Sent: Wednesday, June 22, 2011 3:49 AM To: solr-user@lucene.apache.org Subject: Re: MultiValued facet behavior question You can type q=cardiology and match on cardiologist. If stemming did not work you can just add

Re: MultiValued facet behavior question

We always remove the facet filter when faceting: in other words, for a good user experience, you generally want to show facets based on the query excluding any restriction based on the facets. So in your example (facet B selected), we would continue to show *all* facets. Only if you performed

Re: MultiValued facet behavior question

How is that different from doing a field search and just counting the results? If you only want the facet of the searched term (input), then why not just combine that with the result count and use that? Facets are more useful when you _don't_ know the distribution of values across a result set

Re: MultiValued facet behavior question

Okay, so since you put cardiologist in the 'q', you only want facet values that have 'cardiologist' (or 'Cardiologist') to show in up the facet list. In general, there's no good way to do that. But. If you want to do some client-side processing before you submit the query to Solr, and on

Re: MultiValued facet behavior question

Yeah, I agree with that last statement. It seems to me that the use case where it _might_ matter is where you have a query for MORE than one. q=cardiologist OR family and in that case, it MIGHT be useful to separate the facets in a XOR sense where you don't get cross-pollution. But the

Re: MultiValued facet behavior question

An interesting live scenario for this matter: http://www.bondfaro.com.br/  (brazilian site) The query ipad returns results spread across many categories (links on the left, teasers in the center). The Tablet category (facet) is one of them. The query tablet does exactly the same as clicking

MultiValued facet behavior question

I have a field: specialties that is multiValued. It indicates the doctor's specialties: cardiologist, internist, etc. When someone does a search: Cardiologist, I use q=cardiologistdefType=dismaxqf=specialtiesfacet=truefacet.field=specialt ies What I want to come out in the facet is the

Re: MultiValued facet behavior question

So are you saying that for all results for cardiologist, you don't want facets not matching Cardiologist to be returned as facets? what happens when you make q=specialities:Cardiologist? instead of just q=Cardiologist? Seems that if you make the query on the field, then all your results will

Re: MultiValued facet behavior question

Doing it with q=specialities:Cardiologist or q=CardiologistdefType=dismaxqf=specialties does not matter, the issue is how I see facets. I want the facets to only show the one match, and not all the multiValued fields in specialties that match... Example, Name|specialties Bell|Cardiologist