Stale datasets
The portal is updated when someone remembers to export.
Open dataSolution
Publish public fields.
Keep private ones private.
Upsert changed permit records into a Socrata / Tyler Data & Insights dataset every night, with only the fields that belong in public.
This solution
Open data publishing
StartsOn a schedule · Nightly at 3 am
SystemsSocrata / Tyler Data & Insights, OpenGov Permitting & Licensing, Sentra 311, PostgreSQL / PostGIS
Templates2 ready-made flows to start from2
Stored recordsNone: pass-through, in memory only0
Preview any template on your own data before it writes anything.
§ The problem
What it looks like today.
Oversharing
A full export includes fields that were never meant to be public.
Duplicates
Re-uploading the whole file creates duplicates or wipes history.
§ How it works
How it works: Open data publishing
- 01Nightly at 3 amAfter the day's work
- 02Changed permitsOpenGov, since the last run
- 03Public fields onlyMap fields drops the rest
- 04UpsertInto the dataset by ID
§ 01 / Permits to the portal
Changed records, upserted.
Nightly, changed OpenGov permit records are reduced to their public fields and upserted into a Socrata / Tyler Data & Insights dataset, so the portal matches the system of record.
- Map fields keeps only what you list
- Upsert by ID: no duplicates
- Preview the exact rows before turning it on
§ Templates
Ready-made flows for this.
OpenGov Permitting & Licensing → Socrata / Tyler Data & Insights
Publish OpenGov permits to the open-data portal
Nightly, upserts changed OpenGov permit records into a Socrata / Tyler Data & Insights dataset.
Sentra 311Weekly 311 summary for department heads
Every Monday at 7 am, counts last week's closed 311 requests by type and emails the summary.
§ Systems
Works with
Pre-built connectors used in this solution. Anything else with an API, a database or SFTP works too.
Sentra 311See your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.