| 57 | |
| 58 | === Message Workflows === |
| 59 | The following workflows describe how a message could be responded to. This message may be from Twitter, Facebook(?), SMS or Email. The idea is that Sahana can be used to record the response to all messages. |
| 60 | |
| 61 | ==== Incident Report ==== |
| 62 | 1. A message is received reporting an incident |
| 63 | 1. The user decides to create an incident based on this message (perhaps it is from a trusted source, perhaps they checked to verify it, perhaps this is their policy) |
| 64 | 1. That incident is created with a link to this message (for verification) |
| 65 | 1. If other people see that message, they can see a link to the incident that was created from it. |
| 66 | |
| 67 | ==== Incident Verification ==== |
| 68 | 1. A message is received reporting an incident - which has already been recorded in Sahana |
| 69 | 1. The user links this message to an existing incident |
| 70 | 1. The message now has a link to this incident. That incident now has a link to this (and all other) related messages. |
| 71 | |
| 72 | ==== Request for Volunteers ==== |
| 73 | 1. A message is received requesting volunteers |
| 74 | 1. The user creates a request for volunteers (which is linked to/from this message) |
| 75 | |
| 76 | ==== Request for Supplies ===== |
| 77 | 1. A message is received requesting supplies |
| 78 | 1. The user creates a request for supplies (which is linked to/from this message) |
| 79 | |
| 80 | ==== Request for Information ==== |
| 81 | 1. A message is received asking for information |
| 82 | 1. A Message is sent in response (either to the person or broadcast) (which is linked to/from the first message) |