Open311

Wiki

Collaboration for an Open311 Standard
Personal tools

Difference between revisions of "San Francisco"

Collaboration for an Open311 Standard

Jump to: navigation, search
(Created page with '{{msg:stub}} ''This was taken from the Notes from Cities portion of the [http://etherpad.com/wCotZZ0OCE Open311 DevCamp Etherpad]'' === General Description === 311 twitter inte...')
 
Line 4: Line 4:
 
=== General Description ===
 
=== General Description ===
 
311 twitter integration, exciting about participating in Open311 api, been considering for a while. Agrees with not just looking at request, but also disseminating information. Happy to focus just on requests for now, but then getting to how to answer questsion. Draft api is modeled after DC api. Fast tracking this, next few months . Using Lagan system, the vision is to route that to departments that do the work. Have a middleware system, using Oracle, thinking of changing that model, so 311 is a central hub, so other depts poll system. rather than pushing data out, just wnt to make sure that information will flow out. Very optimistic
 
311 twitter integration, exciting about participating in Open311 api, been considering for a while. Agrees with not just looking at request, but also disseminating information. Happy to focus just on requests for now, but then getting to how to answer questsion. Draft api is modeled after DC api. Fast tracking this, next few months . Using Lagan system, the vision is to route that to departments that do the work. Have a middleware system, using Oracle, thinking of changing that model, so 311 is a central hub, so other depts poll system. rather than pushing data out, just wnt to make sure that information will flow out. Very optimistic
 +
 +
[http://apps.sfgov.org/Open311API/ Information and wiki for San Francisco's Open311 implementation]

Revision as of 15:08, 9 November 2009

This page is a stub. If you have more content to add, please edit this page.

This was taken from the Notes from Cities portion of the Open311 DevCamp Etherpad

General Description

311 twitter integration, exciting about participating in Open311 api, been considering for a while. Agrees with not just looking at request, but also disseminating information. Happy to focus just on requests for now, but then getting to how to answer questsion. Draft api is modeled after DC api. Fast tracking this, next few months . Using Lagan system, the vision is to route that to departments that do the work. Have a middleware system, using Oracle, thinking of changing that model, so 311 is a central hub, so other depts poll system. rather than pushing data out, just wnt to make sure that information will flow out. Very optimistic

Information and wiki for San Francisco's Open311 implementation