one more idea: first search is grouped by brand with limit 1, it gives you a most relevant products for this particular search. than second search boost top products from the first search result by ie. q=original:query ID:(44,56,78,99,22)^1000
On Tue, Aug 21, 2012 at 8:04 PM, Karthick Duraisamy Soundararaj < [email protected]> wrote: > > On Tue, Aug 21, 2012 at 11:32 AM, Tanguy Moal <[email protected]>wrote: > >> Sorry then, my approach really disables pagination jumps. You're left >> with the 'next' button only, or an "infinite-scroll" type of pagination, >> which may not be what you wanted to do... > > You are right. > > >> Did you try disabling tf/idf and using random field as a secondary sort >> ? I'm pretty sure it will give you the best results with best efforts. >> > I was little nervous about turning off idf as I was concerned it might > affect relevancy. Considering that idf promotes documents with unique words > across the index more than the ones, turning off idf might make sense in an > ecommerce application. What do you think? > > But then, I dont get idea of random field for secondary sort. Secondary > sort is applicable only in the cases where the scores/primary sort values > are tied right? So I am not quite sure as how it would fit in here. > > -- > >> Tanguy >> >> 2012/8/21 Karthick Duraisamy Soundararaj <[email protected]> >> >>> Hello Tanguy, >>> I need pagination. The problem with your >>> approach is that, to achieve pagination, you need to do a sort at >>> application level for sorting rather than at the solr level which I think >>> would become messy. Do you see a way around this? >>> >>> Thanks, >>> Karthick >>> >>> >>> On Tue, Aug 21, 2012 at 10:33 AM, Tanguy Moal <[email protected]>wrote: >>> >>>> Hello Karthick, >>>> >>>> 2012/8/21 Karthick Duraisamy Soundararaj <[email protected]> >>>> >>>>> *"Find all the highest scoring document for each manufacuturer in >>>>> the current result set and place them ahead of the rest. Here as you can >>>>> see, the idea is to display one product from each unique manufacturer >>>>> first" >>>>> *. Now to decide how many unique manufacturer to show before the >>>>> normal ordering can be determined relative to the total number of unique >>>>> manufacturers. Like for example, if there are 90 unique manufacturers, >>>>> display products from 45 (approx 50%) first before displaying the rest of >>>>> the products. >>>>> >>>> >>>> That's exactly what grouping will do. At least for the first sentence. >>>> You can ask for many items in each group, display only the first and store >>>> the others "somewhere", for later use. When you reach your "merchant >>>> representation threshold" (say 50% of total number of groups) then you can >>>> start picking the items you stored "somewhere" to display them at randomly >>>> chosen positions. That won't help pagination, though. >>>> >>>> Could that help you ? >>>> >>> >>> >>> >>> >>> >> > > > > -- Sincerely yours Mikhail Khludnev Tech Lead Grid Dynamics <http://www.griddynamics.com> <[email protected]>
