You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-dev@jakarta.apache.org by Ma...@softwareag.com on 2004/02/27 13:14:31 UTC

Extract

Hi Daniel,

in Extract you handle the content as InputStream. What about treating as Reader? The extractor should create character data .

Best regards,
Martin

__________________________
Martin Wallmer
Research & Development
Software AG    ++49 6151 92 1831
Uhlandstr. 12
D 64297 Darmstadt


RE: Extract

Posted by Martin Wallmer <Ma...@t-online.de>.
Hi Daniel,



> -----Original Message-----
> From: daniel.florey@web.de [mailto:daniel.florey@web.de]
> Sent: Freitag, 27. Februar 2004 14:11
> To: Slide Developers Mailing List
> Subject: Re: Extract
>
>
> Hi Martin,
> I'm not at work today, but I checked in some nonsense regarding the
> extractors, so I'll change it on monday:
> - The extractor should be separated into two different interfaces:
> PropertyExtractor: Will be called before content is stored to extract
> additional properties from content. This can be used to extract metadata
> from gif or author from office documents etc.
> ContentExtractor: Will be called before content is indexed. Can be used to
> extract the searchable content in plain text from pfd, word etc.

Great! It should be up to the extractor implementor, if it needs to run
thru the content once or twice to get content AND properties.

> I will change the configuration in Domain.xml, so that indexer and
> extractors can be defined in a separate section and can be referenced from
> the store or event section, ok?

Yes!

> Regards,
> Daniel
>
>

Have a nice weekend!

Regards,
Martin


---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org


Re: Extract

Posted by Daniel Florey <da...@web.de>.
Hi Martin,
I'm not at work today, but I checked in some nonsense regarding the
extractors, so I'll change it on monday:
- The extractor should be separated into two different interfaces:
PropertyExtractor: Will be called before content is stored to extract
additional properties from content. This can be used to extract metadata
from gif or author from office documents etc.
ContentExtractor: Will be called before content is indexed. Can be used to
extract the searchable content in plain text from pfd, word etc.
I will change the configuration in Domain.xml, so that indexer and
extractors can be defined in a separate section and can be referenced from
the store or event section, ok?
Regards,
Daniel


----- Original Message -----
From: <Ma...@softwareag.com>
To: <sl...@jakarta.apache.org>
Sent: Friday, February 27, 2004 1:14 PM
Subject: Extract


Hi Daniel,

in Extract you handle the content as InputStream. What about treating as
Reader? The extractor should create character data .

Best regards,
Martin

__________________________
Martin Wallmer
Research & Development
Software AG    ++49 6151 92 1831
Uhlandstr. 12
D 64297 Darmstadt





---------------------------------------------------------------------
To unsubscribe, e-mail: slide-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-dev-help@jakarta.apache.org