Page tree

Overview

Documentation on the handler architecture and extension points in the system.

Details

Much of the functionality of the system is driven by configurable handlers which help to provide customizeable functionality in the application.  

The basic structure of the handler mechanism uses three parts:

  • A defined interface providing the proscribed functionality
  • An implementation of that interface
  • Setup in the config.properties file to define the handler (or handlers to support) and any external configuration information they require.

The key extension points for this tool are:

HandlerConfig PropertiesDescription

ExportRefsetHandler

export.refset.handler

Exporting refsets to a file. Multiple can be configured.
ExportTranslationHandler

export.translation.handler

Exporting translations to a file. Multiple can be configured.
IdentifierAssignmentHandleridentifier.assignment.handlerAssigning identifiers for terminology objects (e.g. refsets, concepts, descriptions, etc). Multiple can be configured.
ImportRefsetHandlerimport.refset.handler

Importing refsets from a file. Multiple can be configured.

ImportTranslationHandlerimport.translation.handlerImporting translations form a file. Multiple can be configured.
PhraseMemoryHandlerphrasememory.handlerPhrase memory import/export and lookup. Only one can be configured.
SecurityServiceHandlersecurity.handlerAuthentication and logout. Only one can be configured.
SpellingCorrectionHandlerspelling.handlerSpelling import/export and lookup. Only one can be configured.
TerminologyHandler Terminology lookups, including finding descriptions/concepts, resolving expressions, and determining available terminologies and versions. Multiple can be configured.
ValidationCheckvalidation.service.handlerValidating refsets, members, translations, and concepts. Multiple can be configured.
WorkflowActionHandlerworkflow.action.handlerManaging workflow for refsets and translation concepts. Multiple can be configured.
WorkflowListenerworkflow.listener.handlerSupporting communication with third-party workflow engines if desired. Multiple can be configured.

 

See Configuration Settings Overview for specific examples of these config properties and the default setup for IHTSDO.

 

  • n/a

.

  • No labels