Re: [VuFind-General] Any best practices integrating catalogue enrichment with teasers?

[Andreas K. <And...@gm...>]

Hello Andrew,

thanks for your message. Using Solr's highlighting is exactly what I am
planning to do. My main problem at the moment is to display the
highlighting in vufind. And I am not sure if I should use Solr.php or an
implementation of SolrJS.
In Solr.php I cannot find the code stripping off additional fields from
the result sets (the only output seems to be the contents of the
fullrecord-field), and it seems there is no option to activate the
highlighting feature in that class. (I am using 1.0RC 1)

Andreas

Andrew Nagy schrieb:
> Andreas - the best approach for this would be to use the solr
> highlighting feature where you can configure it to pull a "snippet"
> from a specified field.
>
> Let me know if you have any more specific questions about doing this.
>
> Andrew
>
> On 7/28/09, Andreas Kahl <And...@gm...> wrote:
>   
>> Hello everyone,
>>
>> has anyone experience integrating scanned TOCs into a vufind-Search with
>> teaser display? I would be interested if there existed some best
>> practices. Escpecially, I would be very glad to hear wether there are
>> recommendations how to display teasers in vufind's result list and in
>> the record display screen.
>>
>> A short summary about my experiments with that:
>> I got the scanned tocs as pdf and extracted plain text from them. For
>> indexing the texts with their associated Metadata-Documents I use the
>> filenames in the URLs (MARC-Field 856a). I extended VuFindIndexer.java
>> in MarcImporter.jar and added a field 'cecontents' to biblio's
>> schema.xml, which gets filled with the plain text in a custom method.
>> Indexing and Searching works fine and I  adjusted Solr.php to search the
>> additional field if a query is sent via Basic Search.
>>
>> Finally I tried to display teasers, which worked fine using Solr's admin
>> interface. Today, my first try in vufind was to write a Smarty plugin
>> using vufind's Solr.php-class. Unfortunately this class only writes
>> MARC-fields into $result - but I need the highlight-option and my custom
>> cecontents-field (using plain XML-Output didn't help).
>> For tomorrow I am planning to try an implementation using SolrJS written
>> into the output-html via another Smarty-Plugin.
>>
>> Is that a good idea? Do you have other experiences/ideas?
>>
>> Andreas
>>