Contents
| Table of Contents |
|---|
Overview
...
Besides seeing the result of a series of validation steps, the user will be able to determine the results of individual validation steps. The progress in the validation process is called Validation Status.
This functionality is available from Delft-FEWS version 2015.02 onwards.
Use Cases
Validation Status should support the users in their specific validation practices and allow the users to confirm that the data has been adequately validated. The following use cases will be supported:
- For a time series, it will be registered per timestep, which validation steps have been performed
- The progress in the validation process can be used as a condition for execution of a transformation/workflow
- The user gets a visual indication (tooltip, validation step columns in table view, background color and color bar) which validation steps have been performed
- The user gets extended possibilities to validate timeseries manually
Summary of Validation Status implementation
The validation procedure of an organisation can consist of various (serial) validation tasks: Primary/Secondary validation, transformation interpolation of data, visual inspection, ... In the end, a validated timeseries will possibly have a quality flag (Reliable/Doubtful/Unreliable/Missing) as a result from the validation process. Since version 2012.01 FEWS stores not only the quality flags, but also the source of the flag, the so-called flagSource. So the user is able to see why a certain value is validated as unreliable, eg. due to exceeding of the hard max. The regular flagSource (which is visible in the Delft-FEWS interface as the 'Validation' item), in combination with the quality flag is therefor a summary of the validation process.
Since version 2015.02 FEWS makes it possible to configure so-called 'flagSource columns' for each individual validation step, in which the flagSource of the specific validation step will be recorded. From these flagSource columns the user can deduct which individual validation steps have been performed and to what result. Even when a defined validation step has been executed successfully and no quality flag has been changed, a default flagSource "OK" will be set for the respective flagSource column. The flagSource columns therefor provide details on all the validation steps.
Functionality
FlagSource columns can be defined in a dedicated flagSourceColumns regional configuration file, see FlagSourceColumns in the Configuration guide. These flagSource Columns are stored for each timestep for all timeseries that have been validated in the FEWS database. Various configuration options allow the user to harness the Validation Status in the operational process, either by visualisation, export, conditional filtering in transformations, etc.
...