MuseKnowledge™ Application Translation Features: Requirements and Configurations
The following elements that use text translations into a specific language are available in the MuseKnowledge Application:
- Query Translation
- Search Result Translation
All text translation functions in Muse are currently implemented using the Microsoft Cognitive Services. Thus the requirement is to have a Microsoft Azure Subscription in which to create a Translator service which will be used by the Muse translation features. (see below more details for setting up a Microsoft Translator Service)
Azure Translator is a cloud-based machine translation service that is part of the Azure Cognitive Services family of REST APIs. Azure resources are instances of services that you create. All API requests to Azure services require an endpoint URL and a read-only key for authenticating access.
A tutorial for creating a Translator resource in the Azure portal is available here:
When done creating the Translator resource, copy the API Keys and Endpoint values to be configured in Muse. The API Keys and URLs are available in the Keys and Endpoint section in the Azure Portal:
Muse Query Translation is available starting with MuseKnowledge Application version 7.2, release date June 2019.
More details about Muse Query Translation are available in the MuseKnowledge™ Application 8.0 article.
The Query Translation functionality should be already enabled in the MuseKnowledge Application. To ensure the proper configuration, the following items must be verified, enabled and configured if not already:
- Access the Muse Console for Applications Administration (MCAA), select the Muse Application and access the Application General Settings left menu item, Interface Options, Functionality tab and make sure the Enable Query Translation flag is set to yes.
- Check that the TranslatedQueriesMS Muse Source Package (SP) is installed in the application and configured with the MS Azure Translator API key. Edit its configuration in MCAA, (select the Source Package and access Edit Source Advanced Configuration) and in the Custom Parameters place the API key as obtained from the Azure portal as value for the API_KEY metavariable.
- Check that the TranslatedQueriesMS Muse Source Package is part of a Sources Group, by accessing in MCAA the Organize Sources -> Source Grouping section. If not, create a new group in which add the TranslatedQueriesMS SP.
- Check that the Source Group from the previous point #3 is of type Query Translation. Access in MCAA the Organize Sources -> Update Interface section and in the groups listing select as Group Type the Query Translation option.
- Test the TranslatedQueriesMS SP in MCAA in the Test Source(s) section with a query in a different language, other than English which is the default language.
Search Result Translation
The Search Result Translation functionality is available starting with MuseKnowledge Application version 8.4, release date June 2022.
More details about Search Result Translation are available in the Muse Release 220.127.116.11 news article.
Muse Search Result Translation should be already enabled in the MuseKnowledge Application. To ensure the proper configuration, the following items must be verified, enabled and configured if not already:
- Access the Muse Console for Applications Administration (MCAA), select the Muse Application and access the Application General Settings left menu item, Interface Options, Functionality tab and make sure the Enable Record Translation flag is set to yes.
- In MCAA, select the Muse Search Application and access the Application Modules -> Translator Keys left menu. Make sure the MicrosoftTranslator key is installed, edit its configuration file (
Translator Module: MicrosoftTranslator Properties: Configuration File) and in the Connection Parameters section, API Key input add the API key as obtained from the Azure portal.