Glossary

What is data validity?

Data validity describes whether a value satisfies the rules defined for its use, such as a permitted type, format, range or list of options. In a product record, a valid field follows the relevant specification. Validity can be checked automatically where rules are explicit, but passing those rules does not prove that the value describes the product accurately.

Make the acceptance rule explicit

Validity is assessed against a rule, not against an undefined idea of good data. A length field might require a number and a stated unit. A finish field might accept only approved catalogue options. A relationship rule could require the minimum operating temperature to be no greater than the maximum.

The applicable rule can depend on category, market or lifecycle stage. Record those conditions so an item is not rejected by a requirement that does not apply to it.

Example: a supplier voltage column

A supplier sends "230 V" into a field designed to hold a numeric voltage. An import process could separate the number from the unit under an agreed transformation. A value such as "various" may need review because it cannot be interpreted using that same rule.

After transformation, the value 230 may be valid for the field while still being wrong for a particular variant. Confirming that variant requires evidence beyond the format check.

Validity and validation

Validity is a quality characteristic; validation is the activity of testing rules. Validation can also check completeness and relationships. Avoid changing unusual but legitimate specifications merely to make a record pass. A rejected value may reveal an incorrect rule, an incorrect mapping or a genuine source error.

Related terms

Sources and further reading

Product Data Services

Explore practical support for organising, improving and maintaining product information.