Changes between Initial Version and Version 1 of Internship/2013/om_goeckermann/usecases/DisasterResponseRemote

10/17/13 15:19:06 (9 years ago)



  • Internship/2013/om_goeckermann/usecases/DisasterResponseRemote

    v1 v1  
     1== Disaster Response: Remote ==
     4Group of virtual volunteers, physically remote from an incident but collaborating to reduce suffering and provide situational awareness to any interested parties.[[BR]]
     5Volunteers may be members of existing organizations (SBTF, GIS Corps, HOT OSM) or interested individuals who have become alerted to an opportunity.[[BR]]
     7'''Types of Assistance:'''
     8* collect social media messages (Twitter, Facebook, Baidu)
     9* collect email and SMS messages
     10* collect news, RSS and transcribed radio or voice communications
     11* translate messages
     12* categorize messages
     13* determine geographic coordinates of a need or event
     14* provide cumulative effort impossible or inconvenient for single agencies
     15* generate image digitization for shared maps (perhaps integrate with OSM task manager?)
     16* provide analytical assessment
     17* store communications
     18* supplement existing information networks
     20=== Interface ===
     21=== Technology ===
     22Standards Compliant database containing:
     23* event identification
     24* reporter details
     25* the Report
     26* available means of communication
     27* history of interactions regarding that report
     28* location coordinates
     29* multiple location names associated with that coordinate
     30* related reports
     31* time value (to track an events evolution)
     32* supporting or responding agencies (who has viewed it, who is responding)
     33* severity of event
     34* category (icon driven menu)
     35* media (photo, video, audio)
     36* URL groups (supporting organizations, coordinating documents, related web resources)
     37* URL description
     38* relevant feed generation (API or RSS etc.)
     39* tracking of message view or response
     42Each report is an entity with a living human on the other side. Whether the message is regarding a life or death threat, or more mundane matters, it is important to the sender and ought to be afforded attention. In systems without feedback, individuals provide messages in the blind and aid workers must filter through and make critical decisions that increase tension. With feedback and mutual communication, individuals are empowered to assess their own needs in the priority structure. This will reduce the mundane reports and uncover potential for unanticipated solution finding. Remote disaster response should be working towards a goal of enabling input from every affected person in an event. The current fact that it is difficult to impossible doesn't indicate that the goal is any less important. Methods and technologies are already in production to handle significant volumes of information. Data analytics and crowd processing are also more effective than ever before.
     44Report processing will often follow a series of interventions, but the object is to process the messages quickly, rather than to ensure that every message is put through the same procedure. Some actions are not always necessary. SMS from a known and trusted entity can be assumed to be valid until the content proves otherwise. Messages containing lat lon coordinates do not need to wait in a cue every time. This is particularly important for critical messages. These will be verified further upon the action-taking phase, so the priority is to get critical messages identified and into an appropriate workflow.
     46Part of the group effort is categorization. The work is also important to do before the message arrives. Publicity efforts should be supported by all stages of message process that encourages self categorization. Providing two channels for interaction is one example, or choosing delivery technique (e.g. SMS for critical communications, Twitter for others)