Re: [VuFind-Tech] Facets natural sorting problem in browse catalog ( case insensitive letters and numbers sort )

[Michele M. <m.m...@ci...>]

Il 03/12/2013 19:56, Demian Katz ha scritto:
>
> Yes, that is exactly the problem.
>
> *From:*Joe Atzberger [mailto:jo...@bo...]
> *Sent:* Tuesday, December 03, 2013 1:41 PM
> *To:* Demian Katz
> *Cc:* Michele Meloni; vuf...@li...
> *Subject:* Re: [VuFind-Tech] Facets natural sorting problem in browse 
> catalog ( case insensitive letters and numbers sort )
>
> It has to be that the relationship of stored to indexed values is 
> (potentially) many to one.  How would you display/identify a facet 
> with one stored value when there are 100 different stored values 
> mapping into it?
>
> --joe
>
> On Tue, Dec 3, 2013 at 10:24 AM, Demian Katz 
> <dem...@vi... <mailto:dem...@vi...>> wrote:
>
> I'm not entirely sure why Solr made the decision to only use indexed 
> values for facets -- it's possible it has to do with performance, or 
> else it may be due to the issue that you have to use indexed values to 
> match up identical facets correctly, and since different stored values 
> can yield the same indexed value, there then becomes a problem with 
> determining which value to display. In any case, one other possibility 
> you might consider would be to use a delimited format -- change your 
> pipeline so that it would translate:
>
> my book 1
>
> into:
>
> my book 000001|my book 1
>
> and then have VuFind strip off the text before the | character. Again, 
> not a very pretty solution, but it would help you get away from doing 
> natsort all the time.
>
> - Demian
>
> I don't find the sense to display only indexed values!
> I think that we have too much records to use natsort every time but we 
> can try and see how are performances.
> Thanks!
>
> -- 
>
> LogoCineca
>
> 	
>
> *Michele Meloni*
> Information and Knowledge Management Department
> Digital library Division
> Via R. Sanzio, 4
> 20090 Segrate MI, Italy
> tel. +39 02 26995 320 <tel:%2B39%2002%2026995%20320>
> http://www.cineca.it
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of 
> AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
> _______________________________________________
> Vufind-tech mailing list
> Vuf...@li... 
> <mailto:Vuf...@li...>
> https://lists.sourceforge.net/lists/listinfo/vufind-tech
>
I have done it with separator and now I have a the correct sort.
We have make some change at SolrType to preserve store value in the 
correct way.

<fieldType name="paddedStringWithOri" class="solr.TextField" 
sortMissingLast="true" omitNorms="true">
     <analyzer type="index">
         <tokenizer class="solr.KeywordTokenizerFactory"/>
         <!-- filter class="solr.LowerCaseFilterFactory"/ --><!-- The 
lowercase is made by PaddingFilterFactory -->
         <filter class="it.cineca.solr.analysis.PaddingFilterFactory" 
oriValueSeparator="|#P@P#|" padString="0" totalLength="10"/>
     </analyzer>
     <analyzer type="query">
         <tokenizer class="solr.KeywordTokenizerFactory"/><!-- filter 
class="solr.LowerCaseFilterFactory"/ --><!-- The lowercase is made by 
PaddingFilterFactory -->
         <filter class="it.cineca.solr.analysis.PaddingFilterFactory" 
oriValueSeparator="|#P@P#|" padString="0" totalLength="10"/>
     </analyzer>
</fieldType>

Tnx again
-- 
LogoCineca
	*Michele Meloni*
Information and Knowledge Management Department
Digital library Division
Via R. Sanzio, 4
20090 Segrate MI, Italy
tel. +39 02 26995 320
http://www.cineca.it