similar to: omega with samba share

From the documentation I've read, omega can read from multiple databases, but I'm not sure how to go about this. I have three databases created using omindex, currently located at /var/lib/xapian-omega/data/share, /var/lib/xapian-omega/data/users, and /var/lib/xapiax-omega/data/management The quickstart guide says that in omega.conf database_dir should point to the directory

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

I'm finding that omindex is consistently ending prematurely when indexing certain files. The last output looks like this: [Entering directory /compounds/Acetic_acid] Indexing "/MATLAB/compounds/Acetic_acid/AACID_50T.TXT" as text/plain ... added. Indexing "/MATLAB/compounds/Acetic_acid/AACID_50T.pdf" as application/pdf ... "pdftotext -enc UTF-8

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.

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

I am confused about using term prefixes for omega searches. There are a number of term prefixes that are reserved and used by omindex. In order to use those for searching with omega, do I need to use the $setmap{} function in the omega template or are the reserved ones built in? -- Chris Purves Visit my blog: http://chris.northfolk.ca "I can't have a lobotomy just because I've

Dear all, I am a newbie to Xapian-Omega. I installed Xapian-Omega (1.2.14) a few days ago on my freebsd NAS server, and intend to use it to search my CIFS/SMB share. So far it works fine (I am able to search my share using the omega web interface), nevertheless I have few newbie questions. Hoping that somebody can answer my (hopefully not to silly) newbie questions. Indexing file names:

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

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

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

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

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

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

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

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

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

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

> -----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: