context

The context element is a child of the parserOptions element. It has no child elements.

ATG Search contains a large general purpose dictionary which represents all of the knowledge about a language that it processes. The dictionaries for each language can be loaded separately, or in combinations. For each language, the dictionary contains index terms (also called stems), part-of-speech data, syntactic and semantic features, morphological rules, compound and phrase data, term normalization data, term weights, thesaurus entries, text patterns, and various other pieces of data.

The adaptor components are extensions to the general purpose dictionary. Adaptors typically reflect domains, such as financial, computer, and manufacturing. Each domain requires specialized information in the dictionary, which may or may not be applicable to other domains. Administrators determine which adaptors are loaded (see the “Term Dictionaries” chapter of the ATG Search Administration Guide). Adaptors consist of the following:

  • index terms

  • compound terms

  • term normalizations

  • additional thesaurus entries

  • modifications to thesaurus entries in the core dictionary

ATG Search offers the following adaptors for English:

  • aerospace

  • airlines

  • apparel

  • appliances

  • automotive

  • business

  • computer

  • cooking

  • crafts

  • ecommerce

  • financial

  • food

  • healthcare

  • hotels

  • housewares

  • HR

  • insurance

  • jewelry

  • legal

  • manufacturing

  • media

  • personal_care

  • pets

  • sports_outdoors

  • telecommunications

  • tools

  • toys

  • yard_garden

During indexing, the adaptors are loaded based on the languages selected in Search Administration (see the ATG Search Administration Guide).

To use a dictionary adapter, the adapter must be loaded when the content is indexed, and it must be included as a context in parserOptions. For example, to use the healthcare adaptor, it must be selected as a pre-indexing customization in the Search Project via Search Administration. Additionally, each query must include the context in its parserOptions:

<context>healthcare</context>

Multiple instances of this element are allowed. If an adapter is specified at index time but not as a query-time context, the loaded adapter is not used.

Adaptors can affect which strings are considered tokens for indexing purposes, and this effect is independent of the context setting at query time. Therefore, you should usually include all adapters as contexts in the query. The exception would be if a site has mixed content indexed in a single partition; then, different adaptors may be enabled at query time, depending on the context of the query. This allows different thesaurus entries to be used depending on the query context; for example, in one context for healthcare, and in another context for pets.

 
loading table of contents...