WMDA is using the HLA Validator for all the HLA validation in WMDA services including Data Manager. There is a json schema validation to validate the value in json format before reaching the HLA Validator.
There are several validations process involved to better serve this service, and these validations are listed below:
- The specification can be found in the link below:
https://apispecs.wmda.info/?urls.primaryName=HLA%20Validator
2. HLA format validation based on json schema
The json schema used is as below, if you are with technique background, then you can doc the schema doc below:
https://brave-forest-04a379103.azurestaticapps.net/json_schemas/hlaValidator/validateBatchRequestBody.json
As the doc above it too technique, below is the explanation of the format validation that which are NOT supported in the json schema:
| Rules | Regular expression | Valid value examples | Invalid value examples |
|---|---|---|---|
a.dna.field1, a.dna.field2 | ^\\d{2,}:[A-Z0-9:]{1,}$|^NEW$|^UUUU$ | 01:01 | "/" is not allowed: for example01:02/01:03 |
| "*" is not allowed: A*01:02, A*11:FKFNG | |||
| value "new" is not allowed | |||
| Space is not allowed: 07 :BZEJD | |||
| Only one letter after first ":" is not allowed: 03:M | |||
| "XXXX" is not allowed for SER value | |||
| "NNNN" is not allowed for SER value |