Managing Translations

For the purpose of administration and reporting, for the various codes, translations for different languages need to be maintained. These are done using the object LOCALE_KEY_VALUE. The definition of this Object in the Canvas schema is provided in the following table:

Column Name	M / O	Type	Purpose
KEY	M	String	This is the key that needs to be translated.
LANG_ID	M	String	This is the language ID for which the translation is maintained. The language ID respected by Canvas is in the form of the Language + Country code convention – mm_NN, where mm is the 2 character language code in lowercase, and NN is the 2 character country code in uppercase.
DEFINITION	M	String	This is the key (similar to the resource bundle name in Java) under which all the translations are maintained.
LOCALE_VALUE	M	String	This is the translated value for the provided KEY in the LANG_ID.

From the entitlements framework perspective, entries needs to be maintained under the following definitions for the product, sub product and function code as appropriate:

DEFINITION	Purpose
PORTAL_PRODUCT	For every OD_PRODUCT_CODE defined in OD_PRODUCT_MASTER_MB, one entry needs to be present against this definition for every supported language. This is used to display the label for that product code in the administration screens as per the user preferred language.
PORTAL_SUBPROD	For every OD_SUBPROD_CODE defined in OD_PRODUCT_MASTER_MB, one entry needs to be present against this definition for every supported language. This is used to display the label for that sub product code in the administration screens as per the user preferred language.
PORTAL_FUNCTION_CODE	For every OD_FUNCTION_CODE defined in OD_FUNCTION_MASTER_MB, one entry needs to be present against this definition for every supported language. This is used to display the label for that function code in the administration screens as per the user preferred language.