From: Demian K. <dem...@vi...> - 2013-07-19 15:01:08
|
Ahh, I see. And you're right about the boosting. This might be a question for solr-user; so many internals have changed that it may be a side effect of some Solr or Lucene change. Or is it possible that when you indexed the records into 2.0, they were in a different order to begin with? - Demian ________________________________ From: anna headley [an...@gm...] Sent: Friday, July 19, 2013 10:58 AM To: Demian Katz Cc: vuf...@li... Subject: Re: [VuFind-Tech] relevance in vufind 2 vs 1.3 I am just looking at default sort values, without any relevance ranking at all (all relevance scores are 1.0 if you do a blank search because it doesn't have anything to decide the relevance of). Does that make sense? The demo site and your live site also show different result order when you submit a blank search. But it looks like you might be boosting villanova-related stuff on your live site. Thanks! Anna On Fri, Jul 19, 2013 at 10:54 AM, Demian Katz <dem...@vi...<mailto:dem...@vi...>> wrote: https://library.villanova.edu/Find and http://vufind.org/demo are running VuFind 1.4 and 2.0.1 respectively and have similar (but admittedly not identical) indexes and configurations. I'm seeing slightly different relevance ranking between them. At a glance, it looks like it may have something to do with 2.0.1 doing a better job of boosting unstemmed values. Are you saying that in your case, relevance seems completely broken, or just different? - Demian ________________________________ From: anna headley [an...@gm...<mailto:an...@gm...>] Sent: Friday, July 19, 2013 10:38 AM To: vuf...@li...<mailto:vuf...@li...> Subject: [VuFind-Tech] relevance in vufind 2 vs 1.3 We're starting to mess with vufind 2 and finding that, without any of our modifications to indexing or search relevance / ranking, the same set of records indexed in 1.3 vs 2 is returned in a different order when you do a blank search. Result order is the same whether you do it in vufind or directly in solr. All relevance scores are 1.0. Anyone know about changes to solr's default sort order that would give this result? It would be comforting to be able to point to the cause, so we don't have to wonder whether we somehow changed some configuration somewhere. Thanks! Anna |