From: anna h. <an...@gm...> - 2013-10-07 20:25:21
|
It looks like lowercase and / or are treated as boolean operators by default [1]. I think we should make this false by default in VuFind. Changing things like this which make special words behave differently is very jarring to librarians, so I'm concerned that there may be other things in edismax that "make things easier" (i.e. less transparent) that I'm not seeing, and which actually treat the same input differently in confusing ways. I will try to look for other potential problems; if anyone else has greater familiarity with the details it would be great to hear some reassurance or specifics. Anna [1] http://wiki.apache.org/solr/ExtendedDisMax On Mon, Oct 7, 2013 at 2:55 PM, Demian Katz <dem...@vi...>wrote: > I’ve done a bit of testing, and for the most part, you get similar (not > always identical) result sets, but in some cases, the relevance ranking is > different. I suspect that all significant differences are for the better – > using real Dismax for advanced queries instead of the crazy Lucene-syntax > hack we had before is likely eliminating some weird outliers that shouldn’t > have been there in the first place.**** > > ** ** > > - Demian**** > > ** ** > > *From:* anna headley [mailto:an...@gm...] > *Sent:* Monday, October 07, 2013 1:59 PM > *To:* Demian Katz > *Cc:* vuf...@li... > *Subject:* Re: [VuFind-Tech] Extended Dismax**** > > ** ** > > How will this change affect search results?**** > > Thanks, > Anna**** > > ** ** > > ** ** > > On Fri, Oct 4, 2013 at 10:45 AM, Demian Katz <dem...@vi...> > wrote:**** > > I've done a very simple implementation of eDismax here: > > https://github.com/vufind-org/vufind/pull/42 > > This switches VuFind to use eDismax by default and eliminates lots of YAML > configuration that is no longer necessary. It still allows the ability to > switch back to the old behavior on demand through a new YAML setting, > though the only use case I can imagine for this would be if you needed > VuFind to talk to an older Solr index that doesn't support eDismax; still, > no harm in maintaining backward compatibility for the moment at least! > > Please let me know what you think -- if there are no objections, this can > be merged into master soon. > > thanks, > Demian**** > > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk > _______________________________________________ > Vufind-tech mailing list > Vuf...@li... > https://lists.sourceforge.net/lists/listinfo/vufind-tech**** > > ** ** > |