Offline to Online Data Management & Process after Hurricane sandySougwen Chung, Interactive art director / Interoccupy
Where to begin?Information re: volunteer locations / needs found in            Occupy sandy mobilized faster- news (source...
Occupy Sandy V1Built on the Interoccupy Network -> Publishing platform for OccupySystem not built for the breadth of infor...
Volunteer submitted mapmanually updated1 map of dozensvolunteer commitment to maintenanceduplication / inconsistencies imp...
Inefficiencies encountered:- SYNCING ISSUESmultiple places where information needs to beupdated- COMMUNICATION ISSUESUrgent...
Occupy SandyProcess: Week 1 Overview- Email / on-site spreadsheet(120+ person collab doc)- Wordpress- Google Maps- To do l...
Using existing tools....Leveraging Google Fusion Tables / Social Media
Occupy SandyProcess: Present OverviewDATA SOLUTION:Google Fusion Tables- Consolidated data- leverage existing product- low...
Using existing tools....- Google Fusion tableswere made for datamanagement andvisualization.- Twitter was made forshort, t...
The Obvious Solution- Insight: It isn’t the most elegant solution, it was the easiest to implement with limited time / res...
THE RESULTBuilt in less than 6 days, small team...Using existing Occupy network / circle of trust...Erica Heinz, Greg Osof...
THE RESULTBuilt in less than 6 days, small team...Using existing Occupy network / circle of trust...Erica Heinz, Greg Osof...
THE RESULTBuilt in less than 6 days, small team...Using existing Occupy network / circle of trust...Erica Heinz, Greg Osof...
Result:Occupy Sandy volunteer data populates onvolunteer layer on Google Crisis maps
Next steps: TECHIn talks with Google re: how to improvefusion tablesIntegration with Sahana, software madespecifically for ...
Next steps: Process / Communication / NarrativeDocumenting lessons learned this time around for futureresponse effortsimpr...
Relevant questions                               Recap                                                 1) Don’t reinvent t...
- IMMEDIATE:                                          MEDIUM TERMAssisting in designing Workflows for volunteers        1) ...
Thanks!contact: soujourns@interoccupy.nettwitter: @sougwen
Occupy Sandy Presentation for Yoxi / #OperationSandy @NYU
Occupy Sandy Presentation for Yoxi / #OperationSandy @NYU
Upcoming SlideShare
Loading in …5
×

Occupy Sandy Presentation for Yoxi / #OperationSandy @NYU

255 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
255
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Occupy Sandy Presentation for Yoxi / #OperationSandy @NYU

    1. 1. Offline to Online Data Management & Process after Hurricane sandySougwen Chung, Interactive art director / Interoccupy
    2. 2. Where to begin?Information re: volunteer locations / needs found in Occupy sandy mobilized faster- news (sources: red cross, fema, etc) Mutual aid- Word of mouth -> local drop off in my neighbourhood Communities helping communities- Unreliable information via youtube re local drop off points- Finding a comprehensive resource in OccupySandy.org - Organic entity’s burgeoning process - communication flow gaps
    3. 3. Occupy Sandy V1Built on the Interoccupy Network -> Publishing platform for OccupySystem not built for the breadth of information that would come
    4. 4. Volunteer submitted mapmanually updated1 map of dozensvolunteer commitment to maintenanceduplication / inconsistencies impact authority ofinformation
    5. 5. Inefficiencies encountered:- SYNCING ISSUESmultiple places where information needs to beupdated- COMMUNICATION ISSUESUrgent requests are made but seldom is therefollow up for when request has been fulfilled- SO MUCH LAGcrazy bottlenecking makes information updatesslow- Pushing the cart before the horsethe nature of rapid response?
    6. 6. Occupy SandyProcess: Week 1 Overview- Email / on-site spreadsheet(120+ person collab doc)- Wordpress- Google Maps- To do list spreadsheet- manual updates, closed system
    7. 7. Using existing tools....Leveraging Google Fusion Tables / Social Media
    8. 8. Occupy SandyProcess: Present OverviewDATA SOLUTION:Google Fusion Tables- Consolidated data- leverage existing product- low barrier to entry across teams- map visualization + publishing to website viaFusion Table APIUPDATE SOLUTION:
    9. 9. Using existing tools....- Google Fusion tableswere made for datamanagement andvisualization.- Twitter was made forshort, timely, updatesand communication
    10. 10. The Obvious Solution- Insight: It isn’t the most elegant solution, it was the easiest to implement with limited time / resources
    11. 11. THE RESULTBuilt in less than 6 days, small team...Using existing Occupy network / circle of trust...Erica Heinz, Greg Osofsky, Charles(Radgeek),Michael Badger, Andrea Ciannavei,Sougwen ChungUpdates via twitterTimely posts, hashtags, facilitatescommunication between major on-site reliefefforts and individuals for needs fulfillment
    12. 12. THE RESULTBuilt in less than 6 days, small team...Using existing Occupy network / circle of trust...Erica Heinz, Greg Osofsky, Charles(Radgeek),Michael Badger, Andrea Ciannavei,Sougwen Chung- Locations can be filtered by type & Location- improved information design- Colour coded- Community pages are filtered embeds of thesame data set (Whee)
    13. 13. THE RESULTBuilt in less than 6 days, small team...Using existing Occupy network / circle of trust...Erica Heinz, Greg Osofsky, Charles(Radgeek),Michael Badger, Andrea Ciannavei,Sougwen Chung- Locations can be filtered by type & Location- improved information design- Colour coded- Community pages are filtered embeds of thesame data set (Whee)
    14. 14. Result:Occupy Sandy volunteer data populates onvolunteer layer on Google Crisis maps
    15. 15. Next steps: TECHIn talks with Google re: how to improvefusion tablesIntegration with Sahana, software madespecifically for on-site disasterresponse. Sahana updates to FT(dreamworld)
    16. 16. Next steps: Process / Communication / NarrativeDocumenting lessons learned this time around for futureresponse effortsimproving communication between On-site and Online(still a lot of gaps and redundancy)Creating narrative through collaborations to educate,raise awareness, sustain interest
    17. 17. Relevant questions Recap 1) Don’t reinvent the wheel! - What don’t I know that I NEED to know tohelp? 2) Support systems already in place and offer - does it already exist? Can I improve / another perspectiveleverage existing product if it does? 3) The silver lining in data entry Understanding more about whats needed by doing unfun stuff / gaining trust / asking questions
    18. 18. - IMMEDIATE: MEDIUM TERMAssisting in designing Workflows for volunteers 1) How to collaborate with the Fusion Table team,! - placement, education, coordination, get the right contacts, to share what we’ve learned.scheduling, TRUST Help them improve their product. -- First meeting on Monday- Long term commitment! - Creating content that initiates / 2) How to document processes for initialencourages people to get involved after the collaboration -- easy to implement in a small teaminitial shock of crisis has worn off, sustained but the issue of getting people to work together isengagement still a huge issue -- fragmented processes- Improving communicating between Online and -- distance is a factorOnsite -- i know what i know, you know what you know! - currently onsite is testing this proprietarysoftware called Sahana 3) First responders starter kit. Formalizing the! - inking their information with interoccupy systems started at Interoccupy. The resources ARE out there in many forms but AWARENESS is limited. Doing more research and documenting / sharing... resulting in hopefully a reduced barrier to entry.. look into (Hurricane Hackers, Sahana, Spark Relief maps, Need Supply, more..)
    19. 19. Thanks!contact: soujourns@interoccupy.nettwitter: @sougwen

    ×