Difference between revisions of "2016 April 12"

From Digital Response
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
==About digital responder checkins==
+
: Call took place Tuesday, April 12th at 11a PT / 14:00 ET / 19:00 GMT / 21:00 EAT
−
Digital response checkins are, at their most basic, a way to strengthen the connections across the digital response space. Some might be more focused or topical, but these are meant as white-label (unowned) spaces for members of various organizations to have a chance to collaborate. Organizations and other ways of delineating and focusing efforts are absolutely necessary, but so is a space external to that.
+
: 9 folk dialed in via Maestro Conference. No one had issue getting into the call, but we did have some audio issues.
 +
: Link to audio file, if one exists
  
−
You can read more about past calls and the overall process on the [https://digitalresponse.aspirationtech.org/index.php?title=Category:Checkin_call Checkin call category page].
+
==Overview of how the call will work==
 +
* press 1 for technical difficulties and 2 for wanting to make a point
 +
* Agenda (intros of up to 30 seconds about you and your group, then longer updates on deployments and organizational statuses, then wrap-up)
 +
* Note taking (we all take notes for each other)
 +
* Time keeping (if you go over, you will first be poked via chat, and then verbally interrupted)
  
−
==About this April checkin==
+
==Introductions (Who's here?)==
−
The agenda and notes for this call are taking shape on [https://pad.riseup.net/p/AprilDigiRespCall 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.
+
''30 seconds each : 15 minutes tops total : if you just spoke, take notes for the person who speaks after you.''
−
* Call will take place '''Tuesday, April 12th''' at 11a PT / 14:00 ET / 19:00 GMT / 21:00 EAT
+
 
−
* You'll need to [http://myaccount.maestroconference.com/conference/register/5UTTBGBN498FD3YH register] to join us. Those calling from the US will receive a US-based phone line to call. You can also join from an [http://maestroconference.com/gettingin2 International number or from a computer].  
+
Misty
−
: This call will be recorded after we announce we're starting to record until an end point, after which Off The Record discussion can also happen.
+
: work with Willow to support digital humanitarian response program at Aspiration
 +
Kristin
 +
: the engine room, want to know what's up
 +
Scotty
 +
: From CSUMB and NPS
 +
: Wearable Device Integration and Information Sharing for Mental Wellness
 +
Devin
 +
: president of Sahana - works on resiliencecolab.org
 +
Marty
 +
: freelancing in portland, involved with NTEN & nptech,
 +
Christiaan Adams
 +
: From Google Geo team
 +
: Works with non-profits on mapping and imagery, and with Crisis Response team
 +
Peter
 +
: rainhead@gmail.com
 +
: Univ. of Wash. Human Centered Design and Engineering
 +
: runs Teaching Channel website, https://www.teachingchannel.org
 +
: volunteer, American Red Cross Disaster Services Technology
 +
: freelancer in the space, wants to listen in to hear how things ar egoing
 +
Willow
 +
: Ecosystem map
 +
Helen
 +
: Nethope, Coordinated data scramble, decision makers needs.
 +
 
 +
==Review of [[2015_Nov_27|Last Call]]'s Collaboration==
 +
''We'd love to hear about progress on projects in the digital response space, '''especially''' if it involves two or more organizations represented on this call.''
 +
 
 +
 
 +
===Resilience CoLab===
 +
Site to check out what a website is capable of. If people want to join and check it out that's rad. But check out off-the-shelf WordPress functionality for their own purposes. Plugin for needs indication. If you have an org doing disaster (Especially digital) response work, you're likely creating streams of info to keep people up to date on work. With something like the DHN, it's difficult to know what's going on with everyone. So having everyone have a place to add RSS and Twitter feeds to then be curated to go in front of people could be really useful. Collective feed curation. Very standard Wordpress backend.
 +
 
 +
Can also do badging, leverage buddypress network. Admins can set up tasks by setting up information, give badges which can be taken anywhere. Could get a SBTF badge and show it to a HOT community.
 +
 
 +
Commons in a box has a bunch of plugins that are managed centrally for easier management and deployment. no coding required. Easy to set up. You can do it centrally. Has some documentation about the plugins.
 +
 
 +
https://resiliencecolab.org/2016/01/introducing-data-models-for-humanitarian-services-2/
 +
* Contact: Devin
 +
* Need: project pages
 +
* Need: help curate
 +
 
 +
 
 +
===Coordinated Data Scramble===
 +
Quick summary - Since 2011.  At the beginning of an emergency there is a big data scramble.  Would be lots of benefits of coordinating this better. Main area - who has data? who needs data?  how do we get it? Next INWG meeting in a couple of week.  Looking for them to sign off on initial "Data List"
 +
 
 +
How do we implement into a system where people can coordinate? We set up a Trello board for Fiji, first column of cards was all the datasets which might be needed. next was datasets identified as priorities through a survey thorugh the DHN partnership meeting. Then people are working on the data, and links to it. So when people have a need or start working on it, they can update the card. Show the status the data is in.Feedback that people quite like that. Trello is an initial test of the system, might want to build our own version that's a bit more specific to emergencies.
 +
* Contact: Helen
 +
* Need: People that join the skype groups early in a response, we'd love your feedback on how the trello board is set up. Cluster leads should define priorities. Could maybe set up a test version to play with over a series of days.
 +
* Need: Start thinking about if we want a specific version
 +
* Feedback from group (please leave your contact somehow so folk can follow up with you, but know these notes end up in a public place).
 +
** Send to Misty, Scotty, Peter, Martin
 +
** Peter is interested in how these tools are built in general
 +
 
 +
 
 +
===Data/Map Filter===
 +
Categorize each map to the types of questions they might help answer. Datasets shared based on those maps (based on the data scramble)
 +
* Contact: Helen
 +
 
 +
 
 +
===HumTechFest and Book Sprint===
 +
June 4th and 5th in Cambridge, Mass. https://aspirationtech.org/events/humtechfest/cambridge/2016/june
 +
* Contact: willow
 +
* Need: more ideas of things that should be covered at the event
 +
* Need: if you'd like to attend this collaborative event, we'd love to have you there!
 +
 
 +
==Project and Deployment Overviews==
 +
''What is new, that hasn't been gone over yet?''
 +
===Ebola: a Big Data Disaster===
 +
https://responsibledata.io/big-data-ebola-data-responsible-data/
 +
 
 +
Some of the data collection and sharing efforts around Ebola response opened up groups to legal ramifications. We should maybe be more responsible, both for ethical and legal reasons.
 +
 
 +
 
 +
===Google Crisis response team===
 +
Work on info for disaster-affected populations. Products include Google Public Alerts: official alerts on Google Search, Google Maps and google now. Information available to people in the place where people are looking for that information. We have lots of geographic and other datasets. Person finder tool. Christiaan is on the geo side so mapping, aerial & satellite imagery, and sub(?) info.
 +
*Excited to see Coordinated Data Scramble going on. Useful to us as we look for datasets to publish through our crisis maps.
 +
 
 +
===Wearable Sensor Integration for Personal Resiliency===
 +
low-cost, open-source, secure architectures and protocols allowing for data from wearable sensors to be integrated with self-reported information on mood, food and activities, etc, and securely shared with one's support structure to monitor mental healt and improve overall wellness. Software components for next semester. If anyone has good USB and hardware development we'd love to talk to them. Pry some APIs out of them. Get sensors into an environment with the data from multiple devices (personal and environmental sensors) to help a person based on what they're encountering at the time. Reduce stress. Create an ecosystem around it, not a standalone.
 +
*Contact:  Scotty  via jerryscott@gmail.com
 +
* Need: contacts in the hardware world to find/fix API, or USB Bluetech Hackers to get access to some devices
 +
* Need:
 +
* Feedback from group (please leave your contact somehow so folk can follow up with you, but know these notes end up in a public place).
 +
** https://www.dropbox.com/s/5rmq7xpkremwuvx/Whiteboard%208mar16.pptx?dl=0
 +
** https://www.dropbox.com/s/qg2giosq8jm15bn/willow%20whiteboard.JPG?dl=0
 +
 
 +
===Field Experimentation for Humanitarians===
 +
Field experimentation for humanitarian response has been conducted several times at Camp Roberts with the support of Naval Postgraduate School.  This venue continues to be avaiable for humanitarian experimentation on a space available basis.  A small group of us is looking at establishing a similar line of experimentation outside of federal and military support, More to follow soon. If interested, I'll add to you an email list when we start that. Looking at how to engage with IEEE Global Humanitarian Technology Conference - call for papers (abstracts due next week 18 Apr) http://sites.ieee.org/ghtc/author-central/call-for-papers-2016/
 +
* Contact: Scotty va jerryscott@gmail.com / nps.edu/fx / grscott@nps.edu
 +
* Need: People who have worked on previous Camp Roberts Experimentation that might want to collaborate on a paper for the IEEE Humanitarian Technology Conference in August
 +
* Need: Ideas for how to create a sustainable, field experimentation program, geared directly towards humanitarian responders at all levels of organization (big formal to grassroots leadersless non-orgs)
 +
* Feedback from group (please leave your contact somehow so folk can follow up with you, but know these notes end up in a public place).
 +
** Willow needs to loop back about ENCAPE (emergent needs and collaborative planning)
 +
 
 +
==Reflections on platform and process==
 +
Sound quality was super rough. Might have impacted how people were interacting.
 +
 
 +
Phone better than computer for Maestro. no reports of issues calling.
 +
* Willow your line is very fuzzy (I think it might be your mic?) - maybe just too close to the mic? It got better througout the call.
 +
* listening sound quality much improved via cell for me although still not entirely intelligible, but the web interface for the phone option does not progress to a page where i can raise my hand (maybe firewall - had same problem from my work network, but not from a cell phone hotspot)
  
 
[[Category:Checkin call]]
 
[[Category:Checkin call]]

Latest revision as of 16:53, 14 April 2016

Call took place Tuesday, April 12th at 11a PT / 14:00 ET / 19:00 GMT / 21:00 EAT
9 folk dialed in via Maestro Conference. No one had issue getting into the call, but we did have some audio issues.
Link to audio file, if one exists

Overview of how the call will work

  • press 1 for technical difficulties and 2 for wanting to make a point
  • Agenda (intros of up to 30 seconds about you and your group, then longer updates on deployments and organizational statuses, then wrap-up)
  • Note taking (we all take notes for each other)
  • Time keeping (if you go over, you will first be poked via chat, and then verbally interrupted)

Introductions (Who's here?)

30 seconds each : 15 minutes tops total : if you just spoke, take notes for the person who speaks after you.

Misty

work with Willow to support digital humanitarian response program at Aspiration

Kristin

the engine room, want to know what's up

Scotty

From CSUMB and NPS
Wearable Device Integration and Information Sharing for Mental Wellness

Devin

president of Sahana - works on resiliencecolab.org

Marty

freelancing in portland, involved with NTEN & nptech,

Christiaan Adams

From Google Geo team
Works with non-profits on mapping and imagery, and with Crisis Response team

Peter

rainhead@gmail.com
Univ. of Wash. Human Centered Design and Engineering
runs Teaching Channel website, https://www.teachingchannel.org
volunteer, American Red Cross Disaster Services Technology
freelancer in the space, wants to listen in to hear how things ar egoing

Willow

Ecosystem map

Helen

Nethope, Coordinated data scramble, decision makers needs.

Review of Last Call's Collaboration

We'd love to hear about progress on projects in the digital response space, especially if it involves two or more organizations represented on this call.


Resilience CoLab

Site to check out what a website is capable of. If people want to join and check it out that's rad. But check out off-the-shelf WordPress functionality for their own purposes. Plugin for needs indication. If you have an org doing disaster (Especially digital) response work, you're likely creating streams of info to keep people up to date on work. With something like the DHN, it's difficult to know what's going on with everyone. So having everyone have a place to add RSS and Twitter feeds to then be curated to go in front of people could be really useful. Collective feed curation. Very standard Wordpress backend.

Can also do badging, leverage buddypress network. Admins can set up tasks by setting up information, give badges which can be taken anywhere. Could get a SBTF badge and show it to a HOT community.

Commons in a box has a bunch of plugins that are managed centrally for easier management and deployment. no coding required. Easy to set up. You can do it centrally. Has some documentation about the plugins.

https://resiliencecolab.org/2016/01/introducing-data-models-for-humanitarian-services-2/

  • Contact: Devin
  • Need: project pages
  • Need: help curate


Coordinated Data Scramble

Quick summary - Since 2011. At the beginning of an emergency there is a big data scramble. Would be lots of benefits of coordinating this better. Main area - who has data? who needs data? how do we get it? Next INWG meeting in a couple of week. Looking for them to sign off on initial "Data List"

How do we implement into a system where people can coordinate? We set up a Trello board for Fiji, first column of cards was all the datasets which might be needed. next was datasets identified as priorities through a survey thorugh the DHN partnership meeting. Then people are working on the data, and links to it. So when people have a need or start working on it, they can update the card. Show the status the data is in.Feedback that people quite like that. Trello is an initial test of the system, might want to build our own version that's a bit more specific to emergencies.

  • Contact: Helen
  • Need: People that join the skype groups early in a response, we'd love your feedback on how the trello board is set up. Cluster leads should define priorities. Could maybe set up a test version to play with over a series of days.
  • Need: Start thinking about if we want a specific version
  • Feedback from group (please leave your contact somehow so folk can follow up with you, but know these notes end up in a public place).
    • Send to Misty, Scotty, Peter, Martin
    • Peter is interested in how these tools are built in general


Data/Map Filter

Categorize each map to the types of questions they might help answer. Datasets shared based on those maps (based on the data scramble)

  • Contact: Helen


HumTechFest and Book Sprint

June 4th and 5th in Cambridge, Mass. https://aspirationtech.org/events/humtechfest/cambridge/2016/june

  • Contact: willow
  • Need: more ideas of things that should be covered at the event
  • Need: if you'd like to attend this collaborative event, we'd love to have you there!

Project and Deployment Overviews

What is new, that hasn't been gone over yet?

Ebola: a Big Data Disaster

https://responsibledata.io/big-data-ebola-data-responsible-data/

Some of the data collection and sharing efforts around Ebola response opened up groups to legal ramifications. We should maybe be more responsible, both for ethical and legal reasons.


Google Crisis response team

Work on info for disaster-affected populations. Products include Google Public Alerts: official alerts on Google Search, Google Maps and google now. Information available to people in the place where people are looking for that information. We have lots of geographic and other datasets. Person finder tool. Christiaan is on the geo side so mapping, aerial & satellite imagery, and sub(?) info.

  • Excited to see Coordinated Data Scramble going on. Useful to us as we look for datasets to publish through our crisis maps.

Wearable Sensor Integration for Personal Resiliency

low-cost, open-source, secure architectures and protocols allowing for data from wearable sensors to be integrated with self-reported information on mood, food and activities, etc, and securely shared with one's support structure to monitor mental healt and improve overall wellness. Software components for next semester. If anyone has good USB and hardware development we'd love to talk to them. Pry some APIs out of them. Get sensors into an environment with the data from multiple devices (personal and environmental sensors) to help a person based on what they're encountering at the time. Reduce stress. Create an ecosystem around it, not a standalone.

Field Experimentation for Humanitarians

Field experimentation for humanitarian response has been conducted several times at Camp Roberts with the support of Naval Postgraduate School. This venue continues to be avaiable for humanitarian experimentation on a space available basis. A small group of us is looking at establishing a similar line of experimentation outside of federal and military support, More to follow soon. If interested, I'll add to you an email list when we start that. Looking at how to engage with IEEE Global Humanitarian Technology Conference - call for papers (abstracts due next week 18 Apr) http://sites.ieee.org/ghtc/author-central/call-for-papers-2016/

  • Contact: Scotty va jerryscott@gmail.com / nps.edu/fx / grscott@nps.edu
  • Need: People who have worked on previous Camp Roberts Experimentation that might want to collaborate on a paper for the IEEE Humanitarian Technology Conference in August
  • Need: Ideas for how to create a sustainable, field experimentation program, geared directly towards humanitarian responders at all levels of organization (big formal to grassroots leadersless non-orgs)
  • Feedback from group (please leave your contact somehow so folk can follow up with you, but know these notes end up in a public place).
    • Willow needs to loop back about ENCAPE (emergent needs and collaborative planning)

Reflections on platform and process

Sound quality was super rough. Might have impacted how people were interacting.

Phone better than computer for Maestro. no reports of issues calling.

  • Willow your line is very fuzzy (I think it might be your mic?) - maybe just too close to the mic? It got better througout the call.
  • listening sound quality much improved via cell for me although still not entirely intelligible, but the web interface for the phone option does not progress to a page where i can raise my hand (maybe firewall - had same problem from my work network, but not from a cell phone hotspot)
Retrieved from "https://digitalresponse.aspirationtech.org/index.php?title=2016_April_12&oldid=86"