Quick Review of Chicago’s Open 311 Implementation

Here are some notes I took while reviewing the various Web resources published in the City’s Open 311 implementation announced on Friday:

Service Tracker: http://servicetracker.cityofchicago.org/ 

The Service Tracker tool is driven by this open source code:

It displays a running list of service requests submitted under the following service request types:

  • Abandoned Vehicle
  • Alley Light Out
  • Building Violation
  • Graffiti Removal
  • Pavement Cave-In Survey
  • Pothole in Street
  • Restaurant Complaint
  • Rodent Baiting / Rat Complaint
  • Sanitation Code Violation
  • Street Cut Complaints
  • Street Light 1 / Out
  • Street Lights All / Out
  • Traffic Signal Out
  • Tree Debris

Some possible improvements:

  • Full-text search
  • View all service requests by type

Many of these features are already in The Daily Brief: http://311labs.org/experiments/dailybrief (code: https://github.com/codeforamerica/311DailyBrief). What’s the current status of this code? The GitHub page says, “Under RE-construction. Stay tuned!!!”. Some features that would be good to have in this code:

  • Search for a specific service request (a la Service Tracker)
  • Full text search

311 Request Chicago: http://311request.cityofchicago.org/

This is a tool to view existing service requests and submit new requests. The default homepage is “view requests”, and it displays a list of the most recent requests submitted under the following request types:

This list of request types is displayed to the user in a sidebar, so that they can view all requests under each of the types.
It also allows the user to view requests by current status. Example:
There are other service requests in this system as well. A search for the word “restaurant” reveals a different list of service requests on the right-hand side,

Posted

in

, ,

by

Tags: