Data validation: Difference between revisions

Revision as of 09:05, 19 February 2025

Revision as of 05:52, 27 February 2025

Line 1:

{{Short description|The processProcess of ensuring computer data is both correct and useful}}

{{redirect|Input validation||Improper input validation}}

{{more citations needed|date=November 2016}}

Line 7:

==Overview ==

Data validation is intended to provide certain well-defined guarantees for fitness and [[data consistency|consistency of data]] in an application or automated system. Data validation rules can be defined and designed using various methodologies, and be deployed in various contexts.<ref>[https://ec.europa.eu/eurostat/cros/system/files/methodology_for_data_validation_v1.0_rev-2016-06_final.pdf Methodology for data validation 1.0]</ref> Their implementation can use [[declarative programming|declarative]] [[data integrity]] rules, or [[imperative programming|procedure-based]] [[business rules]].<ref>[http://msdn.microsoft.com/en-us/library/aa291820(VS.71).aspx Data Validation, Data Integrity, Designing Distributed Applications with Visual Studio .NET]</ref>

The guarantees of data validation do not necessarily include accuracy, and it is possible for data entry errors such as misspellings to be accepted as valid. Other clerical and/or computer controls may be applied to reduce inaccuracy within a system.

Line 129:

{{DEFAULTSORT:Data Validation}}

[[Category:Data processing]]

[[Category:Data security]]