Checklist for 4236 style deployment

4636-style-checklist

Checklist for 4236 style deployment
From the crisismappers list


00:  Define what you want to accomplish with this deployment -
consider it the "mission statement" part of the Mission 4636.  Useful
for explaining to citizens, responders, press exactly what it is that
you are doing and will help clarify the design / implementation
process going forward.

0. Consider potential negative consequences of project and possible counter-measures

0.1: Establish internal roles and responsibilities at the very least
including deployment manager, communications lead, tech lead

0.2: Establish relationships with aid / response organizations and
make them aware of what you are planning - get to know the consumers
of your information ahead of time and shape your information
collection, analysis, presentation approach to suit THEIR needs.

1. Identify literacy rates and how much of an SMS culture exists in potential/risk areas

1.1 Find out which other social media cultures exist in-country, and see if you can use these as secondary feeds / early feeds whilst you're setting up the SMS short code.  For Pakistan floods, this was Facebook and ham radio - for California riots, it appeared to be Twitter :-).

2. Find out which telco's operate in and their associated market share

3. Approach market leader and explore options for short code

4. If short code not possible, set up FrontlineSMS number

5. Identify languages that text messages will be written in

6. Recruit translators and explore automated translation/tagging options

7. Set up crowdsourcing / mechanical turk platform to translate incoming SMS

8. Integrate SMS into dynamic mapping platform like Ushahidi, and activate Standby Volunteer Task Force

NOTE: Integrating SMS into a mapping platform will add an extra step of processing - consider how the text messages are coming from the Telco. Will they have some geo-reference or do you need a task force to locate the information? 

NOTE: Volunteer-based projects are not sustainable in the long-run - consider how much information needs to be processed using manual labor and then create a sustainable strategy from there (or how long you want the project to run)

9. Draft message to be sent out on local/national media re purpose of SMS project (careful about raising expectations)

10. Craft media strategy (including mass SMS broadcast)

11. Insure that the feedback loop can be closed before making project public

NOTE: Who will be using this information? This goes back to #8 - how will they be using it? A map isn't *always* necessary so talk to your responders/audience and see how they want the information displayed. The biggest problem we had (when talking to consumers of Mission 4636 information) was that it was just too much. They were quickly inundated and map or no, they needed analyzed, concise reports - not streams of messages.


12. Develop strategies for sustainability 

13. Engage language experts for the location included in the event and that a language expert (not an online tool) be used to proof the public information - especially the short code.  Online translators can't interpret or recognize a slang word that we may use that may have a very different meaning for 'in country' listeners or readers.