The percentage of records across one or more systems, fields or datasets that conform to the agreed syntactic formats, controlled vocabularies, reconciliation rules and canonical identifiers established by the governing data model or authority file. Measurement requires clear normalization rules, reconciliation procedures and a delineation of scope (which systems, fields, and time window).

Principle

High data consistency enables reliable joins, automated processing and predictable behaviour of services; inconsistency increases the need for ad hoc reconciliation, human intervention and error-prone mappings.

Demonstration

Illustrative scenario → Two catalogs are compared on a shared identifier field for 10,000 matched records; 9,400 records share exact canonical identifiers or allowed variants as defined by reconciliation rules → Data Consistency Rate = 94%. The reconciliation log records the types of mismatches for corrective governance.

Misapplication

Equating syntactic conformity (e.g., standardized date format or field presence) with semantic alignment—two records may conform to the same format yet use different conceptual definitions (e.g., 'date' meaning publication date versus issue date), producing misleading consistency measurements.

Consequence

Low consistency rates impair cross‑system discovery, aggregation, reporting and automation; they increase costs for data cleaning and can produce incorrect analytics or duplicate user exposures to the same resource.

Reversal

When systems intentionally diverge to preserve local practices, provenance, or legal constraints, forcing strict global consistency can destroy necessary local semantics; in such cases, layered mapping and provenance metadata are preferable to unilateral normalization.

Boundary

Clearly within: fields and identifiers governed by an agreed reconciliation policy across the considered systems. Boundary case: tolerated variants explicitly allowed by the reconciliation rules. Clearly outside: unrelated system logs, transient session data or intentionally incompatible local schemas.

Semantic Tension

Standardization ↔ Local Specificity: enforcing uniform formats and vocabularies improves interoperability but can suppress locally meaningful distinctions and provenance information.

Synthesis

Data Consistency Rate is an operational measure of conformity that acquires meaning only when accompanied by explicit reconciliation rules, scope and governance; improving the rate requires both technical normalization and cross‑system policy alignment.