I think depends on what you need: 1) Simple,unique category - use display facet 2) Categories may be duplicate from display perspective (eg authors) : store display#id in facet field but show only display 3) Internationalization requirements - store I'd but have ui pull and display the translated labels
On 8/9/10, Frank A <fsa...@gmail.com> wrote: > What I meant (which I realize now wasn't very clear) was if I have > something like categoryID and categorylabel - is the normal practice > to define categoryID as the facet field and then have the UI layer > display the label? Or would it be normal to directly use > categorylabel as the facet field? > > > > On Mon, Aug 9, 2010 at 6:01 PM, Otis Gospodnetic > <otis_gospodne...@yahoo.com> wrote: >> Hi Frank, >> >> I'm not sure what you mean by that. >> If the question is about what should be shown in the UI, it should be >> something >> pretty and human-readable, such as the original facet string value, >> assuming it >> was nice and clean. >> >> Otis >> ---- >> Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch >> Lucene ecosystem search :: http://search-lucene.com/ >> >> >> >> ----- Original Message ---- >>> From: Frank A <fsa...@gmail.com> >>> To: solr-user@lucene.apache.org >>> Sent: Mon, August 9, 2010 5:19:57 PM >>> Subject: Facet Fields - ID vs. Display Value >>> >>> Is there a general best practice on whether facet fields should be on >>> "IDs" or "Display values"? >>> >>> -Frank >>> >> > -- Sent from my mobile device
