I18n Item Transformation
Copyright ©
Mindbreeze GmbH, A-4020 Linz, 2020.
All rights reserved. All hardware and software names used are brand names and/or trademarks of their respective manufacturers.
These documents are strictly confidential. The submission and presentation of these documents does not confer any rights to our software, our services and service outcomes, or any other protected rights. The dissemination, publication, or reproduction hereof is prohibited.
For ease of readability, gender differentiation has been waived. Corresponding terms and definitions apply within the meaning and intent of the equal treatment principle for both sexes.
Introduction
Mindbreeze offers metadata internationalization. To do this, the I18n Item Transformation plugin is used for indexing.
I18n Item Transformation plugins
To use internationalization, the I18n Item Transformation plugin must be added to your Mindbreeze installation by loading the corresponding plugin (the Item Transformation Services are delivered with the package “Mindbreeze Item Transformation Plugins“).
The plugin also has to be included in your Mindbreeze license.
Installation
- Install the plugin using the UI Manager
Configuration
- Enable the plugin for each desired index using the UI Manager:
- Go to the “Indices” tab and activate “Advanced Settings”
- Scroll down to the section “Item Transformation Services“
- Select the “I18n Item Transformation” plugin and click “Add”
- Under Resource Settings, click the plus icon for I18n Property.
- Property Name: the name of the metadata for which the internationalization is to be carried out.
- I18n Resource Directory: the directory in which the translation files are located. The name of the file defines the language, e.g. de.csv or en.csv. All files in a directory must have the same format.
- I18n Resource Format: the file format of the translation files.
- CSV: The first column contains the metadata values and the second column contains the corresponding translations. For example:
404; not found
401; not authorized
- JSON: This file consists of a list of JSON keys/value pairs. For example:
{
"404": "Not found",
"401": “Not authorized"
}
For the changes to take effect, a re-indexing or a complete inversion of the index must be performed after configuration.
Notes for Default Metadata
It is not directly possible to transform "default metadata" like title or extension. Other metadata specific to a connector (e.g. color or path) will work directly.
If standard metadata is to be transformed, we recommend the following workaround: A "Precomputed Synthesized Metadatum" must be created in the index, which is then used for transforming. For example, for the standard metadata extension, a Precomputed Synthesized Metadata with "Name": transform_extension and "Property Expression": extension can be added. Then, when configuring the I18nItemTransformation plugin, the Precomputed Synthesized Metadatum "Property Name" must be set with value transform_extension.