Air Twitter To Do Items

August, 2009

• Create aggregate feeds for Air Quality, Smoke, Dust from Delicious, Flickr, Twitter
• Monitor the output of feeds on ESIPAQWG Twitter and tweak detection and aggregation as necessary to filter out unrelated content
• Set up archive database for feed and time chart interface that can be embedded in the portal
• Manually ID location/content of tweets and events, and code into the database

September, 2009

• Initial analysis of all AQ feeds to determine the background AQ chatter vs. AQ event on ESIP Wiki
• Initial comparison of AQ feed to the smoke, dust, haze feeds to determine if event type can be determined between two feeds (i.e. spike in AQ and in smoke feed would ID a smoke event) on ESIP Wiki
• Create template response for Air Quality events with Air Quality Console (datasets relevant to smoke, dust or haze) as well as EventSpace wiki pages on ESIP Wiki where more complete aggregation can be done by the AQ Community
• First initial response to twitter community on AQ events that they tweet about.
• Engage ESIP AQ community in responding with their expertise.
• Continue monitoring/tweaking feeds

October, 2009

• Parse feeds and monitor word use rate. If a particular word is used at higher than normal rate this may id an event (i.e. during AQ events new tags may be implemented and would need to be highlighted and followed for the duration of the event)
• Begin automation of some parts of AQ Event response templates
• Create catalog on ESIP Wiki of Twitter captured AQ events.
• Continue monitoring/tweaking feeds for relevant content
• Continue ESIP AQ and Twitter community engagement

November, 2009

• Formalize documentation of Air Twitter design and implementation for use by other ESIP clusters (Water?) on ESIP Wiki
• Analyze three months of Air Twitter feeds to determine if a baseline can be established on ESIP Wiki
• Continue monitoring/tweaking feeds for relevant content
• Continue ESIP AQ and Twitter community engagement

December, 2009

• Finish Air Twitter documentation and contact ESIP Clusters about interest in implementation.
• Create poster/demo for Jan. 2010 ESIP meeting
• Finish catalog of Twitter captured AQ events
• Continue monitoring/tweaking feeds for relevant content
• Continue ESIP AQ and Twitter community engagement

January 2010 ESIP Meeting

• Report on initial four months of data and provide outbound services.