similar to: omindex and scriptindex question

Hi, I'm experiencing weird behaviour in Xapian/Omega. Here's my situation: * I'm indexing data through scriptindex, the output is as follows: ***************** Replace: 6706476 Replace: 6706477 Replace: 6706478 ***************** Since there is no output after entering several enters, I assume scriptindex is indexing data. * The search I perform on omega is as follows:

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

http://bugs.freedesktop.org/show_bug.cgi?id=26790 Summary: Not center screen Product: xorg Version: unspecified Platform: Other URL: https://bugs.edge.launchpad.net/ubuntu/+source/xserver- xorg-video-nouveau/+bug/529130 OS/Version: All Status: NEW Severity: normal Priority: medium

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

Dear, guys: I am a beginner of Xapian, when reading the documents, I encountered follow questions. (1) I see the Xapian::Document has a method void add_value (Xapian::valueno valueno, const std::string &value) What's the purpose of this method? Document will related to the terms, but what's the purpose of this? (2) add_posting method will add term to a documents. void

Hello, I am using Sarissa v 0.9.7.6 and prototype v 1.5. In ajax application, I am retrieving xml string from a local servlet and displaying it using xslt processing by sarissa. This works perfectly well in FF, however it gives bunch of error in IE. I have posted same type of problem quite few days back and I stopped using Sarissa. Now I need to use Sarissa so any help would be highly

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

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

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

Hello It is possible somehow to give higher priority to recent document. For example, when adding new document to the database, I will add a term that specifies date of the document. During the search, the date of the document is taken into account in the algorithm that calculates document relevancy. In another project I am working on, I would like to limit number of pages returned from 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

I use Omega to index and search an archive of magazine and ebook pdfs etc. I also have a Wiki (in MediaWiki) that I wanted to include in that index too. If it's any use to anybody, I've adapted dbi2omega to export the pages from MediaWiki and shared it on GitHub - search for mediawiki2omega. It doesn't do anything very clever, but it might save someone time figuring out 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

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

Hi all. I have problem compiling xapian php bindings. I am using debian sarge. I have installed php4-dev before compilation. I am getting the following errors: boomer:~/xapian/xapian-bindings-0.9.0# make make all-recursive make[1]: Entering directory `/root/xapian/xapian-bindings-0.9.0' Making all in php4 make[2]: Entering directory `/root/xapian/xapian-bindings-0.9.0/php4' make

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