
🏛️ Government & Public Sector · Data Flow
How government departments publish data safely on an open data portal: anonymisation, approval, publishing and APIs for developers.
Drawing diagram…
Data flow for government open data: department systems export datasets to a staging area, an anonymisation step removes personal data and aggregates small counts, a data officer reviews and approves, approved datasets get metadata and a licence and are published to the open data portal (CKAN) with downloadable files and APIs. Developers, researchers and journalists use them, and usage statistics go back to departments.
flowchart LR D[Department Systems] -->|Raw exports| ST[(Staging Area)] ST --> AN[Anonymise and aggregate] AN -->|Clean dataset| RV[Data Officer Review] RV -->|Rejected, needs fixes| AN RV -->|Approved| MD[Add metadata and licence] MD --> PORTAL[Open Data Portal - CKAN] PORTAL -->|CSV, JSON downloads| USERS[Developers, researchers, journalists] PORTAL -->|REST APIs| USERS PORTAL -->|Usage statistics| D
A single online portal where citizens apply for government services: identity login, a service catalogue, document storage and payments to the treasury.
How a building permit or trade licence application moves through a government office: scrutiny, site inspection, fees and the final certificate.
How a service verifies a person's identity with a national ID and OTP (e-KYC), with consent and without storing the ID number.
How a taxpayer files an income tax return online: pre-filled data, computation, payment of any balance tax and e-verification.
The states of a citizen complaint in a public grievance system: registration, assignment to a department, resolution, citizen feedback and escalation.
A schema for digitised land records: parcels with survey numbers, owners and shares, mutations, encumbrances and map references.