: Hoss, I think the use case being asked about is specifically doing a : facet.sort though, for cases where you actually do want to sort facet values : with facet.sort, not sort records -- while still presenting the facet values : with original case, but sorting them case insensitively.
Ah yes ... thank you, i did in fact missunderstand the question. : Because I'm pretty sure there isn't really any good solution for this, Solr : just won't do that, just how it goes. correct. the facet constraint values come from indexed terms, and the terms are what get sorted by facet.sort -- if you want to "collapse" some terms down so they are equivilent (ie: "Foo" and "foo" and "foo " are treated identical) then that's what you get back. if your goal is just to have "pretty" values, you can use things like the CapitalizationFilter, but if you need a particularly complex analyzer for your values in order for them to sort a certain way, you can't then get back the original pre-analyzed values. One way people deal with this typ of situation, is to index identifers for their facet constraints, and then their UI uses those ids to lookupthe display value (ie: index categoryId, display categoryName) ... this has the added benefit of allowing you to change category names w/o re-indexing. -Hoss
