CouncilMeetingInput: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
== items == | == items == | ||
* item id | |||
* agenda id | |||
* item id | |||
** need to make unique by compounding with date. | ** need to make unique by compounding with date. | ||
* owner | * owner | ||
| Line 12: | Line 14: | ||
** bureau involved (multiple) | ** bureau involved (multiple) | ||
* description | * description | ||
* emergency | |||
* session date | |||
* session location | |||
* yea/nea (including who went which way) | * yea/nea (including who went which way) | ||
* video link | * video link | ||
* transcript link | * transcript link | ||
* document link | |||
* hashtags | * hashtags | ||
* associated item numbers | * associated item numbers | ||
Revision as of 10:34, 3 June 2010
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