Tech Community Sitrep (Jan 22, 2010)
I’m a day behind on getting this SitRep up, my apologies.
Word Doc version:
Tech community sitrep – haiti 22 jan 2010
See it inline below:
(More …)
Tagged: situation report RSS
-
Erik Hersman
-
Erik Hersman
Ushahidi Situation Report (1/20/2010)
Dev Items:
- Reminder, please check http://github.com/ushahidi/Ushahidi_Haiti/issues for current changes/updates to the issues
- Iframe: Push changes on core to iframe (ex: http://www.haiti.com)
- Resolved items (ie, “action taken”) need to have some visual representation that that happened. Ex: I “resolved” this item and it doesn’t show up with anything on the frontend http://haiti.ushahidi.com/reports/view/584
- Get OSM back up on the map, even if it’s just as the + feature on the tab.
- Haiti Tracker: Integrating EDXL and PFIF into Sulsa. (Jon)
- Haiti Tracker: Migrating Haiti Tracker from Magpie to Simple Pie thanks to volunteers at Souktel. (Jon)
- API logger: To track API activities (Henry)
- API: parameter for the API to track where ( could be a webservice or thirdy party client ) a post is coming from http://github.com/ushahidi/Ushahidi_Haiti/issues#issue/19 (Henry)
- Updating the UI for “Categories” on the reports submit page (admin and front-end) [Caleb]
- Minor UI tweaks on home page (move download CSV button to top of page) [Caleb]
Non-Dev items:
- Process flow of 4636 system, a graphical diagram is needed. (Josh Nesbit)
- Heatmap blog post (Erik)
- Organizing of volunteer situation room teams for incoming reports (Patrick & Ory)
- “Resolved Issues” – putting a process and teams in place to gather reports back from the relief orgs in Haiti and map them to the issues within haiti.ushahidi.com (Ory & Patrick)
-
caleb
Just updated the above post to indicate completed tasks.
-
Erik Hersman
Haiti Technology Community Situation Report (1/17/2010)
Again, thanks to the InSTEDD team for providing this technology situation report for Haiti. This is an overview of the last 24 hours worth of work within the community.
Download the Word Doc:
Haiti Technology Community Situation Report – 17 Jan 2010Read it online below:
(More …)-
Eddy
This is a fine, detailed and highly specific post. Please know how appreciated that is. Keep up the great work everyone.
-
-
Erik Hersman
Ushahidi Situation Report
What we’re working on at Ushahidi currently and the point person for each issue.
Dev and Design Side:
- **critical** “Action tag” system – to tag reports with who’s reported on them (feedback loop)
- **critical** Swift River/Haiti Twitter Tracker “curated tweets” – need update and ETA [Jon & team in UG / Swift River community]
- Ensure timestamp is accurate (Github link). Note: set for right timezone? [Henry Addo]
- Search query via the API (for http://www.haiti.com and other iframe users) [Henry Addo]
- “Download data” link on frontend [Ken Kasina / Caleb Bell]
- The Flickr page should use frames from Extraordinaires so that people can help tag flickr images [Caleb Bell]
- Beefing up the How to help page, including an option to map organizations providing assistance and adding a way for volunteers to indicate where they are and what they are available to do. [Juliana Rotich]
- Clustering of Haiti Map data [David Kobia]
- Degradation of map data over time (fading out over 12/24hr period). Closely related: degrading of “resolved” items from the map, maybe to their own category only, or an indication visually that it’s been resolved. [David Kobia]
- 4636 bug reporting place needed [Brian Herbert]
- 4636 feature request: Solving for the “urgency” problem. How does an org receiving the feed understand what is the “most important”? [Brian Herbert]
- Do something with the KML overlay section (either dropdown or move under the timeline) [Caleb Bell]
- Main page: we have a banner with the SMS info and then a box just above the map. I think that’s too much. Could we please remove [Caleb Bell]
- Admin stats page for “impact” is borked (link: http://haiti.ushahidi.com/admin/stats/impact) [Henry Addo]
Non-Dev Side:
- **critical** Strategy for approval/verification situation room sustainability. Fletcher Situation Room is putting together a guide to map incoming SMS, please hold off on creating reports from incoming SMS until then. Guide should be available by 4am Boston time. (need link) [Patrick Meier / Ory Okolloh]
- Get Comcel 4636 shortcode going [Josh Nesbit and US Dept of State]
- Reports approval/verification [Juliana Rotich / Patrick Meier & Team / Ory Okolloh]
- Twitter, Blog updates [Erik Hersman]
- Situation Room & Situation Report coordination [Erik Hersman]
- Graphic explaining how the 4636 system works [Caleb Bell / design volunteer?]
-
Erik Hersman
Update as needed via the comments.
-
caleb
Main Page: SMS Shortcode announcement above map has been removed.
-
jongos
Swift River/Haiti: button is working and live on the site, should be passing all correct values accept location and username
-
Henry
Search query via the API (for http://www.haiti.com and other iframe users) : Fixed
-
Erik Hersman
Right on! Nice work Henry.
-
-
caleb
KML overlay section has now been moved to below the timeline on the home page
-
Erik Hersman
That looks a lot better Caleb. Thanks for updating the UI.
-
-
-
Erik Hersman
Ushahidi Situation Report (1/17/2010)
Ushahidi Haiti Deployment: Situation Report – Jan 17, 2010
Dev items
- Look/fix the geoRSS from the 4636 system
- Fixing bugs and adding usability features on 4636.ushahidi.com (Note: Brian is 100% on this, has no spare capacity)
- Ory’s “Action tag” system – to tag reports with who’s reported on them (feedback loop)
- Halfway done on cluster mode
- Swift River – needed VERY badly for situation room to process incoming reports (how soon?)
- Add public data download on main page (Ken and/or Emmanuel)
- Bug reports – http://github.com/ushahidi/Ushahidi_Haiti/issues
- Make sure that the comments are fixed, there was an issue with the security code
- Figure out an automated way to track who is subscribing to the feeds – Brian to busy to do it now, can we use feedburner or something – that will help me see which organizations are tracking us.
- Admin report edit log so people can see what’s been edited, what hasn’t, and a log of who edited
Design items
- “About” page formatting
- “How to Help” page formatting
- “Report” page categories
- Improve UI on KML layers: text font too large, also big massive white space below time slider
- Graphic explaining how the 4636 system works
Non-dev items
- Put together database of contacts in Haiti with affailiation and contact info for Nigel (Patrick)
- Replying to emails coming to Haiti@ushahidi.com (Patrick/Ory)
- Approving reports to Ushahdi (Patrick/Ory & team)
- Add SMS reports to map (Patrick & team)
- Situation Reports (Erik/Patrick)
- Compiling updated database for Clinton (Patrick)
- Processing of non-English email reports – Creole especially
- We need to devise an sustainability strategy ASAP, can’t keep the Fletcher Sit Room open for more than a day or two, can shift to fully virtual Sit Room but this still requires some management, not sure how to do this.
- Need to show how are data is being used, who is using, etc, stuff that Ory is trying to find out
- Flag particular reports that have critical information e.g. a hospital needs supplies and broadcast to our network but then there is a risk of noise (part of “Action Tag”)
- Encourage responders, situation allowing to let us know if an action has been taken. We can then leave a comment on a report or something. (Part of “Action Tag”)
Recently done/currently doing:
- David – Timeline fixed.
- David – Map changes/updates
- Brian – 4636 system
- Caleb – formatting on homepage
- Caleb – new language switcher
- Ory – media outreach, with focus now on local media
- Ory – closing the loop – make sure aid organizations are tracking us and that we can then track their actions if possible.
- Ory – putting together a list of who is tracking us so that we can publicize
- Ory – approving reports on Haiti admin
- Ken – cleaned up and uploaded the KML overlays
- Patrick – combing all news sources
- Patrick – updating mapping locations database which CrisisMappers group found very useful
- Patrick – managing group of 20+ volunteers, in Boston situation room and virtual
- Erik/Sarah – Media release & blog update
- Erik – Twitter & media
- Erik – situation updates & team coordination
- Henry – bugs
- Henry/David – Alerts system
- Jon – Haiti tracker: “send to Ushahidi” button, tagging and controlling for duplicates
-
Erik Hersman
Tech Community SitRep (1/16/2010)
Courtesy of the good folks at InSTEDD, here is a comprehensive situation report on the tech communities activities through 1/16/2010.
Download it as a Word Document:
Technology Community SitRep Haiti 6 Jan 2010View it online below:
(More …)
Eddy is discussing. 
Henry and one other person are discussing. 
Sanjana Hattotuwa 5:35 pm on January 24, 2010 Permalink |
Dear Eric,
You said that “Decision-makers on the ground still do not have access to accurate, real-time data.” In addition to points noted by you as to why this is the case, the format the data is published on also comes into play. One example is the hugely valuable master contact list in Haiti published yesterday by OCHA and available on the OneResponse website as a ZIP download containing a Excel 2007 format spreadsheet with multiple tabs. Far more simpler would have been to just upload this information to the web for people to access and search? In fact, what I did was to save each tab in that huge spreadsheet as a separate file, upload it to Google Docs, publish them as webpages and link to them on the ICT4Peace Foundation wiki, referenced above. Simple, effective, efficient.
VBW,
Sanjana
Erik Hersman 6:04 pm on January 24, 2010 Permalink |
Great point Sanjana. It’s one of the constant mysteries for me, why data isn’t published in a format easy to get to, mix and reuse for multiple purposes. Don’t even get me started on PDF maps as the only format on some websites…