Difference between revisions of "Digital response ecosystem map"
(Created page with "==Request== Snapshot of the digital response ecosystem for a shared view of the current state of affairs. This will provide better grounding for refining information flow, col...") |
|||
| (14 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {{About Projects}} | |
| − | |||
| − | == | + | ==Is there a digital response ecosystem?== |
| − | + | The digital response to humanitarian and disaster events is chaotic. Official and specialized actors such as [http://unocha.org United Nations Office of Coordinated Humantiarian Affairs] and [http://IFRC.org Red Cross Red Crescent] benefit from the new skills of digital tools and the processes they enable when they are able to fold these new tools into their existing structures. Frontline populations in affected regions continue to use digital tools like [https://itunes.apple.com/app/id874139669 Signal] and Facebook to organize themselves and coordinate response. Ad hoc community groups such as churches and schools are more and more often using their existing technical infrastructure and social media options to organize larger local relief efforts. And digital responders help to clean, structure, and utilize the massive amounts of information generated in times of crisis so those in the chaos can have more visibility to the requests, offers, and other factors in play around them. | |
| − | == | + | ==The problem== |
| − | + | While some official organizations have name-brand recognition, there is little understanding of local, emerging, and digital sectors. Flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem. | |
| + | |||
| + | ==Benefit of an Ecosystem Map== | ||
| + | While a living thing, a snapshot of the digital response ecosystem could provide a shared view of the current actors and flows of data and communication. Our hope is that this shared view might provide better grounding for refining information flow, possibilities for collaboration, and shared infrastructure. We could thus begin to think more holistically about response, provide insights on how to make response infrastructure and mechanism more sustainable and scalable, and be able to easily share an overview to newcomers or other interested parties. | ||
| + | |||
| + | ==Current status and how to get involved== | ||
| + | '''[https://docs.google.com/document/d/1PL3SAvdPg7XzpG5kfVW3hvEfD1hE6Kx95oAMwJENRdY/edit?usp=sharing North Star]''' : our in-process guiding document (or "concept note"). | ||
| + | |||
| + | '''[https://airtable.com/shrN8OGsjYjCjjmR6/tblhLsKuNHNRo1PDz/viwZXkcUR6S0Uciis Backend]''' : where our collaboratively-held data lives. | ||
| + | |||
| + | We're hosting calls with allies in the digital response space to explore what components need to be present for a useful (but not overwhelming) ecosystem map. We recently explored and expanded the ecosystem map | ||
| + | * as a remote session May 31st 9a PT/12p ET, | ||
| + | * at the [[2016 June HumTechFest]] as a session on June 5th, | ||
| + | * June 7th and 8th as interactive wall art at the [http://humanitariantechnology.org/ Humanitarian Technology Innovation Conference], | ||
| + | * at the [http://msfcanada-logday2016.azurewebsites.net/ Doctors Without Borders Canada logistics day] June 10th, and | ||
| + | * at the [[2016 June Meet Up]] on June 16th from 18:00-21:00 in San Francisco, CA! | ||
| + | If you have thoughts on what aspects of organizations, patterns of crisis response, or what sorts of data are useful in disaster and humanitarian response, please [mailto:digitalresponse@aspirationtech.org let us know]! You can also receive ongoing updates by [https://aspirationtech.org/taxonomy/term/71 following the digital response topic on our blog], [https://digitalresponse.aspirationtech.org/index.php?title=Digital_response_ecosystem_map&feed=atom&action=history subscribing to this page's RSS], or [https://lists.aspirationtech.org/lists/info/digitalresponse subscribing to the digital response mailing list]. | ||
[[Category: Project]] | [[Category: Project]] | ||
Latest revision as of 23:03, 24 October 2016
Projects listed on this wiki are held by the wider community, and are listed here only for reference. Our goal is that they be worked on and owned in a distributed and communal way, and are thus Creative Commons Attribution-ShareAlike. All projects should be seen as open to feedback and as continual works in progress. Questions, comments, suggestions, etc can be sent to digitalresponse@aspirationtech.org.
Is there a digital response ecosystem?
The digital response to humanitarian and disaster events is chaotic. Official and specialized actors such as United Nations Office of Coordinated Humantiarian Affairs and Red Cross Red Crescent benefit from the new skills of digital tools and the processes they enable when they are able to fold these new tools into their existing structures. Frontline populations in affected regions continue to use digital tools like Signal and Facebook to organize themselves and coordinate response. Ad hoc community groups such as churches and schools are more and more often using their existing technical infrastructure and social media options to organize larger local relief efforts. And digital responders help to clean, structure, and utilize the massive amounts of information generated in times of crisis so those in the chaos can have more visibility to the requests, offers, and other factors in play around them.
The problem
While some official organizations have name-brand recognition, there is little understanding of local, emerging, and digital sectors. Flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem.
Benefit of an Ecosystem Map
While a living thing, a snapshot of the digital response ecosystem could provide a shared view of the current actors and flows of data and communication. Our hope is that this shared view might provide better grounding for refining information flow, possibilities for collaboration, and shared infrastructure. We could thus begin to think more holistically about response, provide insights on how to make response infrastructure and mechanism more sustainable and scalable, and be able to easily share an overview to newcomers or other interested parties.
Current status and how to get involved
North Star : our in-process guiding document (or "concept note").
Backend : where our collaboratively-held data lives.
We're hosting calls with allies in the digital response space to explore what components need to be present for a useful (but not overwhelming) ecosystem map. We recently explored and expanded the ecosystem map
- as a remote session May 31st 9a PT/12p ET,
- at the 2016 June HumTechFest as a session on June 5th,
- June 7th and 8th as interactive wall art at the Humanitarian Technology Innovation Conference,
- at the Doctors Without Borders Canada logistics day June 10th, and
- at the 2016 June Meet Up on June 16th from 18:00-21:00 in San Francisco, CA!
If you have thoughts on what aspects of organizations, patterns of crisis response, or what sorts of data are useful in disaster and humanitarian response, please let us know! You can also receive ongoing updates by following the digital response topic on our blog, subscribing to this page's RSS, or subscribing to the digital response mailing list.