This article is not applicable to Cloud versions.
The Glossary allows you to maintain a central file of terms and definitions used in procedural content. The glossary functionality ensures authors are using consistent and approved definitions.
Glossary functionality is provided to allow you to maintain a collection of terms and definitions used in procedural content. The glossary allows you to specify consistent, business-specific definitions for your terms and then automatically push these definitions into your documents.
Terms and definitions are displayed in recorded Field/Description tables within the document view of content. Field description tables that are inserted during editing as a step will not support glossary functionality. The following is an illustration of a recorded Field/Description table.
Maintaining terms and definitions in one file allows documents to be updated quickly and accurately. New terms can be added, and changes can be made to definitions for existing terms within the glossary. The glossary functionality supports one definition per term.
Once you have standardized the valid terms and definitions, the administrator executes the globalization process to update definitions (descriptions) of terms (fields) within the documents prior to making the documents available to your end users.
Only those documents created with the same template as that used by the current glossary template can be globalized.
To ensure a manageable glossary file size and ensure optimum performance, there is a system limitation of 2500 terms that can be stored and managed in a Glossary. If an action within the glossary editor would cause this limit to be exceeded, a message is displayed. The number of available terms remaining is always displayed in the lower left.
|
NOTE: |
You can choose not to use a central glossary but, rather, have authors enter definitions directly into the Description column of tables. |