Missing input validation

[fscheel]

The current state of the service is a prototype. As such almost no input validation, cross checks and sanity checks are performed. They need to be implemented.

[mmaiers-nmdp]

For example this resolution field

"ResolutionData": [
    {
      "scopeElement": null,
      "resolution": "4-Field"
    }
]

should be validated against the enum from the yaml

 ResolutionInfo:
    title: ResolutionInfo
    properties:
      scopeElement:
        type: string
      resolution:
        type: string
        description: resolution of the data
        enum:
          - G
          - P
          - gNMDP
          - gDKMS
          - 2-Field
          - 4-Field
          - 6-Field
          - 8-Field
          - Serology

[fscheel]

In a way the enums are evaluated: Invalid values are blanked. I yet have to find a way to turn this blanking off and return an error 400 instead.

[mmaiers-nmdp]

We have discussed configuring the service to refer to a second service that only performs HLA validation. The high-level requirements for this service is something that a group is discussing at WMDA.

[mmaiers-nmdp]

Also need "liftover" for dealing with renamed alleles.
Deleted alleles are a different issue.