Language scenario

This scenario describes how the glossary administrator can set languages to fit the needs of your organization and individual users.

Your organization has offices in Spain, Germany, Britain, and France. Each country has its own categories and terms. Some categories and terms are needed by all countries. Similarly, each country has its own information governance policies and rules because of its unique regulatory requirements. Some policies and rules are needed by all countries.

The glossary assets of all offices are in a single instance of IBM® InfoSphere® Information Governance Catalog. Most users need to see glossary assets only in their preferred language. Similarly, most users want to see the InfoSphere Information Governance Catalog user interface in their preferred language. You enable each user to select multiple languages for glossary asset content, and only one language for the user interface. Executives might need to see glossary assets from several countries. You can create a query to show the multilingual values.

Users might need to see derived assigned assets for terms. Derived assigned assets are assigned assets of assets that are translated and whose Translations field is defined.

The following scenario shows how the glossary administrator sets up the language definitions for the InfoSphere Information Governance Catalog user interface and for the glossary asset content:

Set up multilingual support for glossary assets
A user with the Information Governance Catalog Glossary Administrator role goes to the Administration page and opens the Language Setting page. The administrator clicks Yes for multilingual support, and then selects Spanish, German, English, and French.
Set up support for the user interface of InfoSphere Information Governance Catalog
The administrator wants to enable each user to select which language to see the user interface in. In the Language Setting page, the administrator expands User Interface Languages, and then clicks Yes.
Confirm language setting updates
The administrator clicks the Language Settings icon in the top menu bar. The administrator sees a list of languages that each user can select for the user interface language, and the four languages that the user can select for the glossary assets display.

Example of language settings and terms

A data architect in Spain views glossary terms in Spanish. The architect adds a German term to the Translation list. The architect then assigns the Spanish term to a database column. A data architect in Germany queries glossary assets to find any terms in German whose translated version was modified. The query detects the Spanish term. The German data architect notes that the Spanish term is assigned to a database column.

Thomas, the senior data architect for your organization, defines the term Gold_Customer for each language and assigns each of the terms to its translated counterpart. Thomas defines the following terms:

Table 1. The Details page of each term
Term name	Value in Header > Language field	Has assigned assets	Terms in General Information > Translations list
Gold_Customer	English		Gold_Kunden Cliente_de_oro Client_d_or
Gold_Kunden	German		Gold_Customer Cliente_de_oro Client_d_or
Cliente_de_oro	Spanish		Gold_Customer Gold_Kunden Client_d_or
Client_d_or	French	GSTAT_CUST	Gold_Customer Gold_Kunden Cliente_de_oro

Pierre, a data architect in the French office, configured the user interface and the glossary asset content to be in French. The governance team directs Pierre to assign the database column GSTAT_CUST to the term Client_d_or.
Raoul, a data architect in the German office, configured the user interface to be in German and the glossary asset content to be in German, English, Spanish, and French. Raoul queries the catalog to find all German terms whose translated versions were modified within the last 24 hours. Raoul finds that the French version, Client_d_or, was modified.
Raoul edits the Details page of Gold_Kunden, and then expands General Information. The translated versions are shown in the Translations list. He expands Assigned Assets. He notes that the database column GSTAT_CUST is assigned to the French term Client_d_or. GSTAT_CUST is a derived assigned asset because GSTAT_CUST is not directly assigned to Gold_Kunden.

Example of language settings and rules

A data architect in Spain views information governance rules in Spanish. The architect adds a German rule to the Translation list. The architect then assigns the Spanish rule to govern a database column asset. A data architect in Germany queries information governance rules to find any rules in German whose translated version was modified. The query detects the Spanish rule. The German data architect notes that the Spanish rule is assigned to a database column.

Thomas, the senior data architect for your organization, defines the rule Age must be valid for each language and assigns each of the rules to its translated counterpart. Thomas defines the following rules:

Table 2. The Details page of each information governance rule
Rule name	Value in Header > Language field	Has governed assets	Rules in General Information > Translations list
Age must be valid	English		Alter muss gültig Edad debe ser valido L'age doit etre valide
Alter muss gültig	German		Age must be valid Edad debe ser valido L'age doit etre valide
Edad debe ser valido	Spanish		Age must be valid Alter muss gültig L'age doit etre valide
L'age doit etre valide	French	GSTAT_CUST	Age must be valid Alter muss gültig Edad debe ser valido

Pierre, a data architect in the French office, configured the user interface and the glossary asset content to be in French. The governance team directs Pierre to assign the database column GSTAT_CUST to the information governance rule L'age doit etre valide.
Raoul, a data architect in the German office, configured the user interface to be in German and the glossary asset content to be in German, English, Spanish, and French. Raoul queries the catalog to find all German rules whose translated versions were modified within the last 24 hours. Raoul finds that the French version, L'age doit etre valide, was modified.
Raoul opens the Details page of the rule Alter muss gültig, and then expands General Information. The translated versions are shown in the Translations list. He expands Governs Assets, and notes that the database column GSTAT_CUST is assigned to the French rule L'age doit etre valide.