Validator for data-model

[tom-zoladz]

Description

DataModel contains rules for each entry that entity json records contain. The rules given in the DataModel should be validated when creating or updating the entity.

Since the Spring framework is used, this validator should be compatible with Spring validation.
Where possible use Jakarta validation constraints.

Example of data-model json for this application

{
  "id": "8fd1980d-3151-4d00-8495-5a10bf8e7099",
  "entrySettings": {
    "status": {"type":  "enum_key", "format": "dictionary", "optionsRef": null, "required": true, "readOnly": false},
    "genus": {"type": "string", "format": null, "optionsRef": null, "required": true, "readOnly": true},
    "family": {"type": "string", "format": null, "optionsRef": null, "required": true, "readOnly": true},
    "commonNames": {"type": "string_array", "format": null, "optionsRef": null, "required": true, "readOnly": false},
    "lifecycle": {"type": "enum_key", "format": "dictionary", "optionsRef": "lifecycle", "required": true, "readOnly": false},
    "origin": {"type": "enum_key_array", "format": "dictionary", "optionsRef": "origin", "required": true, "readOnly": false},
    "something": {"type": "enum_key", "format": "dynamic", "optionsRef": "/app-resources/somethings", "required": true, "readOnly": false},
    "wikiLinks": {"type": "string", "format": "url", "optionsRef": null, "required": true, "readOnly": false},
    "imageSource": {"type": "string", "format": "url", "optionsRef": null, "required": true, "readOnly": true},
    "somethingNew": {"type": "string", "format": "url", "optionsRef": null, "required": true, "readOnly": true}
  },
  "groupContents": {
    "potted plant": ["genus", "family", "commonNames", "lifecycle", "origin", "something", "wikiLinks", "imageSource", "somethingNew"],
    "trees": ["genus", "family", "commonNames"],
    "ground plant": ["genus", "family", "commonNames"]
  },
  "enumOptions": {
    "origin": [
      {"key": "origin_asia", "value": "Asia", "info": ""},
      {"key": "origin_europe", "value": "Europe", "info": ""},
      {"key": "origin_southamerica", "value": "South America", "info": ""},
      {"key": "origin_northamerica", "value": "North America", "info": ""},
      {"key": "origin_africa", "value": "Africa", "info": ""},
      {"key": "origin_australia", "value": "Australia", "info": ""},
      {"key": "origin_antarctica", "value": "Antarctica", "info": ""}
    ],
    "lifecycle": [
      {"key": "lifecycle_annual", "value": "Annual", "info": ""},
      {"key": "lifecycle_perennial", "value": "Perennial", "info": ""},
      {"key": "lifecycle_biennial", "value": "Biennial", "info": ""}
    ],
    "substrate": [
      {"key": "substrate_soil", "value": "Soil", "info": ""},
      {"key": "substrate_perlite", "value": "Perlite", "info": ""},
      {"key": "substrate_vermiculite", "value": "Vermiculite", "info": ""}
    ]
  }
}

Sources

The above approach is not strictly following the json-schema.org standard, but the below info may be useful:

• Validation in Spring Boot
• Jakarta validation constraints
• What is a json-schema?
• JSON Schema Reference