How we do it
The homepage says what you get. This page says how, for whoever on your side signs off on access.
What every load does
- Checks it before it goes live. We load the new version beside the one your dashboard shows, query it in your system, and compare row counts, blanks and totals with the source. Any difference discards it, so your dashboard never sees it. Once it is live, we read it back again.
- Swaps all at once. Your dashboard shows the old version or the new one, never half a load. CKAN portals are the exception: rows show while the load runs, about twenty seconds for thirty thousand rows in our sandbox, and the portal is marked with the new version only once the check passes.
- Touches only what it created. It never replaces or deletes a table, index or file it did not create.
- Rolls back in two commands. Restore the previous version, then push it. In PostgreSQL and MySQL the previous version is still in your database, so the push swaps it back instead of reloading. Loading the same file twice changes nothing.
| Check | Source file | Read back from PostgreSQL 17.11 |
|---|---|---|
| Rows | 30,316 | 30,316 matches |
| Blank amounts | 3,175 | 3,175 matches |
| Total | $63,668,595,549 | $63,668,595,549 matches |
| Fiscal years | 6 | 6 matches |
Tested in sandboxes on PostgreSQL with Metabase, MySQL, OpenSearch, Elasticsearch, S3-compatible storage and CKAN. Any other system starts with the same test in your sandbox.
What you approve first
Before anything loads, you see every change with each exception listed, and nothing publishes until you accept them. A sample change review, on a synthetic update to published LA City data.
Access
Public data only. For a pilot, a scoped account that can create tables in one schema (one database on MySQL) or indices under one name, and changes only what it created. We prove it in your sandbox first. Your dashboard reads the same name throughout, so its own access does not change. Or your own staff run the load from our handoff guide. The web app is read-only; data changes only through the operator's command line.
Validation report for the published version · Update log of every import, approval and rollback