GSoC 2022: Microfrontend the OCL Module - Project Updates

Community GSoC
, , , ,
26

I identified a few more errors related to items(concepts/mappings) in an import.

These are the known errors which can occur when importing concepts:

  1. Cannot create concept conceptUuid . Datatype conceptDataType is not supported by OpenMRS.
    This error occurs if the datatype of the concept is not supported.

  2. Cannot import concept conceptUuid , tried: logError .
    This error is thrown when there is a duplicate concept name error or due to failures in openmrs concept service. The logError varies with the scenario. So the error message can be very long sometimes.

The following are the known errors which can occur when importing mappings:

  1. Cannot create mapping from concept with URL fromConceptUrl , because the concept has not been imported.
    This occurs when the fromConcept required for the mapping is missing from the OpenMRS instance.

  2. Cannot create mapping for oclMappingURL as no from concept is defined.
    This is thrown when the mapping is incomplete (fromConcept is missing)

  3. Cannot create mapping from concept with URL toConceptUrl , because the concept has not been imported.
    This occurs when the toConcept required for the mapping is missing from the OpenMRS instance

  4. Cannot create mapping for oclMappingURL as no to concept is defined.
    This is thrown when the mapping is incomplete (toConcept is missing)

I think most of these are already simplified, so I’ll focus more on the errors that fails the whole import.

Examples:

  • HTTP/1.1 208 Already Reported caused by: java.io.IOException: HTTP/1.1 208 Already Reported
  • HTTP/1.1 204 No Content Error caused by: java.io.IOException: …
  • HTTP/1.1 404 Not Found Error caused by: java.io.IOException: …
  • There is no release version of the given source…

(Reference - Unable to import concepts using OCL Subscription Module)

1 Like