How global support for editorial search helps customers
This document guides you through the process of deciding if a language-specific analyzer is suitable for your organization. It also explains how to configure your sites in Arc XP Site Service, including the need to segment sites by language to leverage language-based search capabilities. Here are scenarios where using a language-specific analyzer can lead to more relevant story matches and improve the search experience in Composer:
Language group | Searching in Composer | Language-specific analyzer fit and site setup |
|---|---|---|
Your organization operates one site in non-Latin-based languages, with content generated in languages like Arabic. | Editorial users rely heavily on searching by term in Composer | Using a language-specific analyzer is a good choice. You can configure your site specifically for the Arabic language. |
Your organization operates multiple sites in non-Latin-based languages and content is generated in languages like Arabic, Russian, or Hindi. | Editorial users rely heavily on searching by term in Composer | Using language-specific analyzers is a good choice. You can organize your sites by segmenting them into one site per language, such as Arabic, Russian, and Hindi. |
Your organization operates multiple sites in character-based languages and content is generated in character-based languages like Traditional Chinese (zh-Hant), Simplified Chinese (zh-Hans), and so on. | Editorial users rely heavily on searching by term in Composer | Using language-specific analyzers is a good choice. You can organize your sites by segmenting them into one site per language, such as Traditional Chinese (zh-Hant) and Simplified Chinese (zh-Hans). |
Your organization operates multiple sites in Latin-based languages and content is generated in languages derived from Latin such as English, Spanish, Portuguese, and so on. | Editorial users rely heavily on searching by term in Composer | Using language-specific analyzers is an good choice. You can organize your sites by creating one site per language, such as Spanish, Portuguese, and English. English can be set up with the default analyzer. |
Your organization operates sites in English and they create content only in English. | Editorial users rely heavily on searching by term in Composer | No need for language-specific analyzer because the default analyzer is a great choice. |
If your organization could benefit from using a language-based analyzer based on the criteria in the table, we strongly recommend starting discussions with Arc XP at your earliest convenience. Here's a simple guide on how to begin:
Check the Languages supported in Arc XP.
Determine if any of the out-of-the-box (OOTB) language analyzers are suitable for your organization's needs, requiring minimal effort from your end.
Collaborate with your Arc XP Customer Enablement partner to outline the list of out-of-the-box (OOTB) language analyzers required for your sites. They guide you through this process.
If your organization requires support for a language not currently supported by Arc XP, you have the option to provide a custom language analyzer for one or more sites through Bring Your Own Analyzer (BYOA). For more information on BYOA, see Bring Your Own Analyzer (BYOA)
Whether you opt for OOTB analyzers or BYOA, your Arc XP CE partner handled the provisioning process to ensure your desired language-based analyzer is set up in your Arc XP Sandbox and Production environments.
A typical scenario for language-based analyzers
Scenario: You're an organization joining Arc XP, and you manage multiple sites, each in a different language.
Language setup
Site A: English
Site B: French
Arc XP environment setup
Site A is configured with the default analyzer.
Site B is configured with the French analyzer.
Content indexing
Content migration and authoring new content: You begin creating stories in Arc XP using either the Draft API or Composer.
Arc XP indexes natural language fields based on the language associated with the site where the content is published.
Search experience
When users log in to Composer and perform searches, the following search experiences occur:
Example 1: Searching in Site A (English)
Query: Searching for the English keyword "dog"
Result: Both "dog" and "dogs" are returned because the default analyzer understands English synonyms.
Example 2: Searching in Site B (French)
Query: Searching for the English keyword "dog"
Result: Only an exact match for "dog" is returned because there are no synonyms or rules for "dog" in French.
Example 3: Searching in Site B (French)
Query: Searching for the French term "chien"
Result: Stories containing "chienne" and "chiennes" are returned because the French analyzer recognizes synonyms in French.
Example 4: Searching in Site A (English)
Query: Searching for the French term "chien"
Result: Only an exact match for "chien" is returned because there are no synonyms or rules for "chien" in English.