Difference between revisions of "CouncilMeetingInput"

From PortlandWiki
Jump to: navigation, search
Line 1: Line 1:
 +
= Summary =
 +
 +
1. Improve discoverability of what's on city council meeting agendas.
 +
 +
2. Allow people to comment on upcoming agenda items.
 +
 +
3. Provide a way to track issues over time.
 +
 +
= People =
 +
 +
* Dietrich Ayala (Mozilla)
 +
* Phillip Holmstrand (City of Portland)
 +
* Oscar Godson (City of Portland)
 +
 +
= Implementation =
 +
 +
City bits (all XML)
 +
* agenda feed w/ links to detail feeds
 +
* detail feeds
 +
* future discussion items feed
 +
 +
Core
 +
* convert all to JSON and store
 +
* keyword search feeds
 +
* notifications (twitter, email)
 +
 +
Relationships
 +
* tracking related agenda items over time
 +
* using
 +
 
== main parts==
 
== main parts==
 
* communications to council - public vents
 
* communications to council - public vents
Line 38: Line 68:
 
** if id not unique, compound id+date
 
** if id not unique, compound id+date
 
** if an agenda item concerns previous agenda items, link it, and mechanically expose it
 
** if an agenda item concerns previous agenda items, link it, and mechanically expose it
 +
 +
= UI =
 +
 +
TODO

Revision as of 10:57, 3 June 2010

Summary

1. Improve discoverability of what's on city council meeting agendas.

2. Allow people to comment on upcoming agenda items.

3. Provide a way to track issues over time.

People

  • Dietrich Ayala (Mozilla)
  • Phillip Holmstrand (City of Portland)
  • Oscar Godson (City of Portland)

Implementation

City bits (all XML)

  • agenda feed w/ links to detail feeds
  • detail feeds
  • future discussion items feed

Core

  • convert all to JSON and store
  • keyword search feeds
  • notifications (twitter, email)

Relationships

  • tracking related agenda items over time
  • using

main parts

  • communications to council - public vents
  • time-certain items (owner, vote)
  • consent agenda - 100% covered unless pulled (owner, vote)
  • regular agenda - mostly covered, can vote to address later (owner, vote)

items

  • agenda id
  • item id
    • need to make unique by compounding with date.
  • owner
    • commissioner in charge (multiple)
    • bureau involved (multiple)
  • description
  • emergency
  • session date
  • session location
  • yea/nea (including who went which way)
  • video link
  • transcript link
  • document link
  • hashtags
  • associated item numbers

notification

  • feeds
  • searchable and as feeds

input

  • public comment per agenda item
    • blog post w/ comments

resolution

  • timestamp in video per item
  • what action was taken
  • tracking item relations for resolution
    • if id not unique, compound id+date
    • if an agenda item concerns previous agenda items, link it, and mechanically expose it

UI

TODO