similar to: Omega datevalue search fails during scriptindex flush

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 am trying to use datas written in the stdin to run scriptindex, (I am working with Windows and not Unix). And Scriptindex does not work, the database is created but the datas are not indexed. Thanks by advance Stephane

Hi I am a beginner with Xapian. I am trying to use scriptindex but I get some problems : 1) If my script file is empty I have an indexation by default, and I get two output fields when I am using quest.exe (These fields are caption and sample) 2) I then tryed to not use an empty script file defining this time my own fields, but if I use quest to perform researches these fileds does not appear in

James, thanks for the explanations. I misread the notes. As an exercise, I'm trying to convert an existing project that currently uses Scriptindex and Omega to direct Xapian API calls. I did a (I think) complete dump of a document with delve -r 565 -d database and I see things like subject='A typical subject' with a corresponding set of terms like Sa Stypical Ssubject Which

Hi all, I´ve been developing a search application using Xapian and Omega. When our visitors search on specific keywords it´s noticable that Omega is case sensitive. It will find results on keyword `Asus´ and it will NOT find results on keyword ´asus´. I´ve been looking through the documentation to find a CGI param to turn this

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

Hi people I'm running Xapian (1.0.9) and more specifically omega to index a few different databases. After the databases are first indexed (by user A), the dirs get chmod'ed to 0777 to allow user B full access to them. Even after the indexing is done, the file "flintlock" still exists in all database dirs. It's owned by user A (perm: -rw-------). When user B wants

OK, I'm indexing my data with the scriptindex. I want to be able to restrict the search by the category field. Do I need to do anything to the data itself? Like, literally prefix it with the characters "XC"? Below is my indexor for scriptindex and the my php code... document_id : field=ref unique=Q boolean=Q search_id : field=document_id index=S document_title : field=title

Hi, I've tried to follow all helpful tips I've found in the mailing-list and I've applied these two utf-8 patches; http://article.gmane.org/gmane.comp.search.xapian.general/2324 http://article.gmane.org/gmane.comp.search.xapian.general/1927 Now the QueryParser works as I wants it to do, and creates the terms correctly. But sadly I can't find any documents. If I do this; $ quest

Morning All, I use scriptindex to build my database and the PHP bindings to pull it all out. Is it possible to have more than one index but select what the bindings search on? So at the moment I index property addresses, I would also like to index property descriptions for more advanced searching but only as an optional extra...probably in an extra search box. Also I would like to analyse the

Hi, Currently Omega/scriptindex supports filtering by date. For example, all dates between START and END. Would it be possible to extend this behaviour to include the time? We have documents which expire. In order to filter out 'old' articles, we would like to check if the document date is between START=NOW and END=MAXINT. Best regards, Eric

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

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 wrote: > I think it's a bug. Or at least QueryParser uses a rather delicate rule > for when to add a ":" between the prefix and the term, which scriptindex > doesn't implement. The rule is undocumented (except in the code) so > it's arguable who is correct. I've been looking at this some more. We need some way to distinguish the term prefix from the term

Currently I have the following indexscript: pid : unique=Q boolean=Q field=pid postdate : field=startdate author_name: unhtml boolean=XAUTHORNAME field=author author_id: boolean=XAUTHORID field=authorid url : field=url sample : weight=1 index field=sample How can I create the same indexing using PHP? With this, I can get an searchable index, but I have no idea how to set the fields, so that I

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 am fairly confident that these issues are related to killing the scriptindex process ungracefully causing blocks that were queued for writing to disk to not get written. I mention to send you the file because it could be that you would see almost immediately with the situation is. Thanks > ----- Original Message ----- > From: oscaruser@programmer.net > To:

Hello :-) There was probably no good reason to do this build but the Debian 6.0 Squeeze repo version was 1.2.3, we needed 1.2.4 and I didn't think of using the package from unstable. Arch: x86_64 Platform: Linux 2.6 Debian 6.0 (Squeeze) Compiler: gcc version 4.4.5 (Debian 4.4.5-8) Version: 1.2.4 Status: no known problems Source: http://oligarchy.co.uk/xapian/1.2.4/xapian-core-1.2.4.tar.gz

Hi, I've been disappointed today with some of my Xapian results. Here is the issue : - I am searching for the terms "ipod vid?o 60" (with the OR operator) - the first results sorted by relevance are : (name / description) 1. Etui en cuir Shinnorie EZgoing pour iPod avec vid?o 60 Go - Blanc Etui en cuir Shinnorie EZgoing pour iPod avec vid?o 60 Go - Noir - With the SA1