Build Multilingual Data in the Mart

Eagle's multilingual capabilities allow you to deliver information with entity and security text data translated into any set of non-English languages, including text that must be stored in the database in multi-byte format such as Japanese and Chinese.

Data that can be multilingual includes:

Entity database fields found, in tables of the type that have companion history tables.
Security database fields found, in tables of the type that have companion history tables.
Text-based meta data, such as field attribute names and grouping rule categories.
Code values.
Static data in the Eagle Portal, such as prompts and error messages.

For additional information about multilingual processing outside of Data Mart, refer to the General Reporting Reference Guide, and the Eagle Portal System Administration Guide.

On this page

1 Load Local-Language Data for Use by Data Mart
2 Languages Table
3 Load Entity Data
4 Load Security Data
5 Load Meta Data Text and Code Values

Load Local-Language Data for Use by Data Mart

Before building local-language data in the Mart, you have to load it to appropriate tables in the Eagle data warehouse. The following sections give an overview of how to do this.

Languages Table

The EGL_LANGUAGES table in the PACE_MASTER database, shipped with V11.0 and later, provides support for your selection of non-English languages, as shown in Sample EGL_LANGUAGES Table. Contact your Eagle Client Operations Manager for assistance in populating this table for the languages you need.

Load Entity Data

To provide entity-related text in a non-English language, you have to create a table in the Eagle warehouse using the name in which your required text field is normally found, with the extension "_ML". This table contains an additional key field L_ID, which is the language instance number from EGL_LANGUAGES.You then use an uploader to populate local-language text to that table for any language you have set up in EGL_LANGUAGES. Eagle ships ENTITY_ML and ENTITY_ML_HIST, containing the field ENTITY_NAME, as a "starter". Your database administrator may add any other text field normally found in ENTITY and ENTITY_HIST to their "_ML" companion tables and upload local-language text. The data type is nvarchar in SQL Server or nvarchar2 in Oracle. Table Supporting Four Languages displays an example of ENTITY_ML with ENTITY_NAME loaded in four languages for one entity.

Load Security Data

You can load security text fields the same as you load entity text fields. Eagle ships SECURITY_MASTER_ML and SECURITY_MASTER_ML_HIST, having key field L_ID, and includes field ISSUE_NAME. You can add and load other security fields using the same logic as for entity tables. Security Analytics tables, which do not have companion history tables, are not supported for local language text in V11.0. SECURITY_MASTER_ML Example shows an example of SECURITY_MASTER_ML.

Load Meta Data Text and Code Values

In the PACE_MASTER database, you can load table EGL_GENERIC_XLATION_ML with local-language text contained in your meta data and code values of Entity and Security fields. You may want to localize this text, since it appears on reports in items such as column headings and group names. To enter this data, use the Eagle Translation Center tool.
Example of Table with Issue Name Field Attribute shows an example of rows of this table loaded with the name of a field attribute, "Issue Name".

Example of Table with Code Values shows the same table loaded with code values for an industry, "Advertising", and an investment type, "Common Stock".