similar to: omega: omindex behaviour with duplicate files

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. I am writing a python equivalent of omindex (we are using scriptindex currently - but I wanted to use omindex instead, and extend it to work with our internal file format.. BUT did not want to compile code if possible... so anyway). I have tried to keep the code as close to possible to the omindex native code, but am facing a bit of confusion: what exactly is the reason for omindex to take

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

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

Hi, I was researching indexing of text in omindex and scriptindex. While indexing text with omindex.cc possition of terms is saved with gap. This is not happening with scriptindex.cc While this is happening ? Another question is why in omindex.cc the term possition starts with 0 while in scriptindex it starts from 1 ? Code snippet from omindex.cc // Add postings for terms to the document

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, all -- I want to do Plain Old Omindex'ing *but* the mapping between my documents' filenames and the URLs where I hope search users to find them is, uh..., strange. The simplest thing (to me) would be to run omindex for each document, e.g. omindex --no-delete -U /cool-url-1 /funky/doc/file-blah.pdf omindex --no-delete -U /cool-url-7 /doc/funky/ohmy/blah-file.txt ... and so on...

I would really like to try out the features in the patch above. But I can't ever seem to get the resulting omindex.cc to "make". I tried updating to rev 10801 from the SVN then run /bootstrap but then I seem to get errors compiling everything when I try and do "make" (I'm using ubuntu 8.10). So I thought I'd try an apply the patch to the latest stable version

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

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

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

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

Hi, I'm working on the ticket #743 omindex: delay libmagic checks <https://trac.xapian.org/ticket/743>. As the ticket's Description mention, the call to libmagic is expensive than call the stat, so we can check the size by call the stat to get size before call libmagic to get a mime type. But how about the timestamps check? since timestamps check need to iterate the DB to check if

Given a directory tree like ... /foo | +-- A | +-- B | +-- C ... what is the best way to index A and C into a single Xapian database? AFAIK the alternatives are: omindex --db /my_db --no-delete /foo /foo/A omindex --db /my_db --no-delete /foo /foo/B or omindex --db /my_A_db /foo /foo/A omindex --db /my_B_db /foo /foo/B xapian-compact /my_A_db /my_B_db /my_db The first alternative does not

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

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

At wiki page: http://wiki.xapian.org/Omega I added a comment that ht://Dig looks like dead. Does anybody really use it? >From brief glance at docs I had a feeling it is not easy to configure. Maybe better crawler is GNU wget? Mature, stable, maintained? -- Peter Masiar

On Thu, Apr 18, 2024 at 03:46:53PM +0530, Susmita/Rajib wrote: > On Thu, 18 Apr 2024 at 06:24, Olly Betts <olly at survex.com> wrote: > > You may need to configure apache to tell it to use this for a URL on > > your site. > > How Mr. Betts? Suppose I have a ready open document text file, a > LibreOffice text file. say BettsBio.odt, for which I want to create an >

Hi All, I've installed Xapian and the php module. I've set up a script for use with scriptindex and dbi2omega for getting data from the db into the index easily, the script file is as follows: =============================== id : field=id title : index title: field=title description : index description : truncate=50 field=content ============================= However, when querying

Dose Xapian support wildcards (left truncation)? E.g. *ildcard.doc or *.doc or Wild*.doc I read a post from Olly in 2005 that said it wasn't supported yet, I was wonder if there had been any progress or easy work around since. I mainly need when users want to search by the filename extension. Thanks, Frank