search for: morelik

On Wed, Nov 26, 2003 at 08:31:00PM +0000, Olly Betts wrote: > On Fri, Nov 21, 2003 at 11:52:44AM +0100, Franck Meunier wrote: > > I indexed internal docs, and then ask omega to "MORELIKE" a document. > > It gives me only a link at 43% to the previous revision of this > > document (i also index my archives)... > > > > The problem is that their was only two or three differences between them. > > > > I found that to do a MORELIKE, omega con...

...to also have an example in the documentation for the same? There's a DEFAULT_LOG_ENTRY string in query.cc that I can across while on the word_in_list PR: "$or{$env{REMOTE_HOST},$env{REMOTE_ADDR},-}\t" "[$date{$now,%d/%b/%Y:%H:%M:%S} +0000]\t" "$if{$cgi{X},add,$if{$cgi{MORELIKE},morelike,query}}\t" "$dbname\t" "$query\t" "$msize$if{$env{HTTP_REFERER},\t$env{HTTP_REFERER}}"; Could you explain the meaning of third and and last strings? > You need to think more carefully about the layers involved here. We don't > want to post-p...

Hi All, I would like to take a doc in the xapian DB and find all related documents by relevance e.g. so when you view one document it says "Related entries X Y Z". I'm aware of the "Morelikethis" Lucene plugin that is supposed to do something like this, by generating a query from a document based on term frequency. Has anyone developed a tool to generate a query from a document? Is there a short-cut one can make with RSets? All the best, Tim.

Hi Olly. Thanks for your reply to the previous email. To have an appropriate subject I've started this new thread for further discussions. > There's a $log{} command available in Omega templates. We can't log from > the result page template, as the clicks happen after that is used, but we > could make result links redirect via a second Omega template which does > the

...You could do that by identifying the search session instead of the user, > which makes it closer to what we need than to something that might trip you > into privacy concerns. Okay, that would be much better. :) > Third records some information about what sort of query it is — add, > morelike or a plain query. Last provides the estimated match size and then > the HTTP referrer if one were set. Neither is particularly interesting in > this case. Thanks for the explanation. So, as I understand it, we'll need some more info to be logged than this to be able to train click model...