https://digitalresponse.aspirationtech.org/api.php?action=feedcontributions&user=Willow&feedformat=atomDigital Response - User contributions [en]2024-03-29T04:39:20ZUser contributionsMediaWiki 1.35.1https://digitalresponse.aspirationtech.org/index.php?title=Frontline_communities_holding_responders_accountable&diff=302Frontline communities holding responders accountable2017-04-25T15:38:33Z<p>Willow: </p>
<hr />
<div>{{About Projects}}<br />
<br />
==Request==<br />
A way for frontline communities to hold response groups accountable.<br />
<br />
==Theory==<br />
Local populations already have a good idea of what their needs and resources are. Especially when working with groups like Public Labs, they have metrics associated with their environments. Response agencies should be addressing not only immediate needs but doing so in ways which alleviate long-term issues as well.<br />
<br />
Community-held maps about environment and ongoing needs can be offered to response agencies as baseline data. A rapid proposal process can be created for response agencies to state what work they would be doing and their metrics. The frontline population would then decide which response groups can come into their space. The effectiveness of the response groups in fulfilling their proposals would be assessed by the community and published in transparent reports.<br />
<br />
This can, at its most simple, boil down to a statement of intent or need, followed by ongoing assessment of if needs are being fulfilled. Those statements and metrics can then be sent to the population, response organizations, donors, and constituents as the response unfolds.<br />
<br />
The individual should be the gauge of compliance, and accountability should be to the people rather than to the donors. Metrics of success should be set by the local population, and it is possible for existing technology to provide overviews of status and to expose comprehensive objectives and understandings. This is the difference between a body cam, which is police regulated, and a bystander recording, which is community regulated.<br />
<br />
==The project==<br />
A simple standard ledger of templates for personal accounting, useful for individual planning and contributed to a community for auditing. A "Request for Proposals to Help," of sorts.<br />
<br />
This might be as simple as statements such as these, documented in the public record:<br />
: '''affected communities to responders''': "You will (''a clear change from a current state to a different state'') for (''population/region/etc'') by (''date'')."<br />
* '''for responders to communities''': "We will (''a clear change from a current state to a different state'') for (''population/project/etc'') by (''date'')."<br />
<br />
Surrounding facilitation practices and templates to arrive at these statements can be created. Existing technical tools might be implemented for this new purpose/space, such as the telling of stories being done through Global Voices or a platform such as MicroAggressions, Follow The Money to track how finances are being used, Get Satisfaction as shaming on the record, the Listening Project as asking frontline communities if aid has actually assisted their livelihoods, and Promise Tracker as logging politicians' promises and delivery.<br />
<br />
<br />
[[Category: MIT]] [[Category: Project]] [[Category: Accountability]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=2012_Jul_31&diff=3012012 Jul 312016-10-26T18:24:08Z<p>Willow: Created page with "{{Why Call Ins?}} ==Attendees:== * Willow Brugh - Geeks Without Bounds * Cat - Humanity Road * Sara - Hunch Works, SBTF * Chris - Humanity Road * David - Crisis Commons * Pas..."</p>
<hr />
<div>{{Why Call Ins?}} <br />
==Attendees:==<br />
* Willow Brugh - Geeks Without Bounds<br />
* Cat - Humanity Road<br />
* Sara - Hunch Works, SBTF<br />
* Chris - Humanity Road<br />
* David - Crisis Commons<br />
* Pascal - UW and Crisis Commons<br />
<br />
==Organisational Overview==<br />
===Humanity Road===<br />
Cat and Chris with Humanity Road. Working on August and September. RIMPAC (Navy ex around Hawaii), did an HADR with crisis mapping. Following that in Sept is Pacific Endeavor in Singapore with 22 nations HADR simulation of crisis map. Going to be two weeks - a tabletop exercise followed by symposium and workshop. Also in September SMILE, a conference with the police in Richmond, VA. We're spearheading the 9/11 panel on communicating during a complex crisis. For Pacific Endeavor we are delivering a talk at the symposium and providing a directory of the digital humanitarian groups, still waiting for some of the responses for that directory. https://docs.google.com/presentation/d/1ACMe6qA35Au86F3MEdITPte8mzbTOfPXT-Nx-XKCFeI/edit The directory will be placed in APAN (All Partners Area network) www.apan.org. Any orgs can be listed on the directory and are encouraged to join APAN as well.<br />
<br />
<em>Questions</em>: Pascal?: can anyone join in? Yes, is part of APAN - any VTCs are invited to join in and sign up.<br />
<br />
===Hunch Works / SBTF===<br />
Sara ex Global Pulse, just started company to create Hunch Works (mixed human-data evidence management system, dealing with hunches) and do humanitarian data consultancy.<br />
<br />
Wrote an API to data.un.org ; sucked in all their data and corrected countryname references; added two new columns to each dataset: UN stats code and ISO code for each country reference, and wrote code to upload it all to buzzdata.com/sara . That got attention from State Dept. team working on datasets for WWHGD Working Group (wwhgd.org); wwhgd is collecting pre-crisis info at the same level as FEMA collected for USA, but for other countries that might be affected by disasters.<br />
<br />
Also talking to the ReliefWeb API team and the UNOCHA data team who are building pre-disaster country workbooks; this got me into building ontologies for disaster data needs - there are a half dozen of these, and they don't match: e.g. UNOCHA's COD/FODs, the UNOCHA draft of the work book, UNDP Sudan's metadata list, taxonomy from WWHGD. Need these ontologies (aka taxonomies) to help know what we're looking for with crisismapping - have put up spreadsheet to help with cross-matching.<br />
<br />
Also building datascience toolkit specifications (a toolkit to make big data analysis accessible to non-programmers) and useful bits of code around crisis mapping, e.g. chat monitors for skype,<br />
<br />
And working on conflict mapping technologies and ontologies for dayjob (plan to match these against disaster ontologies).<br />
<br />
SBTF: did a deployment for a UNOCHA team in South Sudan, hunting down as much country data as possible for a UNOCHA team that was going into the country. As part of this, UNDP shared their South Sudan data with OCHA, which is a big deal. SBTF deployment this coming weekend is doing GIS and big data analysis on that data. SBTF also did deployment with USAID, correcting gis references on data on where USAID money is spent.<br />
<br />
<em>Questions</em>: Outside of this forum, how do we get updates on data resources and hunchworks? After have a company name, we'll post everything on the company website. In the meantime, am putting personal stuff up on opencrisis.net, Icanhazdatascience.blogspot.com ,and overcognition.com .<br />
<br />
===CrisisCommons / UW Office of Global Affairs===<br />
Pascal has moved to University of Washington office of global affairs, working in university environment. International students doing research. Building tools using the free resource of the students. Global situational awareness tool. Don't push information into structure, but provide for other people to use. here are filters you can use, but not dictate how people act (don't want to mess with policy). Just provide information and people can deal with the info as per their policies.<br />
<br />
Crisis Commons is dealing with legal container stuff, getting it registered in NC, becoming a full 501c3, doing global liability research. Missing person database project. Have a paper coming out August 30th or so on the legal liability of digital humanitarian response. Draft of version 1 strategy plan to get pushed out. Being sure we're legally covered in things.<br />
<br />
===CrisisCommons===<br />
Patrice Cloutier (CrisisCommons) is leading the development of a national VOST program in Canada (CANVOST), large group meeting tomorrow (second meeting) to move things fwd, all the right stakeholders from gov and volunteers are at the table.<br />
<br />
===Geeks Without Bounds===<br />
Was taking notes and you already read this blog.<br />
<br />
==Post- intro discussions==<br />
===Satellite Imagery===<br />
Opinions on Tomnod hunt for missing climbers<br />
<br />
Tomnod makes putting markers onto satellite images easy. Includes good process and algorithms for doing cross-checking across people's inputs on each tile. Was used by the SBTF to map buildings in Afgooye Somalia for UN refugee agency.<br />
<br />
Do Tomnod do public reports of how it's used, effectiveness, etc? Probably: the outcome on the climbers was that their basecamp was found through the Tomnod search, which got the rescue team to it quickly. Satellite images always take a while to make available, which is why Sara et are also investigating UAV use for humanitarian applications; in this case, the UAVs would probably have had problems with the altitude (this affects smaller UAVs), so we still would have needed satellite imagery.<br />
<br />
===Data storage for the digital humanitarian space===<br />
There is lots of data coming available from deployments, exercises etc: where can we collectively put it? CrisisCommons is planning a common data area; digital humanitarians are working on one, as are the UNOCHA data teams. Sara suggested somewhere like buzzdata,which can have hidden datasets; or perhaps dropbox (with people invited in) for the moment. Agreement that any storage area should be accessible to all actors - i.e. if using a digital humanitarian area, should be available to non-members of it or won't be useful.<br />
[[Category:Checkin call]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=2012_Sept_12&diff=3002012 Sept 122016-10-26T18:22:18Z<p>Willow: Created page with "{{Why Call Ins?}} ==Attendees:== ''List yourselves out as you join the call, the order we go in will be determined by this. Willow goes last.'' * Evert with Haiti Connect *..."</p>
<hr />
<div>{{Why Call Ins?}} <br />
==Attendees:==<br />
''List yourselves out as you join the call, the order we go in will be determined by this. Willow goes last.''<br />
<br />
* Evert with Haiti Connect<br />
* Cat with Humanity Road<br />
* Scott with FEMA<br />
* Pascal with Crisis Commons<br />
* Jen with Crisis Mappers<br />
* Willow with Geeks Without Bounds<br />
<br />
==Agenda:==<br />
What we're up to today - Willow<br />
Organizational overview - what has everyone been up to? Take 3 minutes tops<br />
* Person before you in the list takes notes. (A takes notes for B)<br />
* Person after you keeps time. (C keeps time for B)<br />
Final notes / thoughts / potential overlaps<br />
<br />
==Organisational Overview==<br />
===Cat with Humanity Road===<br />
This week's Situation [http://tropic.ssec.wisc.edu/real-time/mimic-tpw/global/main.html Report ] - From Maine to Nova Scotia - overview on Leslie hitting Newfoundland. Also wanted to let folks know about an event our volunteers monitored this week for impact. One brought in the Mexico shootout panic happening on Twitter. As background on this, drug cartels in Mexico are killing folks who report suspicious activity via social media. This new incident covers people who are starting rumors in social media that create panic Mexico . Might be prudent for crisis responses teams in social media to become aware of this type of thing so they are informed of the risks. We attended and facilitated a panel discussion on the [http://thesmileconference.com/ SMILE Conference] #SMILEcon held in Richmond on 9/11. We're attending and looking forward to ICCM.<br />
<br />
===Scott with FEMA===<br />
Deploying a strategy over the next year for FEMA.gov on drupal. Expect to create a number of APIs, raw datasets and feeds. Make some core data available. Try to see areas where we should focus - response or preparedness, long term recovery, fire, etc. Just me part time right now, will get some staff later. Going to ICCM to listen, but got some requirements from Willow to make an announcement or make shelters available. Real-time system of status and location. White House's safety.data.gov datasets and tools around residential fire and incidence. Expanded sets on flood and such. KML google overlay but want to get to more of a web service capability, facilitate applications. Need requirements for datasets, how FEMA can help.<br />
<br />
===Jen with ICCM===<br />
Coming along really well<br />
<br />
===Pascal with Crisis Commons and UW===<br />
Trying to build out capability for legal org, signed docs. Working on project with GWOB and Gisli and Microsoft on building a place for better tools, continuity, maintain better documentation and support for tools and projects. Researchable, people can find things. If it was built awhile ago, you can go grab it and modify it. Part of Visual Studio release. Not a MSFT only product, will be open and not owned.<br />
<br />
===Evert with Haiti Connect===<br />
Bringing IT infrastructure to schools hospitals etc. Based in Ireland, all volunteer. Expanding, building a dedicated response team. Using wifi to respond and support, a physical network. Software management. Can be a wide network area, manage access. Geolocation and disaster response inherent in network, anyone connected can use it. Making sure you have the right datasets, using google library etc.<br />
<br />
===Willow with GWOB ===<br />
Accelerator teams working on Drought tracking, monitoring medical devices, educational standards ensuring teachers are spending more time with students and less time on lesson plans. Working with AT&amp;T with hackathon, and upcoming hackathon in Birmingham H4D2.EU - front loading it with datasets. Talking to Digital Democracy in Haiti on gender based violence.<br />
==Post- intro discussions==<br />
* Evert needs to meet up with some people. What sorts of data should be plugged into their network when it deploys?<br />
* What format is the data from FEMA in? That can be part of the request as well. Raw datasets, i.e.: GIS do raw shape files. Along lines of Digital Government Strategy; create APIs. No limit on the format of a delivery mechanism. How do we know what is the most up to date? i.e.: HAZUS hospital layer.<br />
==Follow-up / Action Items:==<br />
Send dataset requests to Scott at FEMA (ping Willow for contact) - want to collaborate in a meaningful way. Hospitals are requested. Shelters and flood planes are coming out.<br />
[[Category:Checkin call]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Template:Checkin_Call_Summaries&diff=299Template:Checkin Call Summaries2016-10-26T18:15:04Z<p>Willow: </p>
<hr />
<div>* [[2016 May 23]] : updates on HumTechFest, discussion on the blockchain in response, and questions about international consortium, health site data, the digital response ecosystem map, and urban resilience.<br />
* [[2016 April 12]] : updates from Resilience CoLab, JIFX, prosthetic environments, Coordinated Data Scramble, and decision maker's needs.<br />
* [[2015 Nov 27]] : updates on Humanitarian Services Data Standards Project, Resilience CoLab, Witness Engines/Crisis Archiving, Secure Web Integration Framework, JIFX, Sahana Eden supply and volunteer management database, and RHoK<br />
* [[2015 Sept 23]] : updates on the handbook, ResilienceCoLab, and 2W doc. Also talked about RefugeesWelcome, JIFX, the Earthquake Coordinated Data Scramble, and communication methods (the drafted Code of Conduct for open comms channels, how the call-in platform was working, and how to select other comms platforms).<br />
* [[2015 Aug 06]] : the band is back together! A firehose of a call, many folk gave a quick overview of themselves and their organizations. We also did quick indicators of projects we're working on and how we could use help.<br />
* [[2012 Sept 12]] : updates about how to get data into and out of FEMA.<br />
* [[2012 Jul 31]] : notes from a call while with Geeks Without Bounds with organizational updates from Crisis Commons, Humanity Road, and Standby Task Force about a data commons.<br />
<br />
[[Category:Checkin call]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Digital_response_ecosystem_map&diff=298Digital response ecosystem map2016-10-24T23:03:33Z<p>Willow: /* Current status and how to get involved */</p>
<hr />
<div>{{About Projects}}<br />
<br />
==Is there a digital response ecosystem?==<br />
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.<br />
<br />
==The problem==<br />
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.<br />
<br />
==Benefit of an Ecosystem Map==<br />
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.<br />
<br />
==Current status and how to get involved==<br />
'''[https://docs.google.com/document/d/1PL3SAvdPg7XzpG5kfVW3hvEfD1hE6Kx95oAMwJENRdY/edit?usp=sharing North Star]''' : our in-process guiding document (or "concept note").<br />
<br />
'''[https://airtable.com/shrN8OGsjYjCjjmR6/tblhLsKuNHNRo1PDz/viwZXkcUR6S0Uciis Backend]''' : where our collaboratively-held data lives.<br />
<br />
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<br />
* as a remote session May 31st 9a PT/12p ET,<br />
* at the [[2016 June HumTechFest]] as a session on June 5th,<br />
* June 7th and 8th as interactive wall art at the [http://humanitariantechnology.org/ Humanitarian Technology Innovation Conference],<br />
* at the [http://msfcanada-logday2016.azurewebsites.net/ Doctors Without Borders Canada logistics day] June 10th, and<br />
* at the [[2016 June Meet Up]] on June 16th from 18:00-21:00 in San Francisco, CA!<br />
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].<br />
<br />
[[Category: Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Main_Page&diff=297Main Page2016-10-24T22:54:57Z<p>Willow: /* Projects */ now includes more of a narrative arc about how all these different projects are related.</p>
<hr />
<div>{{About Digital Response}}<br />
<br />
==Join the Conversation==<br />
===Mailing List===<br />
Our '''[https://lists.aspirationtech.org/lists/info/digitalresponse mailing list]''' includes updates about digital responder call-ins, upcoming events, and cross-sector collaborative discussion.<br />
<br />
===Check In Calls===<br />
{{Why Call Ins?}}<br />
<br />
There is a template for how to conduct a digital responder checkin call on the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call checkin call category page]. That page will also give a process for adding your own calls to this wiki.<br />
<br />
{{Checkin Call Summaries}}<br />
<br />
===Direct Contact===<br />
Have a question about this program, but don't necessarily want to talk to a whole group? No worries! Reach out to [mailto:digitalresponse@aspirationtech.org digitalresponse@aspirationtech.org] to be in touch with us directly.<br />
<br />
==[https://digitalresponse.aspirationtech.org/index.php?title=Category:Events Events]==<br />
===Humanitarian Technology Festival===<br />
{{About HumTechFest}}<br />
* [[2016 June HumTechFest]] : June 4th and 5th in Cambridge, Mass. We played a scenario, talked a lot about institutional and grassroots collaboration, and worked on the [[Digital response ecosystem map]].<br />
* [[2015 May MIT|2015 May HumTechFest]] : our first HumTechFest! We talked about how frontline communities could hold responders accountable, did skill shares around open data, and spec'd out easy-to-create after action report templates.<br />
<br />
===Digital Responder Meetups===<br />
{{About Meetups}}<br />
<br />
{{Meetup Summaries}}<br />
<br />
==Projects==<br />
{{About Projects}}<br />
<br />
===[[Digital response ecosystem map]]===<br />
Our knowledge base is housed in the '''[[Digital response ecosystem map]]'''. This is a living knowledge base of tools, personas, resources, etc is maintained collectively by digital responders. The wiki page links to the context, concept note, backend, and places to have further conversation. We view this as a baseline for decision making, for gap analysis, and for resource creation.<br />
* You can add '''resources''' and '''tools''' quickly to the ecosystem map by using a [[Bookmarklet to log projects]].<br />
* The ecosystem map may eventually be presented in more detail similar to our [[Communication tools matrix]]. Every extreme event is different, but all involve coordinating across many different organizations, timezones, politics, etc. We're working to understand the potential constraints and needs of each response, and to map existing communication tools to those needs for speedy selection and setup.<br />
===Projects informed by the ecosystem map===<br />
The ecosystem map points at a few gaps in '''resources''' available for '''personas''' at various points in their '''workflows'''. We have started working on creating resources to fill these gaps. These might be '''Before You Jump In Guides''', which are for digital responders and the intermediaries working with them. These help to scope challenges, point at other possible challenges, and lay some ground work for taking next steps. After a choice about implementing a certain aspect of digital response has been come to, '''Field Guides''' help by providing a series of questions to ask before starting. These questions can help in searching the ecosystem map for a tool which is best suited for a specific context.<br />
* [[Before you jump in: Missing Persons]] : a guide in how (and when) to build or contribute to a missing persons application.<br />
* [[Extreme event preparedness and response for small nonprofits]] : guide for small non profits and other community groups to prepare for, and respond to, crisis.<br />
===A handbook for digital responders===<br />
Once the ecosystem is better defined (and those definitions tested and socialized); resources are located, curated, and created; and trends emerge, we might begin to work on a handbook for working with digital responders.<br />
===Additional Projects===<br />
* [[Frontline communities holding responders accountable]] : response organizations and individual responders are vital contributors to safety, rebuilding, logistics, etc in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so? This project suggests a transparency report for how the needs of an affected population were (or were not) addressed by those claiming to do so.<br />
* [[Media guide for extreme events]] : crises are often accompanied by a media frenzy, and those already stressed because of the impact on their lives are also expected to be spokespeople for their neighborhood. If you're a reporter, how can you act in good faith in an affected region? If you're a member of the affected population, what are ways to approach media inquiries from a social justice perspective?<br />
<br />
==Response Groups and Projects Aspiration Works With==<br />
* [http://climatecentre.org Red Cross Red Crescent Climate Centre] : on [https://aspirationtech.org/blog/willow/nairobi_spring2015 games about citizen reporting], on crowd integration.<br />
* [https://aspirationtech.org/blog/willow/nairobi_spring2015 Dialling Up Resilience] : on accountability mechanisms and local indicators of resilience.<br />
* [http://www.hirondellenews.com/ Hirondelle] : on visually representing their communications network.<br />
<br />
==Words on the Subject==<br />
===The topic on our blog===<br />
Follow and comment on [https://aspirationtech.org/taxonomy/term/72 topical blog entries].<br />
<br />
===Recommended Reading===<br />
* [http://www.democracynow.org/2009/8/31/a_paradise_built_in_hell_rebecca A Paradise Built in Hell] : an easy-to-ready overview of disaster sociology, how people behave in crisis (spoiler: it's not every person for themselves).<br />
* [https://archive.org/details/BlackFlagsAndWindmills Black Flags and Windmills] : review of the politicized relief efforts for Hurricane Katrina performed by the Common Ground Collective.<br />
* [http://cdacollaborative.org/publication/do-no-harm-how-aid-can-support-peace-or-war/ Do No Harm] : review and framework for how to deploy resources into conflict zones without exacerbating the conflict.<br />
The GovLab also has a [http://thegovlab.org/data-and-humanitarian-response/ list of selected readings] worth checking out.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Bookmarklet_to_log_projects&diff=296Bookmarklet to log projects2016-10-24T22:10:19Z<p>Willow: </p>
<hr />
<div>{{About Projects}}<br />
<br />
==Context==<br />
The [[Digital response ecosystem map]] is a great resource, but pulling up the backend each time you stumble across a new project or resource which should be included in it is cumbersome. [http://www.brentdixon.cc Brent] made these two bookmarklets which make it easy to add '''tools''' and '''resources''' to our [[Digital response ecosystem map]]. <br />
<br />
==Implementation==<br />
You can add them to your browser by clicking "bookmarks" > "add bookmark" > add to bookmarks bar > pasting the following as the name and URL.<br />
<br />
===Add Tools Bookmarklet===<br />
'''Name''': Add this as a Tool to Digital Response Ecosystem Map<br />
<br />
'''URL''': <nowiki>javascript:(function(){f="https://airtable.com/shrHlhobMJH3FUvxk?prefill_Tools="+encodeURIComponent(document.title)+"&prefill_Demo or Website URL="+encodeURIComponent(window.location.href);a=function(){if(!window.open(f,"mightchange","location=yes,links=no,scrollbars=no,toolbar=no,width=450,height=650")){location.href=f}};if(/Firefox/.test(navigator.userAgent)){setTimeout(a,0)}else{a()}})();</nowiki><br />
<br />
===Add Resources Bookmarklet===<br />
'''Name''': Add this as a Resource to Digital Response Ecosystem Map<br />
<br />
'''URL''': <nowiki>javascript:(function(){f="https://airtable.com/shr7qsihtIGpJzaI4?prefill_Name="+encodeURIComponent(document.title)+"&prefill_Link="+encodeURIComponent(window.location.href);a=function(){if(!window.open(f,"mightchange","location=yes,links=no,scrollbars=no,toolbar=no,width=450,height=650")){location.href=f}};if(/Firefox/.test(navigator.userAgent)){setTimeout(a,0)}else{a()}})();</nowiki><br />
<br />
[[Category:Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Bookmarklet_to_log_projects&diff=295Bookmarklet to log projects2016-10-24T21:41:14Z<p>Willow: </p>
<hr />
<div>{{About Projects}}<br />
<br />
The [[Digital response ecosystem map]] is a great resource, but pulling up the backend each time you stumble across a new project or resource which should be included in it is cumbersome. [http://www.brentdixon.cc Brent] made these two bookmarklets which make it easy to add '''tools''' and '''resources''' to our [[Digital response ecosystem map]]. You can add them to your browser by clicking "bookmarks" > "add bookmark" > add to bookmarks bar > pasting the following as the name and URL.<br />
<br />
==Add Tools Bookmarklet==<br />
'''Name''': Add this as a Tool to Digital Response Ecosystem Map<br />
<br />
'''URL''': <nowiki>javascript:(function(){f="https://airtable.com/shrHlhobMJH3FUvxk?prefill_Tools="+encodeURIComponent(document.title)+"&prefill_Demo or Website URL="+encodeURIComponent(window.location.href);a=function(){if(!window.open(f,"mightchange","location=yes,links=no,scrollbars=no,toolbar=no,width=450,height=650")){location.href=f}};if(/Firefox/.test(navigator.userAgent)){setTimeout(a,0)}else{a()}})();</nowiki><br />
<br />
==Add Resources Bookmarklet==<br />
'''Name''': Add this as a Resource to Digital Response Ecosystem Map<br />
<br />
'''URL''': <nowiki>javascript:(function(){f="https://airtable.com/shr7qsihtIGpJzaI4?prefill_Name="+encodeURIComponent(document.title)+"&prefill_Link="+encodeURIComponent(window.location.href);a=function(){if(!window.open(f,"mightchange","location=yes,links=no,scrollbars=no,toolbar=no,width=450,height=650")){location.href=f}};if(/Firefox/.test(navigator.userAgent)){setTimeout(a,0)}else{a()}})();</nowiki><br />
<br />
[[Category:Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Bookmarklet_to_log_projects&diff=294Bookmarklet to log projects2016-10-24T21:40:24Z<p>Willow: </p>
<hr />
<div>{{About Projects}}<br />
<br />
The [[Digital response ecosystem map]] is a great resource, but pulling up the backend each time you stumble across a new project or resource which should be included in it is cumbersome. [http://www.brentdixon.cc Brent] made these two bookmarklets which make it easy to add '''tools''' and '''resources''' to our [[Digital response ecosystem map]]. You can add them to your browser by clicking "bookmarks" > "add bookmark" > add to bookmarks bar > pasting the following as the name and URL.<br />
<br />
==Add Tools Bookmarklet==<br />
'''Name''': Add this as a Tool to Digital Response Ecosystem Map<br />
'''URL''': javascript:(function(){f="https://airtable.com/shrHlhobMJH3FUvxk?prefill_Tools="+encodeURIComponent(document.title)+"&prefill_Demo or Website URL="+encodeURIComponent(window.location.href);a=function(){if(!window.open(f,"mightchange","location=yes,links=no,scrollbars=no,toolbar=no,width=450,height=650")){location.href=f}};if(/Firefox/.test(navigator.userAgent)){setTimeout(a,0)}else{a()}})();<br />
<br />
==Add Resources Bookmarklet==<br />
'''Name''': Add this as a Resource to Digital Response Ecosystem Map<br />
'''URL''': javascript:(function(){f="https://airtable.com/shr7qsihtIGpJzaI4?prefill_Name="+encodeURIComponent(document.title)+"&prefill_Link="+encodeURIComponent(window.location.href);a=function(){if(!window.open(f,"mightchange","location=yes,links=no,scrollbars=no,toolbar=no,width=450,height=650")){location.href=f}};if(/Firefox/.test(navigator.userAgent)){setTimeout(a,0)}else{a()}})();<br />
<br />
[[Category:Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Digital_response_ecosystem_map&diff=293Digital response ecosystem map2016-09-08T15:55:24Z<p>Willow: /* Current status and how to get involved */</p>
<hr />
<div>{{About Projects}}<br />
<br />
==Is there a digital response ecosystem?==<br />
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.<br />
<br />
==The problem==<br />
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.<br />
<br />
==Benefit of an Ecosystem Map==<br />
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.<br />
<br />
==Current status and how to get involved==<br />
The map draft is currently available to be viewed [https://docs.google.com/spreadsheets/d/1Pt3hQpz0tXz0ROF5s39TzqoI1UzAFO4Tg1qpyMYgEsU/edit#gid=2130673778 here]. We welcome your feedback and contributions!<br />
<br />
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<br />
* as a remote session May 31st 9a PT/12p ET,<br />
* at the [[2016 June HumTechFest]] as a session on June 5th,<br />
* June 7th and 8th as interactive wall art at the [http://humanitariantechnology.org/ Humanitarian Technology Innovation Conference],<br />
* at the [http://msfcanada-logday2016.azurewebsites.net/ Doctors Without Borders Canada logistics day] June 10th, and<br />
* at the [[2016 June Meet Up]] on June 16th from 18:00-21:00 in San Francisco, CA!<br />
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].<br />
<br />
[[Category: Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Main_Page&diff=292Main Page2016-09-08T15:52:50Z<p>Willow: /* Projects */</p>
<hr />
<div>{{About Digital Response}}<br />
<br />
==Join the Conversation==<br />
===Mailing List===<br />
Our '''[https://lists.aspirationtech.org/lists/info/digitalresponse mailing list]''' includes updates about digital responder call-ins, upcoming events, and cross-sector collaborative discussion.<br />
<br />
===Check In Calls===<br />
{{Why Call Ins?}}<br />
<br />
There is a template for how to conduct a digital responder checkin call on the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call checkin call category page]. That page will also give a process for adding your own calls to this wiki.<br />
<br />
{{Checkin Call Summaries}}<br />
<br />
===Direct Contact===<br />
Have a question about this program, but don't necessarily want to talk to a whole group? No worries! Reach out to [mailto:digitalresponse@aspirationtech.org digitalresponse@aspirationtech.org] to be in touch with us directly.<br />
<br />
==[https://digitalresponse.aspirationtech.org/index.php?title=Category:Events Events]==<br />
===Humanitarian Technology Festival===<br />
{{About HumTechFest}}<br />
* [[2016 June HumTechFest]] : June 4th and 5th in Cambridge, Mass. We played a scenario, talked a lot about institutional and grassroots collaboration, and worked on the [[Digital response ecosystem map]].<br />
* [[2015 May MIT|2015 May HumTechFest]] : our first HumTechFest! We talked about how frontline communities could hold responders accountable, did skill shares around open data, and spec'd out easy-to-create after action report templates.<br />
<br />
===Digital Responder Meetups===<br />
{{About Meetups}}<br />
<br />
{{Meetup Summaries}}<br />
<br />
==Projects==<br />
{{About Projects}}<br />
* [[Digital response ecosystem map]] : some official organizations have name-brand recognition, but there is little understanding of the local, emerging, and digital sectors of disaster and humanitarian response. Additionally, the flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem. Describing that system is a step towards understanding.<br />
* [[Extreme event preparedness and response for small nonprofits]] : guide for small non profits and other community groups to prepare for, and respond to, crisis.<br />
* [[Before you jump in: Missing Persons]] : a guide in how (and when) to build or contribute to a missing persons application.<br />
* [[Frontline communities holding responders accountable]] : response organizations and individual responders are vital contributors to safety, rebuilding, logistics, etc in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so? This project suggests a transparency report for how the needs of an affected population were (or were not) addressed by those claiming to do so.<br />
* [[Bookmarklet to log projects]] : many do-good projects exist across many organizations, spaces, and events. Some were created at hackathons, some have nothing to do with response (but could be useful in crises), and there is no repository of these projects for those building or needing tools. How can we log them in a decentralized way?<br />
* [[Media guide for extreme events]] : crises are often accompanied by a media frenzy, and those already stressed because of the impact on their lives are also expected to be spokespeople for their neighborhood. If you're a reporter, how can you act in good faith in an affected region? If you're a member of the affected population, what are ways to approach media inquiries from a social justice perspective?<br />
* [[Communication tools matrix]] : every extreme event is different, but all involve coordinating across many different organizations, timezones, politics, etc. We're working to understand the potential needs of each response, and to map existing communication tools to those needs for speedy selection and setup.<br />
<br />
==Response Groups and Projects Aspiration Works With==<br />
* [http://climatecentre.org Red Cross Red Crescent Climate Centre] : on [https://aspirationtech.org/blog/willow/nairobi_spring2015 games about citizen reporting], on crowd integration.<br />
* [https://aspirationtech.org/blog/willow/nairobi_spring2015 Dialling Up Resilience] : on accountability mechanisms and local indicators of resilience.<br />
* [http://www.hirondellenews.com/ Hirondelle] : on visually representing their communications network.<br />
<br />
==Words on the Subject==<br />
===The topic on our blog===<br />
Follow and comment on [https://aspirationtech.org/taxonomy/term/72 topical blog entries].<br />
<br />
===Recommended Reading===<br />
* [http://www.democracynow.org/2009/8/31/a_paradise_built_in_hell_rebecca A Paradise Built in Hell] : an easy-to-ready overview of disaster sociology, how people behave in crisis (spoiler: it's not every person for themselves).<br />
* [https://archive.org/details/BlackFlagsAndWindmills Black Flags and Windmills] : review of the politicized relief efforts for Hurricane Katrina performed by the Common Ground Collective.<br />
* [http://cdacollaborative.org/publication/do-no-harm-how-aid-can-support-peace-or-war/ Do No Harm] : review and framework for how to deploy resources into conflict zones without exacerbating the conflict.<br />
The GovLab also has a [http://thegovlab.org/data-and-humanitarian-response/ list of selected readings] worth checking out.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Template:Meetup_Summaries&diff=291Template:Meetup Summaries2016-08-16T21:39:05Z<p>Willow: </p>
<hr />
<div>* [[2016 August Meet Up]] : August 11th in San Francisco, CA. We chatted about HAM radio, community mesh networks, and why we do what we do.<br />
* [[2016 June Meet Up]] : June 16th in San Francisco, CA. We reviewed MapSwipe, how cross-sector communication works, the ecosystem map, and basic ways of plugging into digital response activities.<br />
<br />
[[Category:MeetUp]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=2016_August_Meet_Up&diff=2902016 August Meet Up2016-08-16T21:38:15Z<p>Willow: </p>
<hr />
<div>==About this August checkin==<br />
* MeetUp took place '''Thursday August 11th''' at 17:30 (5:30p) Pacific Time at the [http://sftechcenter.org San Francisco Nonprofit Technology Center] located at '''2973 16th St''' in San Francisco.<br />
* Read more [https://aspirationtech.org/events/digitalresponsemeetup/sanfrancisco/2016/august on our website].<br />
<br />
We chatted about HAM radio, mesh networks, and temporary autonomous zones.<br />
<br />
<br />
[[Category:MeetUp|Events|Nonprofit Tech Center]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=289Category:MeetUp2016-08-16T21:36:07Z<p>Willow: /* Past call links and summaries */</p>
<hr />
<div> This page is a work in progress. Parts of it will be wrong and/or incomplete.<br />
Contributions, suggestions, etc always welcome!<br />
<br />
==Why host meetups for digital responders?==<br />
{{About Meetups}}<br />
<br />
==Scaffolding and resources for hosting a meetup with us or elsewhere==<br />
===Components===<br />
We've found the following to be essential to a group check-in:<br />
* '''Where''' will the meetup take place? : You'll need a physical location. If you're wanting to do a remote session (either with some or all participants), you might find benefit from the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call guide for checkin calls].<br />
* '''When''' will the meetup happen? : The date and time (include the timezone if you have travelers or remote participants!).<br />
* '''What''' will be talked about? : Talk with participants about what's on their minds.<br />
* '''Who''' are you inviting? : Invitee list (organizations and/or individuals).<br />
: We have a mailing list which is invited first, and can be registered for via the [[Main Page]]<br />
<br />
===For attendees===<br />
* '''Be prepared''' : Think about what you want out of the meetup. Are you looking for help on something? Want to give an update on a project? Looking to hear what others are up to? All of these (and more) are great!<br />
* '''Be present''' : Sharing of information requires a receiver. Don't just think about what you'd like to ''say'' to everyone, demonstrate respect by paying attention when others are speaking.<br />
* '''Contribute''' : The facilitator is likely juggling multiple things. The person speaking can rarely/not take notes for themselves as they speak. We rely on the group to document meaningful exchanges, and that means me/you/us documenting, asking questions, offering suggestions.<br />
<br />
===For organizers===<br />
Be clear (but not spammy) about letting people know about the event.<br />
====Pre-MeetUp====<br />
# Make an event page on your website.<br />
# Make a way for people to register (by email, event-specific site, or social media forum.)<br />
# Add a stubbed '''wiki page''' linked to from the [[Template:Meetup Summaries|list of events]]. Our [[MeetUp wiki page template]] may come in handy.<br />
# Invite folk to your event. We announce these meetups to<br />
## [https://lists.aspirationtech.org/lists/info/digitalresponse our digital response mailing list],<br />
## the Digital Humanitarian Network mailing list, and <br />
## the DHN skype channel.<br />
# '''1 or 2 days''' before the event, remind people about the meetup's time and location.<br />
<br />
====Post-MeetUp====<br />
Participants should know they have a set amount of time to add in edits and to make deletions before the notes go in a public-facing location.<br />
# '''1 or 2 days''' after the event, transfer the notes from a collaborative note-taking platform to the '''wiki page'''. ''The only thing left on the riseup pad should be a link to the wiki page''.<br />
# Send out a link to the wiki page, plus thanks and top-level analysis to the same channels the meetup was announced to. Ask if anyone is uncomfortable sharing their contact with other participants.<br />
# '''1 week after the meetup''', send out the participant list and invite everyone to the digital responder mailing list. ''Do not opt them in, let them do it (or not) themselves.''<br />
<br />
===For facilitators===<br />
* Work with participants on the agenda.<br />
* Try to start on time, which means you will need to be present to set up the space about a half hour early.<br />
* Try to end at least a few minutes early.<br />
* Remember the entirety of the group is who you serve, and be ok interrupting someone if they're taking up more than 1/Nth of the time.<br />
<br />
==Past meetup links and summaries==<br />
{{Meetup Summaries}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=288Category:MeetUp2016-08-16T21:35:42Z<p>Willow: /* Pre-MeetUp */</p>
<hr />
<div> This page is a work in progress. Parts of it will be wrong and/or incomplete.<br />
Contributions, suggestions, etc always welcome!<br />
<br />
==Why host meetups for digital responders?==<br />
{{About Meetups}}<br />
<br />
==Scaffolding and resources for hosting a meetup with us or elsewhere==<br />
===Components===<br />
We've found the following to be essential to a group check-in:<br />
* '''Where''' will the meetup take place? : You'll need a physical location. If you're wanting to do a remote session (either with some or all participants), you might find benefit from the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call guide for checkin calls].<br />
* '''When''' will the meetup happen? : The date and time (include the timezone if you have travelers or remote participants!).<br />
* '''What''' will be talked about? : Talk with participants about what's on their minds.<br />
* '''Who''' are you inviting? : Invitee list (organizations and/or individuals).<br />
: We have a mailing list which is invited first, and can be registered for via the [[Main Page]]<br />
<br />
===For attendees===<br />
* '''Be prepared''' : Think about what you want out of the meetup. Are you looking for help on something? Want to give an update on a project? Looking to hear what others are up to? All of these (and more) are great!<br />
* '''Be present''' : Sharing of information requires a receiver. Don't just think about what you'd like to ''say'' to everyone, demonstrate respect by paying attention when others are speaking.<br />
* '''Contribute''' : The facilitator is likely juggling multiple things. The person speaking can rarely/not take notes for themselves as they speak. We rely on the group to document meaningful exchanges, and that means me/you/us documenting, asking questions, offering suggestions.<br />
<br />
===For organizers===<br />
Be clear (but not spammy) about letting people know about the event.<br />
====Pre-MeetUp====<br />
# Make an event page on your website.<br />
# Make a way for people to register (by email, event-specific site, or social media forum.)<br />
# Add a stubbed '''wiki page''' linked to from the [[Template:Meetup Summaries|list of events]]. Our [[MeetUp wiki page template]] may come in handy.<br />
# Invite folk to your event. We announce these meetups to<br />
## [https://lists.aspirationtech.org/lists/info/digitalresponse our digital response mailing list],<br />
## the Digital Humanitarian Network mailing list, and <br />
## the DHN skype channel.<br />
# '''1 or 2 days''' before the event, remind people about the meetup's time and location.<br />
<br />
====Post-MeetUp====<br />
Participants should know they have a set amount of time to add in edits and to make deletions before the notes go in a public-facing location.<br />
# '''1 or 2 days''' after the event, transfer the notes from a collaborative note-taking platform to the '''wiki page'''. ''The only thing left on the riseup pad should be a link to the wiki page''.<br />
# Send out a link to the wiki page, plus thanks and top-level analysis to the same channels the meetup was announced to. Ask if anyone is uncomfortable sharing their contact with other participants.<br />
# '''1 week after the meetup''', send out the participant list and invite everyone to the digital responder mailing list. ''Do not opt them in, let them do it (or not) themselves.''<br />
<br />
===For facilitators===<br />
* Work with participants on the agenda.<br />
* Try to start on time, which means you will need to be present to set up the space about a half hour early.<br />
* Try to end at least a few minutes early.<br />
* Remember the entirety of the group is who you serve, and be ok interrupting someone if they're taking up more than 1/Nth of the time.<br />
<br />
==Past call links and summaries==<br />
{{Meetup Summaries}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Main_Page&diff=287Main Page2016-08-11T02:38:06Z<p>Willow: /* Projects */</p>
<hr />
<div>{{About Digital Response}}<br />
<br />
==Join the Conversation==<br />
===Mailing List===<br />
Our '''[https://lists.aspirationtech.org/lists/info/digitalresponse mailing list]''' includes updates about digital responder call-ins, upcoming events, and cross-sector collaborative discussion.<br />
<br />
===Check In Calls===<br />
{{Why Call Ins?}}<br />
<br />
There is a template for how to conduct a digital responder checkin call on the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call checkin call category page]. That page will also give a process for adding your own calls to this wiki.<br />
<br />
{{Checkin Call Summaries}}<br />
<br />
===Direct Contact===<br />
Have a question about this program, but don't necessarily want to talk to a whole group? No worries! Reach out to [mailto:digitalresponse@aspirationtech.org digitalresponse@aspirationtech.org] to be in touch with us directly.<br />
<br />
==[https://digitalresponse.aspirationtech.org/index.php?title=Category:Events Events]==<br />
===Humanitarian Technology Festival===<br />
{{About HumTechFest}}<br />
* [[2016 June HumTechFest]] : June 4th and 5th in Cambridge, Mass. We played a scenario, talked a lot about institutional and grassroots collaboration, and worked on the [[Digital response ecosystem map]].<br />
* [[2015 May MIT|2015 May HumTechFest]] : our first HumTechFest! We talked about how frontline communities could hold responders accountable, did skill shares around open data, and spec'd out easy-to-create after action report templates.<br />
<br />
===Digital Responder Meetups===<br />
{{About Meetups}}<br />
<br />
{{Meetup Summaries}}<br />
<br />
==Projects==<br />
{{About Projects}}<br />
* [[Digital response ecosystem map]] : some official organizations have name-brand recognition, there is little understanding of the local, emerging, and digital sectors. Additionally, the flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem. <br />
* [[Extreme event preparedness and response for small nonprofits]] : guide for small non profits and other community groups to prepare for, and respond to, crisis.<br />
* [[Before you jump in: Missing Persons]] : a guide in how (and when) to build or contribute to a missing persons application.<br />
* [[Frontline communities holding responders accountable]] : response organizations and individual responders are vital contributors to safety, rebuilding, logistics, etc in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so? This project suggests a transparency report for how the needs of an affected population were (or were not) addressed by those claiming to do so.<br />
* [[Bookmarklet to log projects]] : many do-good projects exist across many organizations, spaces, and events. Some were created at hackathons, some have nothing to do with response (but could be useful in crises), and there is no repository of these projects for those building or needing tools. How can we log them in a decentralized way?<br />
* [[Media guide for extreme events]] : crises are often accompanied by a media frenzy, and those already stressed because of the impact on their lives are also expected to be spokespeople for their neighborhood. If you're a reporter, how can you act in good faith in an affected region? If you're a member of the affected population, what are ways to approach media inquiries from a social justice perspective?<br />
* [[Communication tools matrix]] : every extreme event is different, but all involve coordinating across many different organizations, timezones, politics, etc. We're working to understand the potential needs of each response, and to map existing communication tools to those needs for speedy selection and setup.<br />
<br />
==Response Groups and Projects Aspiration Works With==<br />
* [http://climatecentre.org Red Cross Red Crescent Climate Centre] : on [https://aspirationtech.org/blog/willow/nairobi_spring2015 games about citizen reporting], on crowd integration.<br />
* [https://aspirationtech.org/blog/willow/nairobi_spring2015 Dialling Up Resilience] : on accountability mechanisms and local indicators of resilience.<br />
* [http://www.hirondellenews.com/ Hirondelle] : on visually representing their communications network.<br />
<br />
==Words on the Subject==<br />
===The topic on our blog===<br />
Follow and comment on [https://aspirationtech.org/taxonomy/term/72 topical blog entries].<br />
<br />
===Recommended Reading===<br />
* [http://www.democracynow.org/2009/8/31/a_paradise_built_in_hell_rebecca A Paradise Built in Hell] : an easy-to-ready overview of disaster sociology, how people behave in crisis (spoiler: it's not every person for themselves).<br />
* [https://archive.org/details/BlackFlagsAndWindmills Black Flags and Windmills] : review of the politicized relief efforts for Hurricane Katrina performed by the Common Ground Collective.<br />
* [http://cdacollaborative.org/publication/do-no-harm-how-aid-can-support-peace-or-war/ Do No Harm] : review and framework for how to deploy resources into conflict zones without exacerbating the conflict.<br />
The GovLab also has a [http://thegovlab.org/data-and-humanitarian-response/ list of selected readings] worth checking out.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Digital_response_ecosystem_map&diff=286Digital response ecosystem map2016-07-27T21:34:57Z<p>Willow: /* The problem */</p>
<hr />
<div>{{About Projects}}<br />
<br />
==Is there a digital response ecosystem?==<br />
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.<br />
<br />
==The problem==<br />
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.<br />
<br />
==Benefit of an Ecosystem Map==<br />
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.<br />
<br />
==Current status and how to get involved==<br />
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<br />
* as a remote session May 31st 9a PT/12p ET,<br />
* at the [[2016 June HumTechFest]] as a session on June 5th,<br />
* June 7th and 8th as interactive wall art at the [http://humanitariantechnology.org/ Humanitarian Technology Innovation Conference],<br />
* at the [http://msfcanada-logday2016.azurewebsites.net/ Doctors Without Borders Canada logistics day] June 10th, and<br />
* at the [[2016 June Meet Up]] on June 16th from 18:00-21:00 in San Francisco, CA!<br />
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].<br />
<br />
[[Category: Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Digital_response_ecosystem_map&diff=285Digital response ecosystem map2016-07-27T21:34:04Z<p>Willow: /* Is there a digital response ecosystem? */</p>
<hr />
<div>{{About Projects}}<br />
<br />
==Is there a digital response ecosystem?==<br />
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.<br />
<br />
==The problem==<br />
While some official organizations have name-brand recognition, there is little understanding of the local, emerging, and digital sectors. Additionally, the flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem.<br />
<br />
==Benefit of an Ecosystem Map==<br />
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.<br />
<br />
==Current status and how to get involved==<br />
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<br />
* as a remote session May 31st 9a PT/12p ET,<br />
* at the [[2016 June HumTechFest]] as a session on June 5th,<br />
* June 7th and 8th as interactive wall art at the [http://humanitariantechnology.org/ Humanitarian Technology Innovation Conference],<br />
* at the [http://msfcanada-logday2016.azurewebsites.net/ Doctors Without Borders Canada logistics day] June 10th, and<br />
* at the [[2016 June Meet Up]] on June 16th from 18:00-21:00 in San Francisco, CA!<br />
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].<br />
<br />
[[Category: Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Digital_response_ecosystem_map&diff=284Digital response ecosystem map2016-07-19T18:26:55Z<p>Willow: /* Current status and how to get involved */</p>
<hr />
<div>{{About Projects}}<br />
<br />
==Is there a digital response ecosystem?==<br />
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. Frontline populations in affected regions continue to use the 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 use their existing technical infrastructure and new 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.<br />
<br />
==The problem==<br />
While some official organizations have name-brand recognition, there is little understanding of the local, emerging, and digital sectors. Additionally, the flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem.<br />
<br />
==Benefit of an Ecosystem Map==<br />
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.<br />
<br />
==Current status and how to get involved==<br />
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<br />
* as a remote session May 31st 9a PT/12p ET,<br />
* at the [[2016 June HumTechFest]] as a session on June 5th,<br />
* June 7th and 8th as interactive wall art at the [http://humanitariantechnology.org/ Humanitarian Technology Innovation Conference],<br />
* at the [http://msfcanada-logday2016.azurewebsites.net/ Doctors Without Borders Canada logistics day] June 10th, and<br />
* at the [[2016 June Meet Up]] on June 16th from 18:00-21:00 in San Francisco, CA!<br />
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].<br />
<br />
[[Category: Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=2016_August_Meet_Up&diff=2832016 August Meet Up2016-07-18T19:55:49Z<p>Willow: Created page with "==About this August checkin== * MeetUp will take place '''Thursday August 11th''' at 17:30 (5:30p) Pacific Time at the [http://sftechcenter.org San Francisco Nonprofit Technol..."</p>
<hr />
<div>==About this August checkin==<br />
* MeetUp will take place '''Thursday August 11th''' at 17:30 (5:30p) Pacific Time at the [http://sftechcenter.org San Francisco Nonprofit Technology Center] located at '''2973 16th St''' in San Francisco.<br />
* Read more [https://aspirationtech.org/events/digitalresponsemeetup/sanfrancisco/2016/august on our website].<br />
* Registration coming soon.<br />
<br />
<br />
[[Category:MeetUp|Events|Nonprofit Tech Center]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=MeetUp_wiki_page_template&diff=282MeetUp wiki page template2016-07-18T19:33:59Z<p>Willow: /* Template */</p>
<hr />
<div>==Template==<br />
<nowiki>==About this MONTH checkin==</nowiki><br />
<br />
<nowiki>The agenda and notes for this call are taking shape on [http://pad.riseup.net/p/monthdigitalrespondermeetup this riseup pad] - please join us there! After the call is complete, the notes will be transfered back to this wiki page for long-term keeping.<br />
<br />
<nowiki>* MeetUp will take place '''day month date''' at time (timeA/P) Pacific Time.</nowiki><br />
<br />
<nowiki>* The location is ADDRESS.</nowiki><br />
<br />
<nowiki>* The event page can be found [https://aspirationtech.org/events/digitalresponsemeetup/city/year/month here].</nowiki><br />
<br />
<nowiki>* If people need to register, indicate as such here.</nowiki><br />
<br />
<br />
<nowiki>[[Category:MeetUp|Events|Nonprofit Tech Center]]</nowiki><br />
<br />
==Which looks like==<br />
===About this MONTH checkin===<br />
The agenda and notes for this call are taking shape on [http://pad.riseup.net/p/monthdigitalrespondermeetup this riseup pad] - please join us there! After the call is complete, the notes will be transfered back to this wiki page for long-term keeping.<br />
* MeetUp will take place '''day month date''' at time (timeA/P) Pacific Time.<br />
* The location is ADDRESS.<br />
* The event page can be found [https://aspirationtech.org/events/digitalresponsemeetup/city/year/month here].<br />
* If people need to register, indicate as such here.<br />
<br />
[[Category:MeetUp|Events|Nonprofit Tech Center]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=MeetUp_wiki_page_template&diff=281MeetUp wiki page template2016-07-18T19:33:31Z<p>Willow: /* Template */</p>
<hr />
<div>==Template==<br />
<nowiki>==About this MONTH checkin==</nowiki><br />
<nowiki>The agenda and notes for this call are taking shape on [http://pad.riseup.net/p/monthdigitalrespondermeetup this riseup pad] - please join us there! After the call is complete, the notes will be transfered back to this wiki page for long-term keeping.<br />
<nowiki>* MeetUp will take place '''day month date''' at time (timeA/P) Pacific Time.</nowiki><br />
<nowiki>* The location is ADDRESS.</nowiki><br />
<nowiki>* The event page can be found [https://aspirationtech.org/events/digitalresponsemeetup/city/year/month here].</nowiki><br />
<nowiki>* If people need to register, indicate as such here.</nowiki><br />
<br />
<nowiki>[[Category:MeetUp|Events|Nonprofit Tech Center]]</nowiki><br />
<br />
==Which looks like==<br />
===About this MONTH checkin===<br />
The agenda and notes for this call are taking shape on [http://pad.riseup.net/p/monthdigitalrespondermeetup this riseup pad] - please join us there! After the call is complete, the notes will be transfered back to this wiki page for long-term keeping.<br />
* MeetUp will take place '''day month date''' at time (timeA/P) Pacific Time.<br />
* The location is ADDRESS.<br />
* The event page can be found [https://aspirationtech.org/events/digitalresponsemeetup/city/year/month here].<br />
* If people need to register, indicate as such here.<br />
<br />
[[Category:MeetUp|Events|Nonprofit Tech Center]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=MeetUp_wiki_page_template&diff=280MeetUp wiki page template2016-07-18T19:32:50Z<p>Willow: Created page with "==Template== <nowiki>==About this MONTH checkin== The agenda and notes for this call are taking shape on [http://pad.riseup.net/p/monthdigitalrespondermeetup this riseup pad]..."</p>
<hr />
<div>==Template==<br />
<nowiki>==About this MONTH checkin==<br />
The agenda and notes for this call are taking shape on [http://pad.riseup.net/p/monthdigitalrespondermeetup this riseup pad] - please join us there! After the call is complete, the notes will be transfered back to this wiki page for long-term keeping.<br />
* MeetUp will take place '''day month date''' at time (timeA/P) Pacific Time.<br />
* The location is ADDRESS.<br />
* The event page can be found [https://aspirationtech.org/events/digitalresponsemeetup/city/year/month here].<br />
* If people need to register, indicate as such here.<br />
<br />
[[Category:MeetUp|Events|Nonprofit Tech Center]]</nowiki><br />
<br />
==Which looks like==<br />
===About this MONTH checkin===<br />
The agenda and notes for this call are taking shape on [http://pad.riseup.net/p/monthdigitalrespondermeetup this riseup pad] - please join us there! After the call is complete, the notes will be transfered back to this wiki page for long-term keeping.<br />
* MeetUp will take place '''day month date''' at time (timeA/P) Pacific Time.<br />
* The location is ADDRESS.<br />
* The event page can be found [https://aspirationtech.org/events/digitalresponsemeetup/city/year/month here].<br />
* If people need to register, indicate as such here.<br />
<br />
[[Category:MeetUp|Events|Nonprofit Tech Center]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=279Category:MeetUp2016-07-18T19:27:18Z<p>Willow: /* Pre-MeetUp */</p>
<hr />
<div> This page is a work in progress. Parts of it will be wrong and/or incomplete.<br />
Contributions, suggestions, etc always welcome!<br />
<br />
==Why host meetups for digital responders?==<br />
{{About Meetups}}<br />
<br />
==Scaffolding and resources for hosting a meetup with us or elsewhere==<br />
===Components===<br />
We've found the following to be essential to a group check-in:<br />
* '''Where''' will the meetup take place? : You'll need a physical location. If you're wanting to do a remote session (either with some or all participants), you might find benefit from the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call guide for checkin calls].<br />
* '''When''' will the meetup happen? : The date and time (include the timezone if you have travelers or remote participants!).<br />
* '''What''' will be talked about? : Talk with participants about what's on their minds.<br />
* '''Who''' are you inviting? : Invitee list (organizations and/or individuals).<br />
: We have a mailing list which is invited first, and can be registered for via the [[Main Page]]<br />
<br />
===For attendees===<br />
* '''Be prepared''' : Think about what you want out of the meetup. Are you looking for help on something? Want to give an update on a project? Looking to hear what others are up to? All of these (and more) are great!<br />
* '''Be present''' : Sharing of information requires a receiver. Don't just think about what you'd like to ''say'' to everyone, demonstrate respect by paying attention when others are speaking.<br />
* '''Contribute''' : The facilitator is likely juggling multiple things. The person speaking can rarely/not take notes for themselves as they speak. We rely on the group to document meaningful exchanges, and that means me/you/us documenting, asking questions, offering suggestions.<br />
<br />
===For organizers===<br />
Be clear (but not spammy) about letting people know about the event.<br />
====Pre-MeetUp====<br />
# Make an event page on your website.<br />
# Make a way for people to register.<br />
# Add a stubbed '''wiki page''' linked to from the [[Template:Meetup Summaries|list of events]]. Our [[MeetUp wiki page template]] may come in handy.<br />
# Invite folk to your event. We announce these meetups to<br />
## [https://lists.aspirationtech.org/lists/info/digitalresponse our digital response mailing list],<br />
## the Digital Humanitarian Network mailing list, and <br />
## the DHN skype channel.<br />
# '''2 or 3 days''' before the event, remind people about the meetup's time and location.<br />
<br />
====Post-MeetUp====<br />
Participants should know they have a set amount of time to add in edits and to make deletions before the notes go in a public-facing location.<br />
# '''1 or 2 days''' after the event, transfer the notes from a collaborative note-taking platform to the '''wiki page'''. ''The only thing left on the riseup pad should be a link to the wiki page''.<br />
# Send out a link to the wiki page, plus thanks and top-level analysis to the same channels the meetup was announced to. Ask if anyone is uncomfortable sharing their contact with other participants.<br />
# '''1 week after the meetup''', send out the participant list and invite everyone to the digital responder mailing list. ''Do not opt them in, let them do it (or not) themselves.''<br />
<br />
===For facilitators===<br />
* Work with participants on the agenda.<br />
* Try to start on time, which means you will need to be present to set up the space about a half hour early.<br />
* Try to end at least a few minutes early.<br />
* Remember the entirety of the group is who you serve, and be ok interrupting someone if they're taking up more than 1/Nth of the time.<br />
<br />
==Past call links and summaries==<br />
{{Meetup Summaries}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=278Category:MeetUp2016-07-18T19:17:31Z<p>Willow: /* Pre-MeetUp */</p>
<hr />
<div> This page is a work in progress. Parts of it will be wrong and/or incomplete.<br />
Contributions, suggestions, etc always welcome!<br />
<br />
==Why host meetups for digital responders?==<br />
{{About Meetups}}<br />
<br />
==Scaffolding and resources for hosting a meetup with us or elsewhere==<br />
===Components===<br />
We've found the following to be essential to a group check-in:<br />
* '''Where''' will the meetup take place? : You'll need a physical location. If you're wanting to do a remote session (either with some or all participants), you might find benefit from the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call guide for checkin calls].<br />
* '''When''' will the meetup happen? : The date and time (include the timezone if you have travelers or remote participants!).<br />
* '''What''' will be talked about? : Talk with participants about what's on their minds.<br />
* '''Who''' are you inviting? : Invitee list (organizations and/or individuals).<br />
: We have a mailing list which is invited first, and can be registered for via the [[Main Page]]<br />
<br />
===For attendees===<br />
* '''Be prepared''' : Think about what you want out of the meetup. Are you looking for help on something? Want to give an update on a project? Looking to hear what others are up to? All of these (and more) are great!<br />
* '''Be present''' : Sharing of information requires a receiver. Don't just think about what you'd like to ''say'' to everyone, demonstrate respect by paying attention when others are speaking.<br />
* '''Contribute''' : The facilitator is likely juggling multiple things. The person speaking can rarely/not take notes for themselves as they speak. We rely on the group to document meaningful exchanges, and that means me/you/us documenting, asking questions, offering suggestions.<br />
<br />
===For organizers===<br />
Be clear (but not spammy) about letting people know about the event.<br />
====Pre-MeetUp====<br />
# Make an event page on your website.<br />
# Make a way for people to register.<br />
# Add a stubbed '''wiki page''' linked to from the [[Template:Meetup Summaries|list of events]]. The [[Check in call agenda template]] is useful for this.<br />
# Invite folk to your event. We announce these meetups to<br />
## [https://lists.aspirationtech.org/lists/info/digitalresponse our digital response mailing list],<br />
## the Digital Humanitarian Network mailing list, and <br />
## the DHN skype channel.<br />
# '''2 or 3 days''' before the event, remind people about the meetup's time and location.<br />
<br />
====Post-MeetUp====<br />
Participants should know they have a set amount of time to add in edits and to make deletions before the notes go in a public-facing location.<br />
# '''1 or 2 days''' after the event, transfer the notes from a collaborative note-taking platform to the '''wiki page'''. ''The only thing left on the riseup pad should be a link to the wiki page''.<br />
# Send out a link to the wiki page, plus thanks and top-level analysis to the same channels the meetup was announced to. Ask if anyone is uncomfortable sharing their contact with other participants.<br />
# '''1 week after the meetup''', send out the participant list and invite everyone to the digital responder mailing list. ''Do not opt them in, let them do it (or not) themselves.''<br />
<br />
===For facilitators===<br />
* Work with participants on the agenda.<br />
* Try to start on time, which means you will need to be present to set up the space about a half hour early.<br />
* Try to end at least a few minutes early.<br />
* Remember the entirety of the group is who you serve, and be ok interrupting someone if they're taking up more than 1/Nth of the time.<br />
<br />
==Past call links and summaries==<br />
{{Meetup Summaries}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=277Category:MeetUp2016-07-18T19:16:30Z<p>Willow: /* Scaffolding and resources for hosting a call with us or elsewhere */</p>
<hr />
<div> This page is a work in progress. Parts of it will be wrong and/or incomplete.<br />
Contributions, suggestions, etc always welcome!<br />
<br />
==Why host meetups for digital responders?==<br />
{{About Meetups}}<br />
<br />
==Scaffolding and resources for hosting a meetup with us or elsewhere==<br />
===Components===<br />
We've found the following to be essential to a group check-in:<br />
* '''Where''' will the meetup take place? : You'll need a physical location. If you're wanting to do a remote session (either with some or all participants), you might find benefit from the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call guide for checkin calls].<br />
* '''When''' will the meetup happen? : The date and time (include the timezone if you have travelers or remote participants!).<br />
* '''What''' will be talked about? : Talk with participants about what's on their minds.<br />
* '''Who''' are you inviting? : Invitee list (organizations and/or individuals).<br />
: We have a mailing list which is invited first, and can be registered for via the [[Main Page]]<br />
<br />
===For attendees===<br />
* '''Be prepared''' : Think about what you want out of the meetup. Are you looking for help on something? Want to give an update on a project? Looking to hear what others are up to? All of these (and more) are great!<br />
* '''Be present''' : Sharing of information requires a receiver. Don't just think about what you'd like to ''say'' to everyone, demonstrate respect by paying attention when others are speaking.<br />
* '''Contribute''' : The facilitator is likely juggling multiple things. The person speaking can rarely/not take notes for themselves as they speak. We rely on the group to document meaningful exchanges, and that means me/you/us documenting, asking questions, offering suggestions.<br />
<br />
===For organizers===<br />
Be clear (but not spammy) about letting people know about the event.<br />
====Pre-MeetUp====<br />
# Make an event page on your website.<br />
# Make a way for people to register.<br />
# Add a stubbed '''wiki page''' linked to from the [[Template:Meetup Summaries|list of events]].<br />
# Invite folk to your event. We announce these meetups to<br />
## [https://lists.aspirationtech.org/lists/info/digitalresponse our digital response mailing list],<br />
## the Digital Humanitarian Network mailing list, and <br />
## the DHN skype channel.<br />
# '''2 or 3 days''' before the event, remind people about the meetup's time and location.<br />
====Post-MeetUp====<br />
Participants should know they have a set amount of time to add in edits and to make deletions before the notes go in a public-facing location.<br />
# '''1 or 2 days''' after the event, transfer the notes from a collaborative note-taking platform to the '''wiki page'''. ''The only thing left on the riseup pad should be a link to the wiki page''.<br />
# Send out a link to the wiki page, plus thanks and top-level analysis to the same channels the meetup was announced to. Ask if anyone is uncomfortable sharing their contact with other participants.<br />
# '''1 week after the meetup''', send out the participant list and invite everyone to the digital responder mailing list. ''Do not opt them in, let them do it (or not) themselves.''<br />
<br />
===For facilitators===<br />
* Work with participants on the agenda.<br />
* Try to start on time, which means you will need to be present to set up the space about a half hour early.<br />
* Try to end at least a few minutes early.<br />
* Remember the entirety of the group is who you serve, and be ok interrupting someone if they're taking up more than 1/Nth of the time.<br />
<br />
==Past call links and summaries==<br />
{{Meetup Summaries}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=276Category:MeetUp2016-07-18T19:16:07Z<p>Willow: </p>
<hr />
<div> This page is a work in progress. Parts of it will be wrong and/or incomplete.<br />
Contributions, suggestions, etc always welcome!<br />
<br />
==Why host meetups for digital responders?==<br />
{{About Meetups}}<br />
<br />
==Scaffolding and resources for hosting a call with us or elsewhere==<br />
===Components===<br />
We've found the following to be essential to a group check-in:<br />
* '''Where''' will the meetup take place? : You'll need a physical location. If you're wanting to do a remote session (either with some or all participants), you might find benefit from the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call guide for checkin calls].<br />
* '''When''' will the meetup happen? : The date and time (include the timezone if you have travelers or remote participants!).<br />
* '''What''' will be talked about? : Talk with participants about what's on their minds.<br />
* '''Who''' are you inviting? : Invitee list (organizations and/or individuals).<br />
: We have a mailing list which is invited first, and can be registered for via the [[Main Page]]<br />
<br />
===For attendees===<br />
* '''Be prepared''' : Think about what you want out of the meetup. Are you looking for help on something? Want to give an update on a project? Looking to hear what others are up to? All of these (and more) are great!<br />
* '''Be present''' : Sharing of information requires a receiver. Don't just think about what you'd like to ''say'' to everyone, demonstrate respect by paying attention when others are speaking.<br />
* '''Contribute''' : The facilitator is likely juggling multiple things. The person speaking can rarely/not take notes for themselves as they speak. We rely on the group to document meaningful exchanges, and that means me/you/us documenting, asking questions, offering suggestions.<br />
<br />
===For organizers===<br />
Be clear (but not spammy) about letting people know about the event.<br />
====Pre-MeetUp====<br />
# Make an event page on your website.<br />
# Make a way for people to register.<br />
# Add a stubbed '''wiki page''' linked to from the [[Template:Meetup Summaries|list of events]].<br />
# Invite folk to your event. We announce these meetups to<br />
## [https://lists.aspirationtech.org/lists/info/digitalresponse our digital response mailing list],<br />
## the Digital Humanitarian Network mailing list, and <br />
## the DHN skype channel.<br />
# '''2 or 3 days''' before the event, remind people about the meetup's time and location.<br />
====Post-MeetUp====<br />
Participants should know they have a set amount of time to add in edits and to make deletions before the notes go in a public-facing location.<br />
# '''1 or 2 days''' after the event, transfer the notes from a collaborative note-taking platform to the '''wiki page'''. ''The only thing left on the riseup pad should be a link to the wiki page''.<br />
# Send out a link to the wiki page, plus thanks and top-level analysis to the same channels the meetup was announced to. Ask if anyone is uncomfortable sharing their contact with other participants.<br />
# '''1 week after the meetup''', send out the participant list and invite everyone to the digital responder mailing list. ''Do not opt them in, let them do it (or not) themselves.''<br />
<br />
===For facilitators===<br />
* Work with participants on the agenda.<br />
* Try to start on time, which means you will need to be present to set up the space about a half hour early.<br />
* Try to end at least a few minutes early.<br />
* Remember the entirety of the group is who you serve, and be ok interrupting someone if they're taking up more than 1/Nth of the time.<br />
<br />
==Past call links and summaries==<br />
{{Meetup Summaries}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=275Category:MeetUp2016-07-18T19:00:41Z<p>Willow: </p>
<hr />
<div>{{About Meetups}}<br />
<br />
{{Meetup Summaries}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Template:Meetup_Summaries&diff=274Template:Meetup Summaries2016-07-18T19:00:31Z<p>Willow: </p>
<hr />
<div>* [[2016 August Meet Up]] : August 11th in San Francisco, CA. We'll chat about what we work on and how we discern which projects and deployments are within scope and ethics for our groups and selves.<br />
* [[2016 June Meet Up]] : June 16th in San Francisco, CA. We reviewed MapSwipe, how cross-sector communication works, the ecosystem map, and basic ways of plugging into digital response activities.<br />
<br />
[[Category:MeetUp]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Template:Meetup_Summaries&diff=273Template:Meetup Summaries2016-07-18T19:00:04Z<p>Willow: Created page with "* 2016 August Meet Up : August 11th in San Francisco, CA. We'll chat about what we work on and how we discern which projects and deployments are within scope and ethics fo..."</p>
<hr />
<div>* [[2016 August Meet Up]] : August 11th in San Francisco, CA. We'll chat about what we work on and how we discern which projects and deployments are within scope and ethics for our groups and selves.<br />
* [[2016 June Meet Up]] : June 16th in San Francisco, CA. We reviewed MapSwipe, how cross-sector communication works, the ecosystem map, and basic ways of plugging into digital response activities.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Main_Page&diff=272Main Page2016-07-18T18:58:42Z<p>Willow: /* Digital Responder Meetups */</p>
<hr />
<div>{{About Digital Response}}<br />
<br />
==Join the Conversation==<br />
===Mailing List===<br />
Our '''[https://lists.aspirationtech.org/lists/info/digitalresponse mailing list]''' includes updates about digital responder call-ins, upcoming events, and cross-sector collaborative discussion.<br />
<br />
===Check In Calls===<br />
{{Why Call Ins?}}<br />
<br />
There is a template for how to conduct a digital responder checkin call on the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call checkin call category page]. That page will also give a process for adding your own calls to this wiki.<br />
<br />
{{Checkin Call Summaries}}<br />
<br />
===Direct Contact===<br />
Have a question about this program, but don't necessarily want to talk to a whole group? No worries! Reach out to [mailto:digitalresponse@aspirationtech.org digitalresponse@aspirationtech.org] to be in touch with us directly.<br />
<br />
==[https://digitalresponse.aspirationtech.org/index.php?title=Category:Events Events]==<br />
===Humanitarian Technology Festival===<br />
{{About HumTechFest}}<br />
* [[2016 June HumTechFest]] : June 4th and 5th in Cambridge, Mass. We played a scenario, talked a lot about institutional and grassroots collaboration, and worked on the [[Digital response ecosystem map]].<br />
* [[2015 May MIT|2015 May HumTechFest]] : our first HumTechFest! We talked about how frontline communities could hold responders accountable, did skill shares around open data, and spec'd out easy-to-create after action report templates.<br />
<br />
===Digital Responder Meetups===<br />
{{About Meetups}}<br />
<br />
{{Meetup Summaries}}<br />
<br />
==Projects==<br />
{{About Projects}}<br />
* [[Digital response ecosystem map]] : some official organizations have name-brand recognition, there is little understanding of the local, emerging, and digital sectors. Additionally, the flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem. <br />
* [[Frontline communities holding responders accountable]] : response organizations and individual responders are vital contributors to safety, rebuilding, logistics, etc in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so? This project suggests a transparency report for how the needs of an affected population were (or were not) addressed by those claiming to do so.<br />
* [[Bookmarklet to log projects]] : many do-good projects exist across many organizations, spaces, and events. Some were created at hackathons, some have nothing to do with response (but could be useful in crises), and there is no repository of these projects for those building or needing tools. How can we log them in a decentralized way?<br />
* [[Media guide for extreme events]] : crises are often accompanied by a media frenzy, and those already stressed because of the impact on their lives are also expected to be spokespeople for their neighborhood. If you're a reporter, how can you act in good faith in an affected region? If you're a member of the affected population, what are ways to approach media inquiries from a social justice perspective?<br />
* [[Extreme event preparedness and response for small nonprofits]] : guide for small non profits and other community groups to prepare for, and respond to, crisis.<br />
* [[Communication tools matrix]] : every extreme event is different, but all involve coordinating across many different organizations, timezones, politics, etc. We're working to understand the potential needs of each response, and to map existing communication tools to those needs for speedy selection and setup.<br />
* [[Before you jump in: Missing Persons]] : a guide in how (and when) to build or contribute to a missing persons application.<br />
<br />
==Response Groups and Projects Aspiration Works With==<br />
* [http://climatecentre.org Red Cross Red Crescent Climate Centre] : on [https://aspirationtech.org/blog/willow/nairobi_spring2015 games about citizen reporting], on crowd integration.<br />
* [https://aspirationtech.org/blog/willow/nairobi_spring2015 Dialling Up Resilience] : on accountability mechanisms and local indicators of resilience.<br />
* [http://www.hirondellenews.com/ Hirondelle] : on visually representing their communications network.<br />
<br />
==Words on the Subject==<br />
===The topic on our blog===<br />
Follow and comment on [https://aspirationtech.org/taxonomy/term/72 topical blog entries].<br />
<br />
===Recommended Reading===<br />
* [http://www.democracynow.org/2009/8/31/a_paradise_built_in_hell_rebecca A Paradise Built in Hell] : an easy-to-ready overview of disaster sociology, how people behave in crisis (spoiler: it's not every person for themselves).<br />
* [https://archive.org/details/BlackFlagsAndWindmills Black Flags and Windmills] : review of the politicized relief efforts for Hurricane Katrina performed by the Common Ground Collective.<br />
* [http://cdacollaborative.org/publication/do-no-harm-how-aid-can-support-peace-or-war/ Do No Harm] : review and framework for how to deploy resources into conflict zones without exacerbating the conflict.<br />
The GovLab also has a [http://thegovlab.org/data-and-humanitarian-response/ list of selected readings] worth checking out.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=271Category:MeetUp2016-07-05T19:49:23Z<p>Willow: </p>
<hr />
<div>{{About Meetups}}</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp&diff=270Category:MeetUp2016-07-05T19:48:50Z<p>Willow: Created page with "{{About Meetups]]"</p>
<hr />
<div>{{About Meetups]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Template:About_Meetups&diff=269Template:About Meetups2016-07-05T19:48:25Z<p>Willow: </p>
<hr />
<div>Many digital responders often work alone. And just as independent consultants migrate to coffee shops and coworking spaces to seek out human company, so too do those of us in the humanitarian and disaster response sector. Whether working on the code for tracking infrastructure, struggling with how to tell a story about refugees using mobile technology, thinking about how to invest in a project without disrupting local economies, or wanting feedback on the latest design of your incident-reporting dashboard, we want you to be with friends and cohorts. Many digital humanitarian and disaster responders are the only person in an organization working on this topic, OR you're on a dedicated but distributed team, OR you're just coming to the topic and wanting to put faces with all those online usernames. So it's just nice to hang out, get to know each other, our projects, and brainstorm about challenges.<br />
<br />
We also rely on the networks we already know when a crisis occurs. By establishing bonds of trust, knowledge, and having explored and bettered our own projects and understandings, we'll be able to more effectively respond to the next extreme event. We'll know where we can meet up for physical solidarity, a solid internet connection, and people we know and have worked with before. All those background technical links that allow data and knowledge to be shared for a more holistic response are more likely to happen when we're all in the same space as each other.<br />
<br />
So please bring your questions, your projects, your challenges. We'll provide the soda, beer, and snacks. We are tool- and sector-agnostic, so long as you are dedicated to listening, sharing, and empowerment.<br />
<br />
Want to host one of your own? [https://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp Here's how]! All we ask is that you let us know you are, so we might support you.<br />
<br />
Find yourself in the Bay Area when one isn't happening, or simply don't want to wait until the next one? We welcome digital responders (and others) to come cowork from the Nonprofit Technology Center at 16th and Mission in San Francisco any time. Just give us a heads up.<br />
<br />
[[Category:MeetUp]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Template:About_Meetups&diff=268Template:About Meetups2016-07-05T19:47:45Z<p>Willow: Created page with "Many digital responders often work alone. And just as independent consultants migrate to coffee shops and coworking spaces to seek out human company, so too do those of us in..."</p>
<hr />
<div>Many digital responders often work alone. And just as independent consultants migrate to coffee shops and coworking spaces to seek out human company, so too do those of us in the humanitarian and disaster response sector. Whether working on the code for tracking infrastructure, struggling with how to tell a story about refugees using mobile technology, thinking about how to invest in a project without disrupting local economies, or wanting feedback on the latest design of your incident-reporting dashboard, we want you to be with friends and cohorts. Many digital humanitarian and disaster responders are the only person in an organization working on this topic, OR you're on a dedicated but distributed team, OR you're just coming to the topic and wanting to put faces with all those online usernames. So it's just nice to hang out, get to know each other, our projects, and brainstorm about challenges.<br />
<br />
We also rely on the networks we already know when a crisis occurs. By establishing bonds of trust, knowledge, and having explored and bettered our own projects and understandings, we'll be able to more effectively respond to the next extreme event. We'll know where we can meet up for physical solidarity, a solid internet connection, and people we know and have worked with before. All those background technical links that allow data and knowledge to be shared for a more holistic response are more likely to happen when we're all in the same space as each other.<br />
<br />
So please bring your questions, your projects, your challenges. We'll provide the soda, beer, and snacks. We are tool- and sector-agnostic, so long as you are dedicated to listening, sharing, and empowerment.<br />
<br />
Want to host one of your own? [https://digitalresponse.aspirationtech.org/index.php?title=Category:MeetUp Here's how]! All we ask is that you let us know you are, so we might support you.<br />
<br />
Find yourself in the Bay Area when one isn't happening, or simply don't want to wait until the next one? We welcome digital responders (and others) to come cowork from the Nonprofit Technology Center at 16th and Mission in San Francisco any time. Just give us a heads up.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=2016_June_Meet_Up&diff=2672016 June Meet Up2016-07-05T19:47:14Z<p>Willow: </p>
<hr />
<div>{{About Meetups}}<br />
<br />
8 folk gathered on<br />
: Thursday June 16 from 18:00-21:00<br />
at the<br />
: [http://sftechcenter.org/ San Francisco Nonprofit Tech Center]<br />
:: 2973 16th Street Suite 300<br />
:: San Francisco, CA 94103<br />
for an informal meetup for digital responders.<br />
<br />
==[http://facilitation.aspirationtech.org/index.php?title=Agenda:Hacking Universe of Topics]==<br />
We first did a quick overview of what questions and thoughts participants had.<br />
===Tools===<br />
* What tools do you use?<br />
* HOT OSM - geo stuff it misses, takes too long.<br />
<br />
===Coordination===<br />
* What organizations require humanitarian response?<br />
* How to interface more with local organizations rather than international agencies<br />
* What actions are taken by parties involved in humanitarian response?<br />
<br />
===Active response===<br />
* What is humanitarian response?<br />
* Handling variability of RSVPs to the people who show up to help<br />
* How do people communicate cross-sector?<br />
* Bridging formal and informal groups?<br />
<br />
===Between===<br />
* How can I help?<br />
* Post-disaster ad-hoc networking<br />
* Mapswipe microtasking, unskilled labor<br />
<br />
===Projects===<br />
* Tech-enabled prosthetic environments<br />
<br />
===Groups===<br />
* Who should we be talking to in the Bay Area?<br />
* Ecosystem mapping -- what's going on out there?<br />
* Who do you work with (affected people, partners, etc)?<br />
<br />
===Orphans===<br />
* What do you do? (Aspiration, humanitarian response)<br />
* Camp Roberts<br />
<br />
==Discussion Topics==<br />
We then did quick sticker-voting to discover where the most interest was, and gave roughly 20 minutes per discussion topic. Many flowed into each other.<br />
===MapSwipe===<br />
[https://www.openstreetmap.org/about OpenStreetMap] is "built by a community of mappers that contribute and maintain data about roads, trails, cafés, railway stations, and much more, all over the world." The logistics for response to crises (both fast and slow) are often based on incomplete maps (out of date or [http://www.missingmaps.org/ never mapped to begin with]). One way digital volunteers can contribute to the response is by identifying villages and other infrastructure on satellite imagery. This is often done at a map-a-thon. When MSF and OSM-er [https://twitter.com/ivangayton Ivan Gayton] went to a map-a-thon, he saw that much of the time was spent on classifying squares (farmland, inhabited, wilderness) rather than identifying infrastructure (houses, roads, crops). This seemed like a waste of time. Alison joined us at the meetup to tell us about a technical intervention for this, called '''MapSwipe''', to do some user testing.<br />
<br />
She's looking to find the fastest and easiest way to do the interaction. Also wanted to talk about what project we could foresee using this for, or what sorts of imagery to include (such as from planes or drones).<br />
<br />
MapSwipe users swipe one way on their smart phone screen for a map tile which includes infrastructure, and an opposite direction for those which don't include infrastructure. Users are also encouraged to tap in areas which seem to have infrastructure of some kind. The data is taken in aggregate (and cross referenced with other digital volunteers) to prioritize which map tiles more skilled volunteers should focus on sketching on.<br />
<br />
Other tidbits from our conversation about purpose and usability:<br />
* Can cache images when you don't have access. <br />
* Portable [https://mapmill.org/ MapMill]. <br />
* Imagery is donated by Bing. <br />
* Can also load your own projects in.<br />
* Reward systems for feedback in cute messages as you go.<br />
* There's a slack that some folk contributing and interested are in! Alison will also send us updates later.<br />
<br />
===Ecosystem Mapping===<br />
We took some time to review the [[Digital response ecosystem map]] and to get input from participants about entities, tools, data, etc. The information has been folded into the overview file.<br />
<br />
===How can I help?===<br />
We had a discussion about how newcomers to the space could engage. As about half of the participants were new to the space, it provided a great opportunity to understand questions (and what was already understood).<br />
<br />
'''Questions'''<br />
* I've worked with a ton of tools but not in this space. I use for my job or open source projects but not for this particular type of thing. But using the tool appropriately is a big question for me. What skills are usually useful or needed? <br />
: Haven't had trouble finding groups. <br />
* Asked to help at a Humanitarian OpenStreetMap Team (HOT) event because I do a lot with OSM. Was considered one of the experts there, but I was hesitant because the landscapes etc are so different from your own. You can feel like you're going to ruin some aid worker by sending them to a mound rather than a hut. Just having very little confidence despite having the background technical knowledge.<br />
* Question about any volunteer effort is "is what I'm doing having any impact at all?"<br />
<br />
'''Discussion'''<br />
* Dealing with self doubt<br />
: Even if your project impacted the overall response, how do ''you'' know? "327 people liked your road"<br />
* Accountability. What organizations are we working for? <br />
: Rating of stars for nonprofits for donations, what about the nonoffical nonprofits? How do you get a sense for an alignment for what you're trying to do?<br />
: Rate for use of your funds, rate on use of data. There's an EFF project tracking EULAs, could we model off of that?<br />
* Talked about Response Badges, context guides, and accountability<br />
: Have a background reader on infrastructure on Nepal or something, so people getting involved could learn at a deeper level. It can be hard to just click on stuff and have no context. Take the fact books and convert them into responder friendly formats. Lots of shapes for mapping, the forms of buildings and roads that are specific to certain places. Also what look like buildings but aren't. A '''primer''' on that could be useful, feel better when tagging things.<br />
: NGOs operating on the ground likely have these fact books for regions. An adaptation for region-specific digital responses could be interesting.<br />
: related project on this wiki: [[Frontline communities holding responders accountable]]<br />
* Coming in to help when you don't any context is intimidating.<br />
: A lot of that stuff might exist outside of this context. Design or architecture or urban planning, the beginning of the studio has a design project somewhere where no one has personal context. that's to get people out of their own local. But there's a primer on urban strategy which could be adapted to something like this. But that's well hiding. <br />
<br />
===Cross-sector communication===<br />
It's people, not necessarily institutional support. But the institutions had to make space for it.<br />
<br />
Example: Google Crisis Response would try something out and assess whether or not it worked. One thing was taking maps from a bunch of different places and then combining them. National Weather Service overlayed with imagery that only google had, with something crowdsourced like Ushahidi. Large, formal datasets with fast changing datasets in the hopes that would help people synthesize the data to make better needs assessments. Audience for the map was: agencies, less formal organizations and responders. We would build all these maps and pull together information, but then weren't closing the loop (on resolving discrepancies and also letting people know if the data was useful or not). Gov is working behind really strict firewalls so we can't reach out. But we can get ONE site cleared through the firewall, so a coordinating one like Google Maps is way easier.<br />
<br />
Gov thinking about how to support groups talking to each other. Markup languages etc that are more interchangeable. HXL is one example.<br />
<br />
Google Crisis Map, while a site hosted at google.. the code is 100% open source. You could use it yourself. not just Google APIs, also OSM. Can point at any tile source. The project doesn't contain any data, it just links and displays the data.<br />
<br />
Do you get data that smaller groups wouldn't? I don't think we ever used anything restricted. Ask them to make it available publicly.<br />
<br />
First time I saw the Sandy Crisis Map was at a rebuild by design. Big government grant which was a design competition for hurricane projects around NYC. A sea wall around Manhattan, a marsh. One linked back to that map.<br />
<br />
===Prosthetic Environments===<br />
Side of self care. Especially in crisis you are already altruistic to a point you'll run yourself ragged. You're not around the people who take care with you, tell you to sleep.<br />
<br />
Clinical psychology about prosthetic environments. How a long term care giver establishes such a close relationship with that person that they do radical translation and joint embodiment.<br />
<br />
Those who are remotely deployed are not taking care with themselves. Concept of an ecosystem where these devices can plug into each other. Catching companies at their first big hurdle helps out.<br />
<br />
People who feel compelled to stay online and fix right now. A thing taht is useful about this is the only way you usually have to reach out is chat. Social expectations make it hard to ask. Expect to respond and engage in conversation. Interact with a different method.<br />
<br />
Thank goodness for emojis.<br />
<br />
Lots of teardown online. Electrical devices, super easy to reverse engineer. <br />
<br />
==Closing thoughts==<br />
* Alison - Still new to humanitarian crisis response. The whole wormhole. Seems intimidating but pressing on it shows it's super warm. <br />
* Logan - List of open source projects, tasks I can start on. I have tech skills.<br />
* Matt would like to know more about how to get people involved. Let them know they can get involved whether they have technical skills or not. Making it accessible. Don't bog someone down with humdrum work when they can be coding etc. A progression ladder, skill-specific tasking.<br />
* Scotty - appreciative of people coming in. I'm so jaded.<br />
* Nemesis - exciting, excited to know this exists and that you exist<br />
* Nikki - similar sentiments, would do again<br />
* Ping - this was fun, didn't know what to expect, some serendipitous things happened.<br />
* Willow - was taking notes.<br />
<br />
[[Category: Events]] [[Category: Nonprofit Tech Center]][[Category:MeetUp]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=2016_June_Meet_Up&diff=2662016 June Meet Up2016-07-05T19:45:16Z<p>Willow: </p>
<hr />
<div>{{About Meetups}}<br />
<br />
8 folk gathered on<br />
: Thursday June 16 from 18:00-21:00<br />
at the<br />
: [http://sftechcenter.org/ San Francisco Nonprofit Tech Center]<br />
:: 2973 16th Street Suite 300<br />
:: San Francisco, CA 94103<br />
for an informal meetup for digital responders.<br />
<br />
==[http://facilitation.aspirationtech.org/index.php?title=Agenda:Hacking Universe of Topics]==<br />
We first did a quick overview of what questions and thoughts participants had.<br />
===Tools===<br />
* What tools do you use?<br />
* HOT OSM - geo stuff it misses, takes too long.<br />
<br />
===Coordination===<br />
* What organizations require humanitarian response?<br />
* How to interface more with local organizations rather than international agencies<br />
* What actions are taken by parties involved in humanitarian response?<br />
<br />
===Active response===<br />
* What is humanitarian response?<br />
* Handling variability of RSVPs to the people who show up to help<br />
* How do people communicate cross-sector?<br />
* Bridging formal and informal groups?<br />
<br />
===Between===<br />
* How can I help?<br />
* Post-disaster ad-hoc networking<br />
* Mapswipe microtasking, unskilled labor<br />
<br />
===Projects===<br />
* Tech-enabled prosthetic environments<br />
<br />
===Groups===<br />
* Who should we be talking to in the Bay Area?<br />
* Ecosystem mapping -- what's going on out there?<br />
* Who do you work with (affected people, partners, etc)?<br />
<br />
===Orphans===<br />
* What do you do? (Aspiration, humanitarian response)<br />
* Camp Roberts<br />
<br />
==Discussion Topics==<br />
We then did quick sticker-voting to discover where the most interest was, and gave roughly 20 minutes per discussion topic. Many flowed into each other.<br />
===MapSwipe===<br />
[https://www.openstreetmap.org/about OpenStreetMap] is "built by a community of mappers that contribute and maintain data about roads, trails, cafés, railway stations, and much more, all over the world." The logistics for response to crises (both fast and slow) are often based on incomplete maps (out of date or [http://www.missingmaps.org/ never mapped to begin with]). One way digital volunteers can contribute to the response is by identifying villages and other infrastructure on satellite imagery. This is often done at a map-a-thon. When MSF and OSM-er [https://twitter.com/ivangayton Ivan Gayton] went to a map-a-thon, he saw that much of the time was spent on classifying squares (farmland, inhabited, wilderness) rather than identifying infrastructure (houses, roads, crops). This seemed like a waste of time. Alison joined us at the meetup to tell us about a technical intervention for this, called '''MapSwipe''', to do some user testing.<br />
<br />
She's looking to find the fastest and easiest way to do the interaction. Also wanted to talk about what project we could foresee using this for, or what sorts of imagery to include (such as from planes or drones).<br />
<br />
MapSwipe users swipe one way on their smart phone screen for a map tile which includes infrastructure, and an opposite direction for those which don't include infrastructure. Users are also encouraged to tap in areas which seem to have infrastructure of some kind. The data is taken in aggregate (and cross referenced with other digital volunteers) to prioritize which map tiles more skilled volunteers should focus on sketching on.<br />
<br />
Other tidbits from our conversation about purpose and usability:<br />
* Can cache images when you don't have access. <br />
* Portable [https://mapmill.org/ MapMill]. <br />
* Imagery is donated by Bing. <br />
* Can also load your own projects in.<br />
* Reward systems for feedback in cute messages as you go.<br />
* There's a slack that some folk contributing and interested are in! Alison will also send us updates later.<br />
<br />
===Ecosystem Mapping===<br />
We took some time to review the [[Digital response ecosystem map]] and to get input from participants about entities, tools, data, etc. The information has been folded into the overview file.<br />
<br />
===How can I help?===<br />
We had a discussion about how newcomers to the space could engage. As about half of the participants were new to the space, it provided a great opportunity to understand questions (and what was already understood).<br />
<br />
'''Questions'''<br />
* I've worked with a ton of tools but not in this space. I use for my job or open source projects but not for this particular type of thing. But using the tool appropriately is a big question for me. What skills are usually useful or needed? <br />
: Haven't had trouble finding groups. <br />
* Asked to help at a Humanitarian OpenStreetMap Team (HOT) event because I do a lot with OSM. Was considered one of the experts there, but I was hesitant because the landscapes etc are so different from your own. You can feel like you're going to ruin some aid worker by sending them to a mound rather than a hut. Just having very little confidence despite having the background technical knowledge.<br />
* Question about any volunteer effort is "is what I'm doing having any impact at all?"<br />
<br />
'''Discussion'''<br />
* Dealing with self doubt<br />
: Even if your project impacted the overall response, how do ''you'' know? "327 people liked your road"<br />
* Accountability. What organizations are we working for? <br />
: Rating of stars for nonprofits for donations, what about the nonoffical nonprofits? How do you get a sense for an alignment for what you're trying to do?<br />
: Rate for use of your funds, rate on use of data. There's an EFF project tracking EULAs, could we model off of that?<br />
* Talked about Response Badges, context guides, and accountability<br />
: Have a background reader on infrastructure on Nepal or something, so people getting involved could learn at a deeper level. It can be hard to just click on stuff and have no context. Take the fact books and convert them into responder friendly formats. Lots of shapes for mapping, the forms of buildings and roads that are specific to certain places. Also what look like buildings but aren't. A '''primer''' on that could be useful, feel better when tagging things.<br />
: NGOs operating on the ground likely have these fact books for regions. An adaptation for region-specific digital responses could be interesting.<br />
: related project on this wiki: [[Frontline communities holding responders accountable]]<br />
* Coming in to help when you don't any context is intimidating.<br />
: A lot of that stuff might exist outside of this context. Design or architecture or urban planning, the beginning of the studio has a design project somewhere where no one has personal context. that's to get people out of their own local. But there's a primer on urban strategy which could be adapted to something like this. But that's well hiding. <br />
<br />
===Cross-sector communication===<br />
It's people, not necessarily institutional support. But the institutions had to make space for it.<br />
<br />
Example: Google Crisis Response would try something out and assess whether or not it worked. One thing was taking maps from a bunch of different places and then combining them. National Weather Service overlayed with imagery that only google had, with something crowdsourced like Ushahidi. Large, formal datasets with fast changing datasets in the hopes that would help people synthesize the data to make better needs assessments. Audience for the map was: agencies, less formal organizations and responders. We would build all these maps and pull together information, but then weren't closing the loop (on resolving discrepancies and also letting people know if the data was useful or not). Gov is working behind really strict firewalls so we can't reach out. But we can get ONE site cleared through the firewall, so a coordinating one like Google Maps is way easier.<br />
<br />
Gov thinking about how to support groups talking to each other. Markup languages etc that are more interchangeable. HXL is one example.<br />
<br />
Google Crisis Map, while a site hosted at google.. the code is 100% open source. You could use it yourself. not just Google APIs, also OSM. Can point at any tile source. The project doesn't contain any data, it just links and displays the data.<br />
<br />
Do you get data that smaller groups wouldn't? I don't think we ever used anything restricted. Ask them to make it available publicly.<br />
<br />
First time I saw the Sandy Crisis Map was at a rebuild by design. Big government grant which was a design competition for hurricane projects around NYC. A sea wall around Manhattan, a marsh. One linked back to that map.<br />
<br />
===Prosthetic Environments===<br />
Side of self care. Especially in crisis you are already altruistic to a point you'll run yourself ragged. You're not around the people who take care with you, tell you to sleep.<br />
<br />
Clinical psychology about prosthetic environments. How a long term care giver establishes such a close relationship with that person that they do radical translation and joint embodiment.<br />
<br />
Those who are remotely deployed are not taking care with themselves. Concept of an ecosystem where these devices can plug into each other. Catching companies at their first big hurdle helps out.<br />
<br />
People who feel compelled to stay online and fix right now. A thing taht is useful about this is the only way you usually have to reach out is chat. Social expectations make it hard to ask. Expect to respond and engage in conversation. Interact with a different method.<br />
<br />
Thank goodness for emojis.<br />
<br />
Lots of teardown online. Electrical devices, super easy to reverse engineer. <br />
<br />
==Closing thoughts==<br />
* Alison - Still new to humanitarian crisis response. The whole wormhole. Seems intimidating but pressing on it shows it's super warm. <br />
* Logan - List of open source projects, tasks I can start on. I have tech skills.<br />
* Matt would like to know more about how to get people involved. Let them know they can get involved whether they have technical skills or not. Making it accessible. Don't bog someone down with humdrum work when they can be coding etc. A progression ladder, skill-specific tasking.<br />
* Scotty - appreciative of people coming in. I'm so jaded.<br />
* Nemesis - exciting, excited to know this exists and that you exist<br />
* Nikki - similar sentiments, would do again<br />
* Ping - this was fun, didn't know what to expect, some serendipitous things happened.<br />
* Willow - was taking notes.<br />
<br />
[[Category: Events]] [[Category: Nonprofit Tech Center]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Main_Page&diff=265Main Page2016-07-05T19:44:39Z<p>Willow: /* Events */</p>
<hr />
<div>{{About Digital Response}}<br />
<br />
==Join the Conversation==<br />
===Mailing List===<br />
Our '''[https://lists.aspirationtech.org/lists/info/digitalresponse mailing list]''' includes updates about digital responder call-ins, upcoming events, and cross-sector collaborative discussion.<br />
<br />
===Check In Calls===<br />
{{Why Call Ins?}}<br />
<br />
There is a template for how to conduct a digital responder checkin call on the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call checkin call category page]. That page will also give a process for adding your own calls to this wiki.<br />
<br />
{{Checkin Call Summaries}}<br />
<br />
===Direct Contact===<br />
Have a question about this program, but don't necessarily want to talk to a whole group? No worries! Reach out to [mailto:digitalresponse@aspirationtech.org digitalresponse@aspirationtech.org] to be in touch with us directly.<br />
<br />
==[https://digitalresponse.aspirationtech.org/index.php?title=Category:Events Events]==<br />
===Humanitarian Technology Festival===<br />
{{About HumTechFest}}<br />
* [[2016 June HumTechFest]] : June 4th and 5th in Cambridge, Mass. We played a scenario, talked a lot about institutional and grassroots collaboration, and worked on the [[Digital response ecosystem map]].<br />
* [[2015 May MIT|2015 May HumTechFest]] : our first HumTechFest! We talked about how frontline communities could hold responders accountable, did skill shares around open data, and spec'd out easy-to-create after action report templates.<br />
<br />
===Digital Responder Meetups===<br />
{{About Meetups}}<br />
* [[2016 June Meet Up]] : June 16th in San Francisco, CA. We reviewed MapSwipe, how cross-sector communication works, the ecosystem map, and basic ways of plugging into digital response activities.<br />
<br />
==Projects==<br />
{{About Projects}}<br />
* [[Digital response ecosystem map]] : some official organizations have name-brand recognition, there is little understanding of the local, emerging, and digital sectors. Additionally, the flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem. <br />
* [[Frontline communities holding responders accountable]] : response organizations and individual responders are vital contributors to safety, rebuilding, logistics, etc in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so? This project suggests a transparency report for how the needs of an affected population were (or were not) addressed by those claiming to do so.<br />
* [[Bookmarklet to log projects]] : many do-good projects exist across many organizations, spaces, and events. Some were created at hackathons, some have nothing to do with response (but could be useful in crises), and there is no repository of these projects for those building or needing tools. How can we log them in a decentralized way?<br />
* [[Media guide for extreme events]] : crises are often accompanied by a media frenzy, and those already stressed because of the impact on their lives are also expected to be spokespeople for their neighborhood. If you're a reporter, how can you act in good faith in an affected region? If you're a member of the affected population, what are ways to approach media inquiries from a social justice perspective?<br />
* [[Extreme event preparedness and response for small nonprofits]] : guide for small non profits and other community groups to prepare for, and respond to, crisis.<br />
* [[Communication tools matrix]] : every extreme event is different, but all involve coordinating across many different organizations, timezones, politics, etc. We're working to understand the potential needs of each response, and to map existing communication tools to those needs for speedy selection and setup.<br />
* [[Before you jump in: Missing Persons]] : a guide in how (and when) to build or contribute to a missing persons application.<br />
<br />
==Response Groups and Projects Aspiration Works With==<br />
* [http://climatecentre.org Red Cross Red Crescent Climate Centre] : on [https://aspirationtech.org/blog/willow/nairobi_spring2015 games about citizen reporting], on crowd integration.<br />
* [https://aspirationtech.org/blog/willow/nairobi_spring2015 Dialling Up Resilience] : on accountability mechanisms and local indicators of resilience.<br />
* [http://www.hirondellenews.com/ Hirondelle] : on visually representing their communications network.<br />
<br />
==Words on the Subject==<br />
===The topic on our blog===<br />
Follow and comment on [https://aspirationtech.org/taxonomy/term/72 topical blog entries].<br />
<br />
===Recommended Reading===<br />
* [http://www.democracynow.org/2009/8/31/a_paradise_built_in_hell_rebecca A Paradise Built in Hell] : an easy-to-ready overview of disaster sociology, how people behave in crisis (spoiler: it's not every person for themselves).<br />
* [https://archive.org/details/BlackFlagsAndWindmills Black Flags and Windmills] : review of the politicized relief efforts for Hurricane Katrina performed by the Common Ground Collective.<br />
* [http://cdacollaborative.org/publication/do-no-harm-how-aid-can-support-peace-or-war/ Do No Harm] : review and framework for how to deploy resources into conflict zones without exacerbating the conflict.<br />
The GovLab also has a [http://thegovlab.org/data-and-humanitarian-response/ list of selected readings] worth checking out.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Main_Page&diff=264Main Page2016-06-22T22:16:12Z<p>Willow: /* Recommended Reading */</p>
<hr />
<div>{{About Digital Response}}<br />
<br />
==Join the Conversation==<br />
===Mailing List===<br />
Our '''[https://lists.aspirationtech.org/lists/info/digitalresponse mailing list]''' includes updates about digital responder call-ins, upcoming events, and cross-sector collaborative discussion.<br />
<br />
===Check In Calls===<br />
{{Why Call Ins?}}<br />
<br />
There is a template for how to conduct a digital responder checkin call on the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call checkin call category page]. That page will also give a process for adding your own calls to this wiki.<br />
<br />
{{Checkin Call Summaries}}<br />
<br />
===Direct Contact===<br />
Have a question about this program, but don't necessarily want to talk to a whole group? No worries! Reach out to [mailto:digitalresponse@aspirationtech.org digitalresponse@aspirationtech.org] to be in touch with us directly.<br />
<br />
==[https://digitalresponse.aspirationtech.org/index.php?title=Category:Events Events]==<br />
{{About HumTechFest}}<br />
* [[2016 June Meet Up]] : June 16th in San Francisco, CA. We reviewed MapSwipe, how cross-sector communication works, the ecosystem map, and basic ways of plugging into digital response activities.<br />
* [[2016 June HumTechFest]] : June 4th and 5th in Cambridge, Mass. We played a scenario, talked a lot about institutional and grassroots collaboration, and worked on the [[Digital response ecosystem map]].<br />
* [[2015 May MIT|2015 May HumTechFest]] : our first HumTechFest! We talked about how frontline communities could hold responders accountable, did skill shares around open data, and spec'd out easy-to-create after action report templates.<br />
<br />
==Projects==<br />
{{About Projects}}<br />
* [[Digital response ecosystem map]] : some official organizations have name-brand recognition, there is little understanding of the local, emerging, and digital sectors. Additionally, the flows of information, communication, and other aspects of coordination are poorly understood, even by those within the ecosystem. <br />
* [[Frontline communities holding responders accountable]] : response organizations and individual responders are vital contributors to safety, rebuilding, logistics, etc in many extreme events -- but who holds them accountable? Are there mechanisms by which those most affected by the extreme event might do so? This project suggests a transparency report for how the needs of an affected population were (or were not) addressed by those claiming to do so.<br />
* [[Bookmarklet to log projects]] : many do-good projects exist across many organizations, spaces, and events. Some were created at hackathons, some have nothing to do with response (but could be useful in crises), and there is no repository of these projects for those building or needing tools. How can we log them in a decentralized way?<br />
* [[Media guide for extreme events]] : crises are often accompanied by a media frenzy, and those already stressed because of the impact on their lives are also expected to be spokespeople for their neighborhood. If you're a reporter, how can you act in good faith in an affected region? If you're a member of the affected population, what are ways to approach media inquiries from a social justice perspective?<br />
* [[Extreme event preparedness and response for small nonprofits]] : guide for small non profits and other community groups to prepare for, and respond to, crisis.<br />
* [[Communication tools matrix]] : every extreme event is different, but all involve coordinating across many different organizations, timezones, politics, etc. We're working to understand the potential needs of each response, and to map existing communication tools to those needs for speedy selection and setup.<br />
* [[Before you jump in: Missing Persons]] : a guide in how (and when) to build or contribute to a missing persons application.<br />
<br />
==Response Groups and Projects Aspiration Works With==<br />
* [http://climatecentre.org Red Cross Red Crescent Climate Centre] : on [https://aspirationtech.org/blog/willow/nairobi_spring2015 games about citizen reporting], on crowd integration.<br />
* [https://aspirationtech.org/blog/willow/nairobi_spring2015 Dialling Up Resilience] : on accountability mechanisms and local indicators of resilience.<br />
* [http://www.hirondellenews.com/ Hirondelle] : on visually representing their communications network.<br />
<br />
==Words on the Subject==<br />
===The topic on our blog===<br />
Follow and comment on [https://aspirationtech.org/taxonomy/term/72 topical blog entries].<br />
<br />
===Recommended Reading===<br />
* [http://www.democracynow.org/2009/8/31/a_paradise_built_in_hell_rebecca A Paradise Built in Hell] : an easy-to-ready overview of disaster sociology, how people behave in crisis (spoiler: it's not every person for themselves).<br />
* [https://archive.org/details/BlackFlagsAndWindmills Black Flags and Windmills] : review of the politicized relief efforts for Hurricane Katrina performed by the Common Ground Collective.<br />
* [http://cdacollaborative.org/publication/do-no-harm-how-aid-can-support-peace-or-war/ Do No Harm] : review and framework for how to deploy resources into conflict zones without exacerbating the conflict.<br />
The GovLab also has a [http://thegovlab.org/data-and-humanitarian-response/ list of selected readings] worth checking out.</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=263Before you jump in: Missing Persons2016-06-17T18:26:17Z<p>Willow: /* Complications versus easing interaction */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
There are already missing persons tools and organizations which have been vetted for capacity and integrity for follow-through and security. Here are the few most successfully used ones: American Red Cross’ [http://www.redcross.org/find-help/contact-family/register-safe-listing Safe and Well], [http://google.org/personfinder/global/home.html Google Person Finder], [http://sahanafoundation.org/ Sahana], [https://refunite.org/ Refugees United], International Committee of the Red Cross’ Restoring Family Links, National Center for Missing & Exploited Children. Please offer to help improve and maintain these existing tools (code repos and communities are linked to from each name)! If you are uncomfortable or unsure of how to contact them, please let me/Tim know!<br />
<br />
However, we also understand that the world changes. We gain access to new technologies, there are new clever people in the world, and our understandings of situations change. There is '''always''' room for improvement in this space, just as any other. Want to do something substantively “better” or different than what the existing tools and organizations already do? Here’s what you need to know:<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]<br />
<br />
[[Category:Project]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=262Before you jump in: Missing Persons2016-06-17T18:24:35Z<p>Willow: /* This is an inhabited space */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
There are already missing persons tools and organizations which have been vetted for capacity and integrity for follow-through and security. Here are the few most successfully used ones: American Red Cross’ [http://www.redcross.org/find-help/contact-family/register-safe-listing Safe and Well], [http://google.org/personfinder/global/home.html Google Person Finder], [http://sahanafoundation.org/ Sahana], [https://refunite.org/ Refugees United], International Committee of the Red Cross’ Restoring Family Links, National Center for Missing & Exploited Children. Please offer to help improve and maintain these existing tools (code repos and communities are linked to from each name)! If you are uncomfortable or unsure of how to contact them, please let me/Tim know!<br />
<br />
However, we also understand that the world changes. We gain access to new technologies, there are new clever people in the world, and our understandings of situations change. There is '''always''' room for improvement in this space, just as any other. Want to do something substantively “better” or different than what the existing tools and organizations already do? Here’s what you need to know:<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=261Before you jump in: Missing Persons2016-06-17T18:23:47Z<p>Willow: /* This is an inhabited space */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
There are already missing persons tools and organizations which have been vetted for capacity and integrity for follow-through and security. Here are the few most successfully used ones: American Red Cross’ [http://www.redcross.org/find-help/contact-family/register-safe-listing Safe and Well], [http://google.org/personfinder/global/home.html Google Person Finder], [http://sahanafoundation.org/ Sahana], [https://refunite.org/ Refugees United], International Committee of the Red Cross’ <br />
<br />
However, we also understand that the world changes. We gain access to new technologies, there are new clever people in the world, and our understandings of situations change. There is '''always''' room for improvement in this space, just as any other. Want to do something substantively “better” or different than what the existing tools and organizations already do? Here’s what you need to know:<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=260Before you jump in: Missing Persons2016-06-17T18:22:00Z<p>Willow: /* This is an inhabited space */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
There are already missing persons tools and organizations which have been vetted for capacity and integrity for follow-through and security. Here are the few most successfully used ones: American Red Cross’ [http://www.redcross.org/find-help/contact-family/register-safe-listing Safe and Well], [http://google.org/personfinder/global/home.html Google Person Finder], [http://sahanafoundation.org/ Sahana], [https://refunite.org/ Refugees United], <br />
<br />
However, we also understand that the world changes. We gain access to new technologies, there are new clever people in the world, and our understandings of situations change. There is '''always''' room for improvement in this space, just as any other. Want to do something substantively “better” or different than what the existing tools and organizations already do? Here’s what you need to know:<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=259Before you jump in: Missing Persons2016-06-17T18:21:44Z<p>Willow: /* This is an inhabited space */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
There are already missing persons tools and organizations which have been vetted for capacity and integrity for follow-through and security. Here are the few most successfully used ones: American Red Cross’ [http://www.redcross.org/find-help/contact-family/register-safe-listing Safe and Well], [http://google.org/personfinder/global/home.html Google Person Finder], <br />
<br />
However, we also understand that the world changes. We gain access to new technologies, there are new clever people in the world, and our understandings of situations change. There is '''always''' room for improvement in this space, just as any other. Want to do something substantively “better” or different than what the existing tools and organizations already do? Here’s what you need to know:<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=258Before you jump in: Missing Persons2016-06-17T18:21:31Z<p>Willow: /* This is an inhabited space */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
There are already missing persons tools and organizations which have been vetted for capacity and integrity for follow-through and security. Here are the few most successfully used ones: American Red Cross’ [http://www.redcross.org/find-help/contact-family/register-safe-listing Safe and Well], <br />
<br />
However, we also understand that the world changes. We gain access to new technologies, there are new clever people in the world, and our understandings of situations change. There is '''always''' room for improvement in this space, just as any other. Want to do something substantively “better” or different than what the existing tools and organizations already do? Here’s what you need to know:<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=257Before you jump in: Missing Persons2016-06-17T18:21:07Z<p>Willow: /* This is an inhabited space */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
There are already missing persons tools and organizations which have been vetted for capacity and integrity for follow-through and security. <br />
<br />
However, we also understand that the world changes. We gain access to new technologies, there are new clever people in the world, and our understandings of situations change. There is '''always''' room for improvement in this space, just as any other. Want to do something substantively “better” or different than what the existing tools and organizations already do? Here’s what you need to know:<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=256Before you jump in: Missing Persons2016-06-17T18:20:36Z<p>Willow: /* Complications versus easing interaction */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
Your goal is to make finding loved ones easier, right? Think about how many tools are already in play (see “This is an inhabited space” section above), and what adding one more to the mix would be like. Every new missing persons platform is another point of decision-making stress on the missing persons and those seeking them. Imagine being asked for personal information about yourself while under extreme duress over and over and over again.. or having to repeatedly enter in the details of someone you love and are deeply worried about while on a desperate search for them. The listed existing tools have gone through (and in some cases, are still working out) data sharing flows to reduce these stressors while still maintaining their commitments to privacy and security of the data they hold. If you launch your tool, you’ll need to adhere to the same levels of empathy, respect, privacy, and sharing. (Side note, please don’t start a “uniting platform,” either, lest we get [https://xkcd.com/927/ here]. That’s what sharing standards are about.)<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=255Before you jump in: Missing Persons2016-06-17T18:20:19Z<p>Willow: /* Complications versus easing interaction */</p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
[http://www.timschwartz.org/ Tim] and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=254Before you jump in: Missing Persons2016-06-17T18:19:54Z<p>Willow: </p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==<br />
<br />
==A component, not a solution==<br />
The software-based frontend and backing database are a TINY FRACTION of the overall system of missing persons reunification efforts. People are often missing for a *reason*, possibly because of political unrest, domestic violence, or displacement. If your platform publishes photos of someone or their geographic location, will someone try to come after them? Can you protect their physical and emotional wellbeing? There are national and international laws in place to protect such individuals, especially children, and your component of the system must be in alignment with those laws (or have a damn good and intentional reason for not being as such). Ethically, you should also respect an individual’s desire or need for privacy. In the Missing Persons Community of Interest, organizations handling missing persons data are reviewed by external parties for their ability to perform long-term maintenance and protection of said data. You and your tool will need to undergo the same rigor before being launched.<br />
<br />
==Complications versus easing interaction==<br />
<br />
<br />
We look forward to your heartfelt, well-thought out contributions to this space.<br />
<br />
and [[User:Willow|Willow]]</div>Willowhttps://digitalresponse.aspirationtech.org/index.php?title=Before_you_jump_in:_Missing_Persons&diff=253Before you jump in: Missing Persons2016-06-17T18:17:48Z<p>Willow: </p>
<hr />
<div>When a disaster occurs, whether fast like an earthquake or slow like a drought or war, people go missing. As outsiders wishing to contribute to restoring the stability of our worlds, the desire to reunite friends and loved ones through the technology we know so well can be tempting. Making use of our knowledge of social platforms, geotagging, and databases is far easier than addressing the long-term systemic injustices which allow these crises to affect entire populations in the way they do, afterall. But let’s say a typhoon has just made landfall, or that there’s a sudden influx of refugees from a drought-blighted country, and you and a group of your friends have gathered to see what you can do about it. This is beautiful — we need to learn how to work in solidarity with those in other geographies. But it’s also a delicate space. This particular post is about whether or not you should build that missing persons app, or spend your time contributing to something like [http://google.org/personfinder/global/home.html Google Person Finder], [https://www.openstreetmap.org/ OpenStreetMap], [http://sahanafoundation.org/ Sahana], or [http://blog.standbytaskforce.com/ Standby Task Force] instead.<br />
<br />
The missing persons/reunification domain of humanitarian response is not just about people logging themselves so as to be findable by those missing them. It’s also about those individuals being protected during the process, having support in finding those they’ve been separated from, and the infrastructure which surrounds these actions. Software has a lot to contribute to connection, information security, and sorting through indexes, but missing persons is a delicate space with real humans in the mix.<br />
<br />
==This is an inhabited space==</div>Willow