Yes, let the 'service layer' solve this, in our case our JS-interface does this job. Internal (in Lucene) values for field MIME-type are e.g. application/pdf and text/html. In the interface layer, which is JS, those values are mapped to Web page, Webpagina or PDF document, PDF-document, and more languages. Same same is true for our language selection facet, internal they are ISO (en, de, fr, nl etc) but are mapped to any format desired by the customer, usually the name language of the name of that very language.
Re: 64 bits payload, thanks, that gives me 57 additional bits to encode language features into our text! -----Original message----- > From:Webster Homer <webster.ho...@sial.com> > Sent: Wednesday 23rd August 2017 22:21 > To: solr-user@lucene.apache.org > Subject: Re: Facet on a Payload field type? > > The payload idea was from my boss, it's similar to how they did this in > Endeca. > I'm not sure I follow your idea about "mapping internal value to translated > value". Would you care to elaborate? > My alternate idea is to have sets of facet fields for different languages, > then let our service layer determine the correct one for the user's > language, but I'm curious as to how others have solved this. > > On Wed, Aug 23, 2017 at 2:10 PM, Markus Jelsma <markus.jel...@openindex.io> > wrote: > > > Technically they could, facetting is possible on TextField, but it would > > be useless for facetting. Payloads are only used for scoring via a custom > > Similarity. Payloads also can only contain one byte of information (or was > > it 64 bits?) > > > > Payloads are not something you want to use when dealing with translations. > > We handle facet constraint (and facet field) translations just by mapping > > internal value to a translated value when displaying facet, and vice versa > > when filtering. > > > > -----Original message----- > > > From:Webster Homer <webster.ho...@sial.com> > > > Sent: Wednesday 23rd August 2017 20:22 > > > To: solr-user@lucene.apache.org > > > Subject: Facet on a Payload field type? > > > > > > Is it possible to facet on a payload field type? > > > > > > We are moving from Endeca to Solr. We have a number of Endeca facets > > where > > > we have hacked in multilangauge support. The multiple languages are > > really > > > just for displaying the value of a term internally the value used to > > search > > > is in English. The problem is that we don't have translations for most of > > > our facet data and this was a way to support multiple languages with the > > > data we have. > > > > > > Looking at the Solrj FacetField class I cannot tell if the value can > > > contain a payload or not > > > > > > -- > > > > > > > > > This message and any attachment are confidential and may be privileged or > > > otherwise protected from disclosure. If you are not the intended > > recipient, > > > you must not copy this message or attachment or disclose the contents to > > > any other person. If you have received this transmission in error, please > > > notify the sender immediately and delete the message and any attachment > > > from your system. Merck KGaA, Darmstadt, Germany and any of its > > > subsidiaries do not accept liability for any omissions or errors in this > > > message which may arise as a result of E-Mail-transmission or for damages > > > resulting from any unauthorized changes of the content of this message > > and > > > any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its > > > subsidiaries do not guarantee that this message is free of viruses and > > does > > > not accept liability for any damages caused by any virus transmitted > > > therewith. > > > > > > Click http://www.emdgroup.com/disclaimer to access the German, French, > > > Spanish and Portuguese versions of this disclaimer. > > > > > > > -- > > > This message and any attachment are confidential and may be privileged or > otherwise protected from disclosure. If you are not the intended recipient, > you must not copy this message or attachment or disclose the contents to > any other person. If you have received this transmission in error, please > notify the sender immediately and delete the message and any attachment > from your system. Merck KGaA, Darmstadt, Germany and any of its > subsidiaries do not accept liability for any omissions or errors in this > message which may arise as a result of E-Mail-transmission or for damages > resulting from any unauthorized changes of the content of this message and > any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its > subsidiaries do not guarantee that this message is free of viruses and does > not accept liability for any damages caused by any virus transmitted > therewith. > > Click http://www.emdgroup.com/disclaimer to access the German, French, > Spanish and Portuguese versions of this disclaimer. >
