Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

See DHP-1074 - Getting issue details... STATUS

JSON Validation

JSON Schemas will be used to validate the structure of the JSON data and type correctness.

JSON Schemas can be added as an Assessment Resource. Pre-req DHP-1070 - Getting issue details... STATUS

JSON-to-Table-Row (see DHP-1072 - Getting issue details... STATUS ) will check Assessment Resources for the Assessment ID / Revision for all JSON Schemas. For each file in the zip file, it will look for the JSON Schema with a title that matches the file name. We will then validate each file against the schema.

Previous experience tells us that researchers still want data even if it fails validation. However, we will log a message to the logs if it fails validation. We will use a Log Scan to add this to our dashboards so we can monitor and detect invalid uploads and incorrect schemas and fix app issues and systemic issues.

Table Column Validation

A list of table columns will be added as an Assessment Resource. The format will be a simple JSON Array of strings, where the strings are the names of the expected table columns (excluding common metadata columns).

If JSON-to-Table-Row generates columns not in this list, we will log a message. We will use Log Scans to add this to our dashboard, similar to above.

  • No labels