What is described here as "Passage Search" is nothing more than a PhraseQuery with a large slope. I think it's a UI problem rather than a ranking algorithm. For example you may want to have translate simple multi-term queries into phrasequery by default (instead of AND or OR). Let's say search you convert the query into <"man bites dog"~1000> every time someone types just <man bites dog> so to give more weight to documents/passages that contain the words near to each other, like Google does by does.
What I would like however is to have query variables that can be used when you don't have a good way of estimating the slope. It would be ideal to have a query syntax implementation that would allow doing something like: <"man bites dog"~DOCSIZE> that would execute a phrasequery with the slope being the individual document size in number of characters of each hit. Has anyone thought of how to introduce variables into the query language? J.D. -----Original Message----- From: Giulio Cesare Solaroli [mailto:[EMAIL PROTECTED] Sent: Thursday, January 27, 2005 5:39 PM To: Lucene Developers List Subject: Passage Search Hi all, reading some posts in Steve Green's weblog, I found the description of a "Passage search" (http://blogs.sun.com/roller/page/searchguy/20050126). Translated into Lucene words, this looks like a nice score algorithm that could be applied to rank the matching documents. Does anybody have any idea on how the suggested approach stands up to Lucene current algorithm, and how difficult would be to inplement also the "Passage search" scoring? Thanks for your attention. Regards, Giulio Cesare Solaroli --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
