Hoss..
--> I strongly advise anyone who asks me 99% of the time "fall back" queries
for 0 results found are a really bad idea, because they can easily
create
very strange user experiences.
yes, I do agree it will create strange user experience in most of the
cases.But in my case I need to show some results that is closely related to
the user instead of saying "no results found".
for Eg. user may be looking for the mobile-phone costs below $5000,white
color,samsung,jelly bean,etc..
I have mobile-phones with all these specification but price is
$5005.Instead of giving 0 result I want to show this.I cannot go back and
ask for the requirement change.
thanks for the useful links.
Thanks & Regards,
Senthilnathan v
Thanks & Regards,
Senthilnathan V
On Tue, Dec 17, 2013 at 9:28 PM, Chris Hostetter
<hossman_luc...@fucit.org>wrote:
>
> : Subject: Fallback Local Requests
>
> ...
>
> : if this query returns 0 results then
> : -->fire a fallback query after changing the value of size_min and
> : size_max
>
> I strongly advise anyone who asks me 99% of the time "fall back" queries
> for 0 results found are a really bad idea, because they can easily create
> very strange user experiences.
>
> Check out slide #11, the "Fallback" example ~ 14:50 ...
>
> https://people.apache.org/~hossman/ac2012eu/#slide11
> http://vimeopro.com/user11514798/apache-lucene-eurocon-2012/video/55822630
>
> ...watch the whole video for an in depth discussion on how to take
> advantage of domain knowledge to *boost* documents based on important
> criteria so they score higher instead of using sledgehammers like fallback
> queries.
>
>
> -Hoss
> http://www.lucidworks.com/
>
