Linguistic search and sort

You can configure PolicyCenter to perform search and sort operations in languages other than the default en_US. PolicyCenter provides support for language-appropriate text search and sort for a single language.

Note: The base configuration of PolicyCenter provides free text search only in United States English. You must configure Guidewire Solr Extension to be able to perform free text searches in languages other than United States English. This configuration requires expertise in configuring Apache Solr. For information on basic configuration of free-text search, see Free-text search configuration.

Understanding linguistic search and sort of character data

There are two primary ways to search for and sort character data:

  • Treat the character data as binary code points and compare and sort the data numerically.
  • Treat the character data linguistically. This approach applies specific collation rules to order words in a list that reflect the commonly accepted practices and expectations for a particular language.

Linguistic search applies a specific collation to the character data. A collation is an overriding set of rules that applies to the ordering and comparison of the data. Collation strength refers to the elements of the collation process that the search and sort code applies to the data.

For example:

  • Collation strength controls whether the search and sort code respects or ignores differences in case and accent on a character, such as the leading character on a word.
  • In the Japanese language, collation strength also controls whether the search and sort code respects or ignores the differences between:
    • Katakana and Hiragana
    • Full-width and half-width Katakana character differences

PolicyCenter uses the value of configuration parameter DefaultApplicationLocale and the language_languageCode.xml and collations.xml configuration files to implement localized search and sort functionality.

Note: PolicyCenter displays the default locale value when the current locale value is missing. However, PolicyCenter always sorts by the current locale value. As a result, sorting of a localized column of a list view can appear to be broken when the column has one or more untranslated values.