Versions Compared

Old Version 5

changes.mady.by.user Phillip Warner

Saved on

compared with

New Version 6

changes.mady.by.user Phillip Warner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • conceptMappingSpecifications
    • autoGeneratedMappings
      • folder containing auto-generated concept mappings
    • manualMappings
      • folder containing manually created concept mappings
  • knowledgeModules
    • folder containing knowledge modules exported from Guvnor (or other systems that generate knowledge packages)
  • resourceAttributes
    • folder containing OpenCDS configuration resources
    • knowledgeModules.xml
      • used for knowledge module metadata, for knowledge modules contained in the knowledgeModules folder (see above)
    • openCDSCodeSystems.xml
      • used to define the Code Systems supported by OpenCDS
    • openCdsExecutionEngines.xml
      • used to define which inferencing engines should be available to/used by OpenCDS
      • This file should not need to be modified except in certain cases.
    • semanticSignifiers.xml
      • Used to define which vMR versions are supported by the system.
      • This file should not need to be modified except in certain cases.
    • supportedConceptsConfigFile.xml
      • Used to indicate the supported concept for each OpenCDS Concept Type. (Unused during runtime.)

Anchor
ConceptMappings
ConceptMappings
Concept Mappings

...

  1. If you are using new concepts, add them to the relevant folder within the conceptMappingsSpecifications folder (see Concept Mappings).
  2. If your Knowledge Module supports one or more Code Systems that are not currently specified in OpenCDS configuration, add them to openCDSCodeSystems.xml (see OpenCDS Code Systems).If your Knowledge Module supports one or more concept types that are not currently specified in OpenCDS configuration, add them to supportedConceptsConfigFile.xml (see Supported Concepts).
  3. New Knowledge Module
    1. If the knowledge module is new, export it from Guvnor and place the downloaded binary package into the knowledgeModules folder (see Configuration Overview).
    2. Add an entry for the new knowledge module in knowledgeModules.xml (see Knowledge Modules).
  4. Replacing an Existing Knowledge Module
    1. If the knowledge module already exists and you want to replace it with changes made in Guvnor, you may replace the existing module; be sure the file name is consistent with the previous instance (see Configuration Overview).
  5. Restart OpenCDS (v1.1.5 and earlier).

...