similar to: GSoC 2016: Text-Extraction Libraries in Omega

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

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

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

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

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

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

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

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

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

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

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

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

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 >

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:

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

I've now got working (but not necessarily policy compliant) debian packages for xapian-core, the xapian python bindings, and omega and omindex. I will be sorting out a public apt repository of these shortly. Is it appropriate to add the debian control files (ie, those files in the debian directories in CVS) to the distribution tarballs? I think yes - they don't take up much space,

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

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

James, That was exactly the issue. libmagic.dll.a was in /lib under cygwin. Adding a -L/lib took care of this. This was also an issue with -lpcre, which adding -L/lib fixed as well. Of course, I'm now running up against something else. from make libtool: link: g++ -fshow-column -Wall -W -Wredundant-decls -Wpointer-arith -Wca st-qual -Wcast-align -Wno-long-long -Wformat-security