similar to: GSoC 2017: Letor Click Data Mining

Hi James, > Isn't this from the query template, ie from the main web page of search > results? (It might make sense from opensearch as well, though.) Yes, you are right; it is the query template. The reason I said opensearch template is that I haven't quite read all sections of the Omega docs and I'm still in the process. Thanks for pointing that out. I'm aiming to cover

> 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

I've just noticed the Omega "opensearch" template seems to lack escaping for URLs in <link> tags: $httpheader{Content-Type,application/xml}<?xml version="1.0"?> <rss version="2.0" xmlns:openSearch="http://a9.com/-/spec/opensearchrss/1.0/"> <channel> <title>Xapian search results</title>

> The log command will be executed wherever it is in the template. > By "current system user", what do you mean? There'll need to be > write permission for the CGI process, which is probably the same > identity as the web server process. I basically changed the ownership of the /var/log/omega directory to the current user using: sudo chown `whoami` /var/log/omega But I

I am interested in the project 'Learning to Rank Click Data Mining', and here is my current understanding about this project: 1. where can we get your click data. we can extend the omega to supports log the user's search and clicked documents 2. the specific click data information and format. Based on some paper and public query dataset format(AOL search query logs[1] and Sogou

Hi James, > ID: some identifier for each query > QUERY: text of the query (when the query is run) > URLs: every URL displayed (or alternatively, the Xapian docid — this > might be easier) > OFFSET: otherwise you'll have difficulty coping with result pages other > than the first page (when this happens, the query ID should probably > remain the same, and when you aggregate

Hello, I was looking for a search engine for a small internal documentation site and found xapian and omega. Downloaded and compiled it using msys and ming on a german windows xp system. Finally installed apache on the same box. Following the omega example I copied the book to .../apache/htdocs and startet the omindex which hang up on the first document found. Even on very short doc with

Hello :-) There was probably no good reason to do this build but the Debian 6.0 Squeeze repo version was 1.2.3, we needed 1.2.4 and I didn't think of using the package from unstable. Arch: x86_64 Platform: Linux 2.6 Debian 6.0 (Squeeze) Compiler: gcc version 4.4.5 (Debian 4.4.5-8) Version: 1.2.4 Status: no known problems Source: http://oligarchy.co.uk/xapian/1.2.4/xapian-core-1.2.4.tar.gz

Hello :-) We have Xapian and Omega working nicely. Now we would like more functionality at the browser UI, such as being able to specify date ranges and being able to search the file name including looking only for, say, .odt files. Question is whether the best choice for this would be to develop a template using OmegaScript or to switch to C++ or some other language. Availability of skills

Hi, In my explorations of Omega codebase, I have found that Omega is currently missing support for newer weighting schemes added in 1.4.1 (BM25+, PL2+, Dir+). I'd submit a PR addressing that but as I think I might be missing something so just wanted to check if there's a particular reason for that? P.S. Finally back after a long week. Been eagerly waiting for a weekend since the

I'm using omega for a sitesearch and currently having a problem trying to filter $field(sample). At the moment it returns text from the page header and navigation within the sample, ideally I'd like it to return only the page content. I've been trying various omegascript commands to trim the output or seperate the fields and also looking at scriptindex to control how the xhtml is

Folks, Is it possible to query a document value (doc.set_value(i, val)) as part of the Omega query. I know how to do it from code. Is there a query markup to use for Omega? ...Thanks, ...Ken

> In case I wasn't clear: I don't think you have to modify the command > at all. Just create a template that uses the command as it currently > works. I thought we needed a new template only for the second log file? To generate the first log file using the existing $log command, I have introduced another $log command in query template that looks like:

> > I'm not clear on what the OFFSET really represents. Could you > > please explain a bit? > > Omega paginates results (as does Xapian's MSet, internally). So if > you're displaying the second page of results, you'll need to know > that when building training data. It's affected by TOPDOC and also > by the <>[# CGI variables, but internally to

Hi, I spent this week mostly understanding how the existing templates work and setting up Omega CGI on my system to have a better grasp over how things actually look like when using different templates. This helped me look at things associated with logging the click data from a better perspective. As already documented on the project's wiki page, we need the following fields in separater

Hi, I configured XAPIAN 1.0.1 and OMEGA 1.0.1. on my development machine (first removed the old ones). I recreated my databases (both quartz and flint) and tried to run original queries against the databases created by the new versions. I'm getting empty result sets from OMEGA. If I use the delve tool I actually see that the records are created fine. No log files are written as far as I

Hi, I'm Ayush an undergraduate Computer Science student from Thapar university, India. I was fiddling with xapian since the morning and trying to understand the code and internals of Xapian. I tried implementing the bite sized project idea posted here: https://trac.xapian.org/wiki/ProjectIdeas#AddnewOmegaScriptcommandtodoasubstringsearch but could not understand what needs to be returned when

> There's a lot of flexibility already, because the log format is just > omegascript. So I don't think you need to implement a new command to > achieve this. (Although you might need a command to generate the query > id. It depends on how you're going to do that.) Ok, I'll try adapting the existing log command to achieve the kind of logging we want. And, about the

I installed Xapian and Omega following the instructions for the RHEL 5 RPM package found at xapian.org. I was going to perform the quick start instructions, but there is not "omnidex" for the omindex --db DBPATH --url / WEBPATH command. The quick start also mentions running omega from usr/lib/omega/bin; however that was not created as well using the RHEL 5 RPM. Is there a walkthrough on

> -----Original Message----- > Date: Tue, 26 Apr 2011 13:35:20 +0100 > From: James Aylett <james-xapian at tartarus.org> > Subject: Re: [Xapian-discuss] Omindex: what are the default numbered > indexes? > To: <xapian at catcons.co.uk> <xapian at catcons.co.uk> > Cc: 'Xapian Discussion' <xapian-discuss at lists.xapian.org> > Message-ID: