<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
You also need to add a field to the record.<br>
<br>
Terms are what allow a record to be found<br>
Keys are used for maniupations, conditions and sorting during search<br>
Fields are used to retreive per-record text for summaries and things
like for Omega.<br>
<br>
I suggest you look at the scriptindex source code to see what it does.<br>
It makes a good read.<br>
<br>
Sam<br>
<br>
Sig Lange wrote:
<blockquote cite="mid89bf9a4b0503091137ab2ef90@mail.gmail.com"
type="cite">
<pre wrap="">I'm attempting to create a database that's compatible with omega. The
main problem i'm having is getting a URL to appear for my term. I am
using .add_term("U/<uid>") where <uid> is a hex digest. I can ensure
that it's well under the 240 term length limit. I used
xapian.Database.all_termsbegin() and listed the terms, they are infact
there. When I search in omega however, I don't get a URL at the
bottom, as if I were using omindex or scriptindex. Is there other
fields this depends on? What are some possible reasons. I've gone
through the omindex.cc source and generated url related terms as well
thinking there was a dependancy type situation. I've had no success
with that however. I am using python and .add_term(),I've attached the
source of my indexing script if anyone is interested.
Thank You.
</pre>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Xapian-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Xapian-discuss@lists.xapian.org">Xapian-discuss@lists.xapian.org</a>
<a class="moz-txt-link-freetext" href="http://lists.xapian.org/mailman/listinfo/xapian-discuss">http://lists.xapian.org/mailman/listinfo/xapian-discuss</a>
</pre>
<pre wrap="">
<hr size="4" width="90%">
This message has been 'sanitized'. This means that potentially
dangerous content has been rewritten or removed. The following
log describes which actions were taken.
Sanitizer (start="1110397131"):
Part (pos="2743"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
Match (rule="default"):
Enforced policy: accept
Part (pos="3693"):
SanitizeFile (filename="iEmail.py", mimetype="application/octet-stream"):
Match (rule="default"):
Enforced policy: accept
Defanged UNIX shell script(s).
Part (pos="7625"):
SanitizeFile (filename="unnamed.txt", mimetype="text/plain"):
Match (rule="default"):
Enforced policy: accept
Total modifications so far: 1
Anomy 0.0.0 : Sanitizer.pm
$Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $
</pre>
</blockquote>
<br>
</body>
</html>