On Mon, 14 Aug 2000, Jimmie Houchin wrote:
> I may be clueless and out of my league here and I haven't read the
> sources so I don't know... Well enough of a disclaimer. :)
I *have* read the ZCatalog/SearchIndex sources, but I don't understand
this part of it yet (or really that much of it at all
Hello,
I may be clueless and out of my league here and I haven't read the
sources so I don't know... Well enough of a disclaimer. :)
Is there anything in there which can provide the seek or byte position
of the hit within text object? If so, it shouldn't be too difficult to
read X bytes before a
Hello,
I may be clueless and out of my league here and I haven't read the
sources so I don't know... Well enough of a disclaimer. :)
Is there anything in there which can provide the seek or byte position
of the hit within text object? If so, it shouldn't be too difficult to
read X bytes before a
Hi Toby
> If you really do have a 67 page document,
For the sake of the argument, that was page 67 of a 149-page
document ..
> it would be better to store each page in its own ZODB
> object, and index each page individually.
Well, the number of pages depends on the formatting .. but it
migh
On Mon, 14 Aug 2000 13:04:49 +0100, Chris Withers <[EMAIL PROTECTED]>
wrote:
>Jean Jordaan wrote:
>> I've already got a pretty structured-text "Abstract" field
>> that tells about the document, but I'd like to *see* the
>> sentence on page 67 or wherever in a document where my
>> term matches, so
Jean Jordaan wrote:
>
> Dunno if Catalog can do it either .. not even if I do include the
> fulltext in the MetaData Table. 'Cause the hit will have come
> from the indexed text, so it has no way of knowing *which* hit in
> the original fulltext it was .. right?
Yeah, but there may be some undoc
Dunno if Catalog can do it either .. not even if I do include the
fulltext in the MetaData Table. 'Cause the hit will have come
from the indexed text, so it has no way of knowing *which* hit in
the original fulltext it was .. right?
--
jean
___
Zope
Jean Jordaan wrote:
> I've already got a pretty structured-text "Abstract" field
> that tells about the document, but I'd like to *see* the
> sentence on page 67 or wherever in a document where my
> term matches, so I know whether it's mentioned in passing
> or really important ..
erk... that's a
Hi Geir
> make a pythonmethod that returns the first 200 letters or
> something of the text ,
I've already got a pretty structured-text "Abstract" field
that tells about the document, but I'd like to *see* the
sentence on page 67 or wherever in a document where my
term matches, so I know whe
on Monday, August 14, 2000 Jean Jordaan wrote :
JJ> This works great, but returns only the
JJ> found objects and the cached properties specified in the
JJ> MetaDate Table.
JJ> Wouldn't it be great to be able to give just a line or two
JJ> of context from the full text, the way Google does?
Hi all
I've got a lot of Word docs and Powerpoint presentations
and PDFs etc in the ZOBD, stored with their full text in
a property of the containing object, so that all those binary
docs are searchable. This works great, but returns only the
found objects and the cached properties specified in
11 matches
Mail list logo
