Add a validation attribute for all classes

[jpdupuy]

The business side requested to add an extra attribute for all classes in order to know if the object has been reviewed and validated from the business side point of view.
Importing a CSV files from the LEICA Field Survey is done by the Land Surveyor within QGIS thanks to the EasyImport plugin.
However, the business knowledge (ie: material type, diameter, insulation, ownership, ...) is only known and completed by the business side (another person).
Once the attributes have completed and verified, the business owner would like to make sure that the review is correct, by checking the "validation" attribute.
Note that the modification date is updated each type one of the attributes gets updated.

[ponceta]

This could be a tdh_validation boolean field that can be used for validation purpose by any entity. This would avoid customizations client side.

[sjib]

• Is a boolean field ok, or would it need a value list with different steps of validation?
• Does the validation check if all fields are filled out or if the right value has been chosen? Rather the second one - first thing could be done otherwise (and easily automated)
• What happens, if an attribute, eg. diameter is changed - will the validation field then be de-selected and the validation autorithy needs to re-check?
• If different groups have different ideas when something is valid, can this be done also with such an attribute. Or then rather go for INTERLIS MANDATORY Check CONSTRAINT in an external tool (lilke CHECKVSA)?

[sjib]

@jpdupuy It would be maybe good to add a description for the validation field

[jpdupuy]

@sjib
I reviewed the need with the business owner :
It is to define it as a boolean field, no need for a value list with different steps of validation. No need to introduce complexity.
the validation is check if the right value has been reviewed by the business owner who is the validation authority (based on delivery bill and its description of materials, diameters, etc ..) and the approved implementation drawings.
if an attribute, eg. diameter is changed - the validation field will not be de-selected. Since the validation authority is in charge to set the values or inform the application user to change one of the attributes. There is no needs to re-check or implement a complex workflow.

Only one person is in charge of the validity rules. The INTERLIS MANDATORY Check CONSTRAINT in an external tool (lilke CHECKVSA) to data interchange? The validation field which is requested is an added value for the validation authority only.