Maybe I'm missing something (it's late).... but why not just index+store? The
stored value will be the original and indexing can lowercase (as you set it),
so it's case-insensitive.
Also, does this actually work for you:
<tokenizer class="solr.KeywordTokenizerFactory"/>
<filter class="solr.StandardTokenizerFactory"/>
2 Tokenizers?
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
> From: Ian Connor <[EMAIL PROTECTED]>
> To: solr <solr-user@lucene.apache.org>
> Sent: Wednesday, August 6, 2008 8:21:28 PM
> Subject: case preserving for data but not for indexing
>
> In order to preserve case for the data, but not for indexing, I have
> created two fields. One is type Author that is defined as:
>
>
> sortMissingLast="true" omitNorms="true">
>
>
>
>
>
>
>
> and the other is just string:
>
>
> sortMissingLast="true" omitNorms="true"/>
>
> this is used then for the author lists:
>
> omitNorms="true" multiValued="true"/>
>
> stored="true" omitNorms="true" multiValued="true"/>
>
> Is there any other way than to have two fields like this? One for
> searching and one for displaying. People's names can be vary case
> sensitive for display purpose (eg McDonald. DeBros) but I don't want
> people to miss results because they search for "lee" instead of "Lee".
>
> Also, can anyone see danger is using StandardTokenizerFactory for
> people's names?
> --
> Regards,
>
> Ian Connor
