Naming Standard for a Model
Abbreviation/Naming standard can help one to derive business names from physical ones in a consistent manner. For example, a physical name empl_first_name can be interpreted as a business name Employee First Name by tokenizing the physical name over the “_” separator, assuming “empl” is an abbreviation of “employee” and capitalizing the first letters of each word. This process is automated by Talend Data Catalog based upon any defined naming standard.
A naming standard is a list of abbreviations and words they represent, defined in a Naming Standard model. Talend Data Catalog allows one to define a naming standard once and reuse it for documenting different models and their new versions.
To associate a naming standard with a model for naming standard purposes, you may do so at model creation time or when editing the Naming Standard options of the Model in the configuration manager.
Naming standards are used to construct the Business Name of an object based upon its physical name either from a defined set of naming standard name/abbreviation pairs, or if there is no matching name/abbreviation pair or no naming standard is specified, then the Business Name is constructed based upon simple fixed rules (Naming Rules) and the options you specify here.
The naming standards metamodel is available (and may be edited or integrated with others) in MANAGE > Metamodel.
Naming standards apply to tables and columns in relational type imported models and to files and fields in file-based import models. For these objects, use the Edit Documentation option to edit the Business Name, and the naming standard will be suggested.
You may also apply naming standards to the above objects recursively at the multi-model, table, and column level by using the More Option… menu in the upper right of the object page.
A naming standard may be associated with multiple abbreviations. In this case, all of them are used when applying/proposing the naming standards. The longest match is the one picked when there are multiple matches. If more than one naming standard has the same abbreviation, the result is undefined, thus, one should ensure that there is only one naming standard with a particular abbreviation.