similar to: help improving relevance of snippets displayed by Omega

Olly, Thanks again very much for helping me improve my understanding of Xapian and Omega. Thanks especially for pointing out that my idea of trying to generate a snippet from stemmed text lacking capitalization and punctuation would probably not produce a user-friendly result. But I'm still doubtful that expanding the sample size could be the right way to obtain excerpts from the document

On Fri, Sep 18, 2020 at 04:51:44PM -0400, Michael Decerbo wrote: > I guess that this is because the template shows a snippet generated from > the returned document's "sample" field: > > <small>$snippet{$field{sample}}</small><br> > > and perhaps the text in that "sample" field is fairly short and generated > when the document is

Thanks Olly! But expanding the sample seems like the wrong solution. Is there a way to instead pass a hit or hits from the document to snippet generation? Michael

Hi, Ha, I was reading this thread thinking TheyWorkForYou (which I help maintain) does highlight terms wherever they are, and then you mentioned it :) The code is open source; it is quite old and probably hair-raising, but as you say it does basically do what you want. Our Xapian database stores terms/boolean terms/values for the text, and for the document itself stores only an identifier. It

Whoops, forgot to say, as Olly said, much of that could probably now be simplified with Xapian's snippet() function, which I can only assume did not exist back when all this was written! :) ATB, Matthew On Mon, 21 Sep 2020 at 09:28, Matthew Somerville <matthew at mysociety.org> wrote: > Hi, > > Ha, I was reading this thread thinking TheyWorkForYou (which I help > maintain)

On Fri, Sep 18, 2020 at 08:33:49PM -0400, Michael Decerbo wrote: > But expanding the sample seems like the wrong solution. Is there a way to > instead pass a hit or hits from the document to snippet generation? I'm not sure what you have in mind, but the only way I can see that working is if it read all the positional data for all the terms in the document, and then sorted it to

Hi, I would like to add "text/x-mail" support to omega. I'm using mhonarc to export mail to HTML format and I'm using HTML parse to index mail content (largely inspired by "application/vnd.ms-outlook" format). The problem is that files attached to the mail are not indexing at all. I think it's not possible in "index_file" function to index 2 files as one

Proposed changes to omindex Currently Available Items ========================= 1) Have the Q prefix contain the 16 byte MD5 of the full file name used for document lookup during indexing. 2) Add the document?s last modified time to the value table (ID 0). This would allow incremental indexing based on the timestamp and also sorting by date in omega (SORT=0) a. Currently I store the timestamp

On Fri, Jul 29, 2005 at 10:08:13AM +0100, james wrote: > SVN root: svn://svn.xapian.org/xapian > Changes by: james > Revision: 6355 > Date: 2005-07-29 10:08:13 +0100 (Fri, 29 Jul 2005) > > Log message (6 lines): > omindex.cc: add --preserve-nonduplicates / -p option to not delete any > documents that aren't updated, in replace duplicates mode

hallo, I'm indexing a filesystem using omindex, and users can query the database via omega: everything works fine now I'd like to add an option like "search files by name" and I'm wondering how to do this can omega search files by name directly? how should I build the query? could I use scriptindex to index, eg., the locate database? how? should I index file names

Hi all I need a little clarification with regard to Omega's behaviour with 'duplicate' files when running 'omindex'. How is a duplicate recognised? Is it simply by file path? How is an unmodified file detected, if at all? I would like to set up subversion post-commit hook to update my index. If possible I would like to just update the index with the newly commited files.

All, I've run into a couple of things using omega/omindex under cygwin. I don't think I'd attribute them to xapian, omega or omindex, but wanted to get them out to the list so that if anyone else should run into these things down the road, hopefully someone will remember and be able to help. 1) after compiling and building omega, and doing make install, I get a set violation when

Hello :-) Sorry if this question is na?ve and confused; I'm new to Apache configuration. Can Apache be configured to run omega via a file in the conf.d directory rather than a virtual server? I have been using a virtual server on port 80 but now need to run nagios on port 80 too and do not want to ask the users to start using a URL with a non-standard port for omega. KISS. AFAIK omega

I propose making a few changes to the way omega (and omindex) operate. I'm posting these to the list before doing so to check if they'll cause obvious problems for anyone. 1) Configuration handling for omega. Omega has a configuration file, which specifies where databases, templates and logfiles are to be found. It currently looks for this configuration file in its current working

On Thu, 18 Apr 2024 at 06:24, Olly Betts <olly at survex.com> wrote: [ ... ] > Yes - it's in the xapian-omega package you already have installed: > > /usr/lib/cgi-bin/omega/omega Thank you, Mr. Betts. for your replying to my questions. Please consider me a novice and elaborate further, Mr. Betts. > You may need to configure apache to tell it to use this for a URL on

Hi List Is there a good way to generate search term suggestions meant for the user to see? I was thinking using the relevance set and expansion set stuff for this, but since these functions return a lot of Z-prefixed stemmed down versions of words, those results are not always suitable to be presented to the user. Cheers Alec

Finally had a chance to read this - looks great, thanks Jim! I think we can improve it ever so slightly by being a little more explicit at the end: > {{{ > /usr/local/bin/omindex --db /var/lib/omega/data/default > --url /book /var/www/book > }}} [...] > The --url parameter identifies the url prefix that corresponds to > the directory we start indexing from. Since we put the

Dear senior ML members and developers of Xapian Omega, Mr. Olly has helped me cross the bump of the initial learning curve. (ref: https://lists.xapian.org/pipermail/xapian-discuss/2024-April/010034.html) How can I use Xapian Omega directly (i.e., without using `recoll` and `xapiandb`) to index a directory of text files with all strings greater than 3 characters, to create an index text file

OK, I'll try again. Thanks, Jim. -------------- next part -------------- An embedded message was scrubbed... From: Jim Lynch <jwl@sgi.com> Subject: Irix install of omega fails. Date: Mon, 28 Jun 2004 14:16:46 -0400 Size: 2057 Url: http://lists.tartarus.org/pipermail/xapian-discuss/attachments/20040628/212669c1/Irixinstallofomegafails.eml

Hi, I'm using omindex to index files and I want make query with user/group boolean prefix (I*, I at ... and I#...). That work well with "other" and "group" right, but not in all case for "user" right. Here is an example: assume that we have an user "ftp" not in "users" group. If file right are: -rw-r------ 1 ftp users 13 2013-10-06