Understanding the Data Service Checkers

The relational schema of the database does not implement the constraints as defined through the JDL model such as uniqueness, nullablility, max-length or bounds. This allows you to import data with inconsistencies and to clean them afterward within the Platform.

To help with this process, the Platform Data Service provides built-in data checkers that are automatically triggered upon any data modifications (e.g. importing a scenario, editing data), and that report all inconsistencies found in a Scenario based on the JDL model definitions.

Built-in data checkers can also be triggered manually from the Web client or through the service APIs. For more details, please refer to Chapter Understanding the Platform APIs.

The detected issues with data are stored in the GeneSchemaIssue collection and can be visualized in the Web client, either using the Data Grid component or using the Issue List component.

After running built-in data checkers, the scenario data status is updated to a value among VALID, WARNING or ERROR depending on the highest issue severity reported in both GeneSchemaIssue and GeneIssue collection. For more details, please refer to Chapter Understanding the Execution Service.

Note: GeneSchemaIssue collection is reserved for Platform built-in data checkers, and should never be modified by project code. Each time the data checkers are run, the content of this collection is automatically replaced with the newly detected issues.