search for: omegascript

...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 both for development and long-term support are relevant. For development, I am the only resource; my web programming skills are basic (some hand edited static HTML pages), my C is very rusty (no C++), I have Ruby (not Ruby on Rail...

> Hi, Vivek — there isn't any particular reason that I'm aware of. It's > probably worth pointing (in the omegascript documentation) to the part of > the getting started guide which talks about the different weighting schemes If there isn't any reason then I'd like to send in a patch adding support for those weighting schemes in weight.cc and I agree omegascript documentation should also be updated to...

...'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 this command is called. This line is not so clear to me: expand to the offset of the first occurrence of fish from the start of the string if $query, or to if $query doesn't contain the substring fish. Also in qu...

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 parsed. I'm still new to omega so I'd be grateful for any input on the proper method to use. ---omindex command ~/omega/bin/omindex --db ~/omega/data/default --mime-type xht...

...nternally). 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 omega there's one > variable it's mapped onto. > > In omegascript, you can find this using $topdoc. Thanks for the explanation. Understood now. > > In the end, we will have two files it seems -- one created from the > > query template containing separate entries for each executed search > > as per the format you described previously and anothe...

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

> 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

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

> It may be worth splitting that part of the $set documentation out into its > own section somehow, because it's getting a bit long - Undoubtedly; $set command has the longest section on the documentation page :) But it would be hard splitting that up because the documentation is organised in a way that each command is really contained in its own specific section. > and the details

...ursework because the > semester end is nearing. Not a problem -- that sort of thing is affecting a lot of people at the moment! > I used the latest development version which is 1.3.5 for this patch. > I have implemented the $match function and it works fine when I tested it > with the omegascript templates provided in the development omega source > tarball (1.3.5) Great. In future you should work from a git checkout rather than a tarball, because it makes it less likely you'll run into conflicts with subsequent work (or rather, if you do, you can resolve them more easily). > So...

.../data/default" --url /book "D:/develop/apache22/htdocs" the omega.conf is in the same directory and looks like: # Directory containing Xapian databases: #database_dir /var/lib/omega/data database_dir D:\develop\apache22\cgi-bin\omega\data # Directory containing OmegaScript templates: # template_dir /var/lib/omega/templates template_dir D:\develop\apache22\cgi-bin\omega\templates # Directory to write Omega logs to: #log_dir /var/log/omega log_dir D:\develop\apache22\logs # Directory containing any cdb files for the $lookup OmegaScript comman...

...$root/usr/share/xapian-omega/templates/inc rsync -a --quiet templates/ $root/usr/share/xapian-omega/templates/ # Extra to Olly's proforma file list cp -p AUTHORS COPYING ChangeLog NEWS README TODO $root/usr/share/doc/xapian-omega/ # Equivalent to some of the "not found"? cp -p extra/omegascript.vim $root/usr/share/vim/vim72/ mkdir -p $root/var/lib/omega/data chown docmgt:docmgt $root/var/lib/omega/data if [[ ! -d $root/var/lib/omega/templates ]]; then mkdir -p $root/var/lib/omega/templates rsync -a --quiet templates/ $root/var/lib/omega/templates else echo "$root/var/lib/o...

On Mar 29, 2016 4:49 PM, "Olly Betts" <olly at survex.com> wrote: > > On Tue, Mar 29, 2016 at 11:41:02AM +0100, James Aylett wrote: > > It's probably helpful to create a ticket and claim it (and update the > > project ideas list to link to it), so other people don't try to work > > on it as well. (I have a feeling that it might have been among the

> 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 t...

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

...not entirely sure how to achieve the last part i.e. updating the log file with click information but as discussed earlier, a log template can helpful here. As of now, I think it could be implemented like topterms template (i.e. without any structure to be displayed) where we'd jsut invoke some Omegascript commands to do the update. Another question -- we'd need to trigger this template whenever a click happens, so is it possible to have such a behaviour from within query template through some existing Omegascript commands? Thanks, Vivek -------------- next part -------------- An HTML attachment...

...day or two to have a good understanding of how the project will fit in. However, I won't be able to cover all the Omega- -Script commands but atleast the most related ones like $log. > We need some way of logging when people click on a search result — which > you can build using a second omegascript template, as Olly suggested. Okay, so it will act between the query template and a linked document pointed by a search result. Do you think we need to make this new template transparent to the user in some way as we might have to record some information such as user ids in the form of IP? In any c...

Hi , I am currently using xapian with plaintext parsr (i think) to get output on konsole itself. How it cud be possible get that output on the/as the html page or xml page Thank You. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.tartarus.org/pipermail/xapian-discuss/attachments/20060327/dbe044f3/attachment.htm

Hello, I have installed and configured omega to index samba shares on a debian server. I would like to know if it's possible to change the HREF links on the search results page to begin "file://" instead of "http://" I had a look at the templates files and there was no obvious solution that I could see. Thanks. -- Chris Purves Visit my blog: http://chris.northfolk.ca