A public dataset needs an owner, a review trigger and a correction route. Launching a portal is only the first handoff.
Handover memo: public facilities directory
A hypothetical city publishes a facilities directory. The launch team checks the map and download, then moves to another project. Three months later, a sports hall changes its opening arrangements. Which record changes, who approves it, and how does the public copy catch up?
ArcGIS Hub supports sharing curated content and open data through sites. Keeping a dataset useful requires an operating agreement around that capability.
The agreement to leave behind
| Responsibility | Completed example | Evidence of completion |
|---|---|---|
| Authoritative record | Facilities register owned by the services department | Named source and accountable owner |
| Routine review | Monthly review plus review when a facility changes | Dated review entry, even if nothing changed |
| Correction intake | Public contact route attached to the dataset | Test message reaches the assigned team |
| Approval | Services owner confirms the changed hours | Decision and source retained |
| Publication | Data steward updates the public representation | Public map and download checked for agreement |
| Continuity | Deputy covers owner absence | Deputy can locate the procedure and source |
“Monthly” is an example local agreement, not a recommended frequency for every dataset. Match the interval to the consequence of stale information and the change process.
Walk through the correction
A resident reports that the sports hall is closed on a day shown as open. The steward records the report without treating it as verified fact. The facilities owner confirms the new arrangement. The approved change reaches the authoritative record, then the public representation. A reviewer checks both the map and download.
If the map is corrected but the downloadable file remains old, the incident is not fully closed. Record the discrepancy and fix the publication path rather than telling the next user to ignore the download.
Describe what a user is receiving
Publish the dataset's purpose, coverage, relevant date, update approach, field meanings, use terms and correction contact. Distinguish the date the page changed from the date the underlying information was reviewed. A new page timestamp cannot make an old source current.
Before exposing data, check what is actually appropriate for public release. The directory may need a public facility address but not internal staff contact details. Review the public view and downloadable attributes as separate surfaces.
Measure a maintenance outcome
For the first operating review, trace one correction from intake to verified public result. Measure elapsed time only after defining the start and finish. A portal's value is easier to defend when somebody can show that corrections reach users, rather than only report how many datasets were uploaded.
For related preparation, read explaining a public proposal. Discuss this workflow with InfoGraph or review relevant GIS training.
