Term migration uses the /atg/dynamo/service/jdbc/EServerJTDataSource connection to extract eServer vocabulary into a term dictionary. Terms are created in a new term dictionary entitled “eServer <KB> vocabulary,” where KB is the domain prefix associated with that eServer KB.
Search has two configurable parameters. The values for these parameters are based on the following EServerMigrationService properties:
importTermsLanguage– Identifies the language of the term dictionary to be created. Note: eServer supports only one language per KB so each vocabulary should be relative to a single languageimportTermsLoadMode– Can be set toModify,OverrideorReject. The default isModify
Before initiating term migration, it is important to note that eServer terms and Search terms are structured very differently. In Search terminology, a Term Dictionary defines synonyms and other word associations used during the search.
In eServer terminology, a Term is a word or phrase. If the word or phrase appears in the vocabulary, it is referred to as a controlled term. A Vocabulary is analogous to an Search term dictionary. Customer defined vocabulary is composed of synonym (called strongly related terms) and associated (called somewhat related) relationships between terms.
It is recommended you revisit you vocabulary before term migration, or have ATG review the dictionaries that result from importing eServer terms in order to identify any inconsistencies.
