How UDataX reviews data corrections and source questions.
UDataX uses generated public-source snapshots for lookup, enrichment, and export workflows. This policy explains how reported data issues are reviewed and how accepted corrections flow into the next source update.
What we review
- 1Reference rows
Postal place names, country fields, holiday rows, and source notes. - 2Workflow behavior
Lookup results, CSV parsing, export fields, and visible error messages. - 3Source context
A public authority, dataset page, or reproducible example that supports the report.
Review steps
- 1Reproduce
We check the page, input value, country, date, or CSV sample from the report. - 2Compare sources
We compare the generated snapshot with the cited public source and source terms. - 3Apply update
Accepted corrections are added to the source refresh queue or handled as page behavior fixes.
What to send
Include the page URL, exact input value, country or year where relevant, expected result, observed result, and a public source link. CSV reports should include a minimal sample row with non-sensitive values.
Important boundaries
Postal coordinates are centroid references, not official delivery boundaries. Holiday rows are public reference data and should be verified against the relevant authority before payroll, settlement, legal, or compliance use. Country data is useful for standardization but does not replace process-specific regulatory guidance.