The real point of global hackathons


TL;DR: it’s global community!

I’m sitting in the iHub Nairobi today, waiting for Space Apps Challenge to start.  I’ve been in Kenya for a few days now, spending time with the amazing techs here, and getting more and more impatient for the first Brcks to go on sale (and not just because I’m about to be working in rural Tanzania).  Because the one thing that holds people back here, and in many other “developing” countries, is connectivity. The ability to connect to the global community of information that the internet and all its pages, apps, and datastores offers without having those “I would get you that information but the power just went off / the internet just went down” moments.  Brck is designed to help solve that type of connectivity problem.  But there are other forms of connection happening across the internet: the human ones.

Back in 2010, Spike Foote and I spent 48 very long hours connecting people across the world working on similar problems (or the same problems) in different Random Hacks of Kindness cities.  I still remember the shock from the iHub, and especially the AkiraChix, that people outside Nairobi were watching what they did, and wanted to reach out and connect to them.  Yes, there are many comments about how effective the projects from global hackathons are and aren’t, and there are things that could be done better, like organizing global lists of for-good hackathons and projects done and to do (which is one reason that OpenGoodHacks was created), but the one thing that I always point to, that I always come back to, is that global hackathons create global hacker communities.  These are the people who really solve the problems in a country – the people from those countries, working together with people around the world, sharing ideas.  In 2010, I watched the Nairobi hackers teach US hackers about mobile phone programming.  These are the kinds of connections that make us strong together.

And now, as I sit here waiting for Nairobi to start, whilst checking comments from SpaceApps sites around the world, in a space that has fostered many local tech companies and many great local hackers, I think about the challenges ahead for this globalized world.  I am more aware than ever that we have to connect across borders and continents, and that the best way in for many many people is through global hackathons like this.  That, and remembering to create low-bandwidth versions of the tech pages that people here need access to!

Maps of Maps


I amused myself last night by answering one of my burning questions, namely “can I make a better list of crisis maps out of all the partial lists I have lying around”.

Here’s the original map of Ushahidis:

Here’s a copy of the draft results (i you want edit access to the real thing, just ask… and blame the spammers for this – they’re even targetting maps now) – my other unanswered questions include whether there’s been a drop-off, rise or steady number of new maps, and how the categories lists have changed over the past few years (I’ll put the scraper for that into github).

And here, for balance, are some Esri crisis maps. Because I just downloaded their WordPress plugin, and it’s, kinda, playtime.

OpenCrisis Townhall Meeting 21st February 2014


What’s This?

Meeting: OpenCrisis TownHall

Date: 20th February 2014

Agenda: a roundup of what we’ve been doing and deployments we’ve heard about in the past month; a check on what groups and people needed; and an outline plan for the coming month.

Who was present: Sara, Pat, Donna, Rose, Leesa, om, Brendan…later Hilary Nicole

Last month: 23 January 2014 minutes

What’s Happened?

Past month: Deployments

  • What: South Sudan crisis

    • who:  HOT OSM, GISCorps, Ushahidi, OpenCrisis, MapAction

    • where:  South Sudan

    • what:  OpenCrisis set up coordination skypechat and googledoc (http://bit.ly/1f9C457) for groups mapping the South Sudan crisis. HOT OSM has mapped several affected areas, in collaboration with UNITAR/UNOSAT, HIU (State Dept)  with assistance from GISCorps and, for area identification, OpenCrisis (BOH). MapAction has also been working with OCHA. sending a two-person team to Juba for a period.

    • Deployment dates:  24th December – continuing (contact Brendan or Sara)

 

  • What: Central African Republic crisis

    • who:  HOT OSM

    • where:  CAR

    • what:  HOT has been doing a lot of mapping – both settlements and infrastructure, since the crisis began. State Dept’s HIU has been helping with current sat imagery provision

    • Deployment dates:  HOT has been active for CAR/RCA for over a year, but this activity has intensified since mid-late December 2013

 

  • Events with monitoring but not deployments:

    • Kyiv (Kiev) demonstrations – concern and willingness to map seen online, http://www.galas.org.ua/ – Ukrainian language Ushahidi crisis map

    • Mt Sinabung eruption (Sumatra, Indonesia) – HOT OSM task for this http://tasks.hotosm.org/job/412.

    • UK floods.  London hackathon, Justine Mackinnon involved with local work.

    • Samar East (Philippines): big forest fire in Balangiga area – call for crisis mapping assistance on Crisismappers list (20 Feb)…not clear if any organised response to it

    • US Northeast cold – not monitored; some VOST local deployments.

Past month: Activities

 

OpenCrisis

  • Blogposts: great posts this past month (including on data ownership, data security & publication issues, Monitoring & Evaluation, LGBT/GBV mapping issues, verification) – keep ‘em coming!

  • Anahi email in Crisismappers mailing list: about South Sudan data prompted much research, much debate and two OpenCrisis blogposts – ‘Who owns crisis data?’ and ‘Concerning responsible use and publication of crisis data for South Sudan

  • OpenCrisis platforms: Migration to WordPress almost complete (just link integrity survey and fettling to be finished off) – site now fully functioning.

  • Membership: 27 people on WP site (few more to be asked if want to be added), including 1st applications direct from new site; 24 on OpenCrisis Googlegroup; (37 on total list…but some of these have just cruised by once…and therefore probably shouldn’t be counted)

  • Drones – any progress Joseph?

  • Training – was a busy month… open data training delayed till March, but will happen. Dhairya (& Brendan, to lesser extent) contributed to a TechChange training course

  • Twitter a/c: much more active over last 3 weeks – but could still be moved up notch

  • Personal Democracy Forum suggested that we submit a talk to them on our South Sudan dataset experience and learnings.

  • OpenCrisis involved in ongoing discussions (as observer, minor contributor) with HOT, State Dept’s HIU about mechanics of provision of sat imagery to community, workflows prior to HIU’s rollout of MapGive program

 

Other community activities

  • Humanitarian Data Project: getting going again – have started an online list of community-created datasets as part of a discussion on how to license and open these. Have also connected HDP to the Ushahidi CrisisNet project (which isn’t aimed at crisismapping, but does have some overlaps with it).

  • Accademics / SBTF Academics: Joseph launching room and collaboration space this weekend: “I’m in the process of setting a large group of academics for the purpose of creating joint university-level courses in Crisis Mapping, Crisis Management, Geo-Informatics. In addition I think this group is a great forum to discuss inter-institutional consortiums for the design of new approaches and technologies for humanitarians and civil protection. It’s another great way to meet the top academics committed to social good through technology. Join us by adding me on skype @ josephrichardpollack or sending me an email. Looking forward to your participation!” – Joseph.

  • Data handling guidelines – we need these,and SBTF have asked for some too. Who’s up for research and writing some? BOH is…

  • ODbL license: may be more restrictive than we (and HOT OSM) think. We need to investigate this asap (especially since all recent OC datasets have ODbL licenses on them), and see if we can get some legal help with it.

  • info4disasters website: Info4 is regrouping regarding “Country Pages” and EOCs in light of the “found” materials Sara pointed us to on the Wayback Machine (a great archive site for looking for “lost” internet pages)

  • WHS: info4disasters & SBTF working on the World Humanitarian Summit (deployment of DHN). Proposed that OpenCrisis assist Info4Disasters with part of their remit for this.

  • Wider discussions on data security, conflict data & associated mapping: see Heather Leson’s great post here.

 

Other activities:

 

  • Hackathons: International Open Data Day and CodeAcross (see Pat).

News, Announcements etc

AOB

  • Next Townhall meeting: 14th March  2014.   TownHalls are on the second Friday of every month (formerly Wednesdays), at 12:00 EST / 17:00 GMT unless otherwise stated.  Remaining Townhalls for 2014 are: 14th March, 11th April, 9th May, 13th June, 11th July, 8th August, 12th September, 10th October, 14th November, 12th December.

  • DHN new website up (http://dev.dhn.amanisites.org/) as of this week – seeking feedback from any DHN members of members – https://docs.google.com/forms/d/144DNNShKAb0c8BNRO7TjW5LsnVqV9E_5ESsU1dY7FyI/viewform

  • Cool tool: MapWarper.net, for aligning old maps with modern location-corrected maps

  • Has been ‘strongly suggested’ that OpenCrisis contribute to Personal Democracy Forum, June 2014, New York

  • OpenCrisis is now registered at ALNAP – meaning we get updates on events, jobs, opportunities in humanitarian learning field. “The Active Learning Network for Accountability and Performance in Humanitarian Action (ALNAP) is a system-wide organisation dedicated to improving the accountability and performance of humanitarian action by strengthening the humanitarian evidence base through sharing lessons, researching key issues and, where appropriate, providing leadership to find collective approaches and solutions.”

  • GDELT, the conflict data warehouse, is back!  see here. And…it has a new home – here.

What do we need to do?

Last month’s plan

  • Create agenda for next month (use template) (DONE)

  • Sara to make list of all the people and groups who email her about crisismapping

  • Platform discussion (DONE)

  • Incorporation discussion (DONE)

  • Launch new opencrisis.org site on Saturday 25th January… continue to populate this, and explore complementary platform options. (DONE)

  • Sara – write a page about open data licenses and how to do them right (DONE)

  • Lillian to write blogpost about the maze of finding open data in Thailand

  • Brendan writing blogpost about ‘Geolocation in context’ (in rough draft…overtaken by other South Sudan issues :P )

  • Rose – summary of verification handbook? Verification Handbook with guidelines to verify digital, user generated content.  Will have guidelines, tools, checklist, etc. Supposed to be released January 2014 (sometime this month), freely available.  Will write summary (REM) (DONE)

  • Sara – post about open data cambodia (but only with permission from team)

  • Sara – run training session on open data.

 

Needs

  • Blogposts for the new website – please write them!

 

Next month’s plan

 

  • By-laws discussion and drafting…and consultation…and adoption

  • ODbL licensing issues: We need to investigate this asap (especially since all recent OC datasets have ODbL licenses on them), and see if we can get some legal help with it. BOH to talk to Lillian; BOH to draft workflows that community can use with e.g., placename databases to ensure that is clear which data are OSM-compatible, and which not

  • Adopt a to-do/task management tool; possible options include…. WordPress plugin (keeps all activity inside OC website) or external tools like:Trello, Asana, Kerika (free for non-profits), Atlassian (also free for non-profits, IIRC), RedMine.

  • Ask for OpenCrisis seat at Oakland event on crisismapping and security concerns.

  • Discuss with Info4Disasters how OpenCrisis might contribute to WHS work

  • Data handling guidelines – draft these, get feedback from groups inc SBTF

  • Feedback on DHN website – please! (see above – form here)

  • Brendan writing blogpost about ‘Geolocation in context’

  • Lillian to write blogpost about the maze of finding open data in Thailand

  • Sara – run training session on open data.

  • need to have a slightly more organised division of OpenCrisis responsibilities…e.g., Site management, members, media (social & other), planning ahead

  • More organised responsibilites – Brendan to lead. Sara to hold the anti-bureaucracy stick.

  • Investigate grant-aid opportunities

  • Translators – write-up and effort to help Info4 etc more easily find translators for their wor.

  • Add “Things you should know about online maps” section to GIS how-to guides. (any other ‘how-to’s in pipeline…needed?

  • Drones – add page, start connecting with drone deployers (Joseph/Sara).

  • Representation; Look at where OpenCrisis should be represented at community conferences, events over next year

  • Hilary – blog post on potential of crowdmapping of poaching and illegal game hunting in wildlife reserves

Monitoring and Evaluation for Digital Humanitarian Response – A Novel Function


By: Lillian Pierson

I’ve recently been tasked with building and managing a Monitoring and Evaluation Team for an organization within the digital humanitarian response community. Although after-action reports have been created by many groups since at least 2010, Monitoring and Evaluation is a relatively novel and absolutely vital function in the digital humanitarian response space. We need to be monitoring and evaluating how our work-products are performing on the ground, so that we can optimize our workflows and increase the effectiveness of our products. In digital humanitarian response, the main goal is for us to provide timely and accurate information to field humanitarians (or affected populations) who are responding to save lives or aid crisis-affected communities in an emergency situation on-the-ground. Within this core function, we must also work to ensure that any of the information we release adheres to the “do no harm principle”.

To monitor and evaluate the effectiveness of our workflows and product utilization, we must start by taking a broad view of the humanitarian response ecosystem and probe to discover our relative position in that ecosystem. To get a visual idea, please see the infographic posted below. We need to ask questions about on-the-ground information product usage (by field response organizations), information product utilization and tracking (by other digital humanitarian response organizations), information product monitoring (i.e.; quality assurance, quality control), and M&E team function and efficiency (a project management and implementation task).

Beyond asking the right questions and evaluating responses, as part of building an M&E team, I have also researched categorical functions of sub-teams within a typical monitoring and evaluation implementation. As stated above, M&E is a novel function in the digital humanitarian space, and the technical nature of digital humanitarian response cannot be omitted from consideration when building a team. Borrowing from and adapting UNDP’s Handbook on Monitoring and Evaluation for Results, my initial recommendation is that an M&E Team in digital humanitarian response should have the following 4 functional groups:

  • Outcome Monitoring Team (An Implementation Role)
  • Outcome Evaluation Team (An Implementation Role)
  • Partner Engagement Team  (An Implementation Role)
  • Monitoring Tools and Mechanisms (A Technical Team – Research and Development Role)

And from there moving forward, I have formulated a basic set of questions, the answers to which could be assessed to form some basic plans about how an M&E Team might best operate within the disaster response framework.

Continue reading

Issues in Mapping Sexual Violence and Hate Crimes


Last year, I published an article discussing the challenges to Documenting Rape in Africa [full text unedited draft here] which continue to hamper effective prevention efforts across the continent and internationally. In this general review, informed heavily by Caroline Muthoni Muriithi the Sexual Violence and Trafficking program officer at Equality Now in Nairobi, constraints on effective programming such as lack of reliable data on actual occurrences due to a complexity of social factors that inhibit reporting  were identified. This discussion is not new, what is however are the many innovative and dynamic applications to track sexual violence and hate-motivated crimes through social media and collaborative mapping such as the Women Under Siege project, HarassMap, and Bachao. These and other efforts have increasingly been utilized by advocates seeking to strengthen the base of evidence available to practitioners. Which can be particularly useful in countries or regions where weak or ineffective public institutions lack quality assurance in data informatics. However, recent discussion on this site and iRevolution on the public availability and ownership of such data particularly in situations of limited statehood raise important questions for ongoing efforts to document these abuses.

As an example, the Being LGBT in Asia project is a crowdsourced instance that seeks to map the ‘Successes and Barriers to LGBT Rights in Asia’. This Ushahidi-based map tracks a wide diversity of social trends and population indicators across regional outlets, intended to provide an understanding of the challenges faced by Lesbian, Gay, Bisexual and Transgender people in Asia. This joint analysis is being undertaken by grassroots LGBT organizations and community leaders in the region, together with the United Nations Development Program (UNDP) and the United States Agency for International Development (USAID), utilizing a participatory approach to the documentation of legal, social and environmental challenges faced by LGBT persons across civil society institutions.  In the context of such a project, who can be said to “own” this data and what potential conflicts of interest could arise between the international organizations providing technical assistance for the project and agents on the ground mired in the daily battles of this work?

Another map called the Geography of Hate, developed by Dr. Monica Stephens at Humboldt State University, drew data on 150,000 tweets sourced by the DOLLY project out of the University of Kentucky. Heat maps of hate speech were generated after researchers hand-filtered tweets categorizing them as positive, neutral or negative based on a pre-defined rubric. Negative messages were mapped to the county level to protect privacy and actual tweet locations, which highlights an interesting gray area of security concern. By blinding this data, one has effectively “protected” perpetrators of these crimes, an issue also identified in the proposal found here on Praxis’s Mapping Sexual Assault proposal site. This is an area of legal and policy research that is currently being prioritized across gender, public health, judicial and development fields.

The International Lesbian, Gay, Bisexual, Trans and Intersex Association (ILGA) has produced a comparative mapping on the status of sexual and gender minority rights globally. The map covers a range of social, legal and institutional indicators and its dataset provides researchers and advocates with a critical resource while also linking out to timely analysis of current trends across sectors. Such information can be one tool for lobbyist and development workers advocating for change, but organizations and digital activists also need to be careful when publicizing socially mined data that has the potential to be utilized by repressive governments to further human rights violations.

More notable examples of this happening can be found from lessons learned in the Arab Spring also touched upon by Brendan in his post on issues around the use and publication of Crisis Data in the context of South Sudan .  Privacy concerns, which is an echo of security risk concerns faced by Volunteer Technical Communities (VTCs) operating in disaster settings more generally.  A post last November on Anahi Ayala Iaccuci’s Diary of  a Crisis Mapper blog covers this issue drawing on lessons learned in the context of Typhoon Yolanda (Haiyan) in the Philippines.

These experiences raise important issues on the implications on activists working to document sensitive human rights abuses that are sexual in nature or motivated by hate. Who defines a particular form of speech as hateful and what standards are used to support this valuation? Further, what can be done to ensure that data is not captured and then withheld from agents operating on behalf of survivors? As covered by Lillian Pierson in her upcoming post on Monitoring & Evaluation for Digital Humanitarian Response – a Novel Approach, there must be explicit efforts to address the unintended consequences in humanitarian crisis mapping and response to complex human rights and security issues.

In the interest of furthering informed critical dialogue and open debate on mapping sexual violence and hate crimes: interested readers and practitioners are encouraged to submit for the recent LGBTI in Africa: Call for Articles issued by the Pan-African social justice press, Pambazuka News, due February, 21st 2014.

 

Concerning responsible use and publication of crisis data for South Sudan


This blogpost seeks to answer a number of honestly expressed concerns – which have been recently conveyed to us – about possible risks attached to the publication of different kinds of information from the public domain (principally Twitter names, radio stations and event locations) in a data resource doc for South Sudan that Sara-Jayne Terp of OpenCrisis set up before Christmas 2013 and which has since been curated by myself, Brendan O’Hanrahan.

We have examined these concerns in great detail and have sought and received the views of several humanitarian information and media professionals who are either based in South Sudan or were based there until the outbreak of this crisis,

Twitter Lists

We believe that there is a fundamental misapprehension at the heart of the concerns that have been raised about our work, particularly as it relates to Twitter: contrary to those assumptions, South Sudan is not experiencing a (so-called) “Arab Spring” or Iranian “Green Revolution” situation at the minute – rather, it is a minor civil war with ethnic undertones, which is essentially based on two factions jockeying for control of one party at the heart of what is, effectively, a one-party state. I wouldn’t classify anybody on the Twitter list contained within our resource doc as a proper social media activist in the sense one would use this term for other recent political crises: there’s one (very high-profile) rap artist in the diaspora who has strongly identified with one side, but somebody who appears on the BBC, Al Jazeera, etc doesn’t really need his identity protected. Then there are 3-4 people who might be categorised as peace activists – but while in some countries this might leave them vulnerable to persecution of some kind, there has been absolutely zero evidence of this for South Sudan. Indeed, if anything, my analysis would be that the peace activists have been more aligned with the status quo than against it – with more of their efforts focused on getting the rebels to abandon their rebellion…and being critical of the UN in a way that sometimes echoes regime criticism.

Twitter does not exist in some grey samizdat-style space; thanks to Twitter lists (not to mention blogposts like Lesley Anne Warner’s), anybody who wants to get hold of prominent Twitter accounts relating to South Sudan can do so in seconds.  To illustrate, here’s a table of the most well-known Twitter lists for (or including) South Sudan.

List Name No. of a/cs Owner
Sudan/South Sudan 69 Gintare Eidimtaite
South Sudan 12 Quinn MacDonald
South Sudan 19 Rachael Akidi
South Sudan 39 Alun McDonald
South Sudan 26 Veronica Ledesma
South Sudan 72 Gabriela Jacomella
South Sudan 87 Geoffrey York
South Sudan 273 Brendan O’Hanrahan
South Sudan 24 Daniel Stuckey
southsudan 81 Clemens Lerche
SS 11 AbdulRahman
Sudans 90 Robyn Dixon
South Sudan 27 Paul Brown
Sudans 125 Lauren P Blanchard
SouthSudanCrisis 100 Carlo Pisani
Sudanese 169 John Fenning
South Sudan 47 Ben Byerly
R.O.S.S. Related 100 Christine Elizabeth
south sudan 55 Hosanna Fox
South Sudan 75 U.S. Mission in Juba
South Sudan 30 Akshaya Kumar
Sudan/South Sudan 164 Teresa Reiter
SouthSudan 41 Anna Bagadi
both sudans 142 sonjasugira

And, in the interests of shining more light about what sort of people actually populated the resource doc’s Twitter list, I extracted the following summary breakdown

South Sudanese citizens No. in (or mainly in) South Sudan Diaspora Journalists/news outlets Analysts Humanitarian or UN
21 12 11 23 11 4

One minor point to highlight here is that the resource doc’s Twitter page has very few full names (this is simply because it was abandoned as a continuing project – because it was felt that public Twitter lists did the same job pretty much as adequately) – and those few nearly all relate to journalists and analysts. Though considering how conspicuous anybody on that list is, I really don’t see a problem with putting their full names there. It would save some evil mukhabarat-style agent 15 minutes of due diligence at most. A media and social media specialist normally based in South Sudan and with extensive experience of social media dynamics in East Africa concurred with our view that there were no vulnerable activists on this list.

Radio Station Lists

I am aware that radio stations (as well as several other kinds of media outlets) have been targeted in South Sudan – there is absolutely no question that South Sudan has become an increasingly hostile environment for journalists to work in over the last 18 months – see the many examples detailed on CPJ’s South Sudan page. However, again, I really, really doubt whether any of the information provided in our document would be necessary for any media suppression goons to do their job. From the government side all radio stations are licensed – so they have that information already…and from the rebel side, it does not make a plausible scenario that they would use our information to potentially target any radio operations when they have local knowledge already at hand. It should also be mentioned that there is already a detailed map of radio stations for South Sudan.

It’s important to stress that we deliberately did not keep any notes as to stations’ political alignment nor are any details about names of those working for them or their actual addresses given.

We have spoken to professionals working in the media development and humanitarian information spheres for South Sudan (two present in-country) – showing them the resource doc, and they have said that as long as no names or detailed addresses were published they saw no problems, since such information is widely available, or the radio stations are well known in their local areas.

Placenames and associated information

The source of over 50% of the named locations (and all of the IDP locations) in this doc is the body of humanitarian updates issued, principally, by OCHA, as well as IOM and USAID. See e.g., this and this, so any condemnation of this ‘loose’ information policy is effectively extended to them. 95% of the remainder of the locations in the placenames and coordinates sheet originate in news reports, or from Twitter updates from trusted journalists  – and the vast majority appeared in several different news sources. Many of the placenames first mentioned in news reports subsequently appeared in the maps of violent incidents produced by USAID, e.g. this one for 27 January. The remainder are either from otherwise researched and credible sources or are included for assistance in geographical orientation.

While there is no direct verification protocol, only reports from trusted sources have been included  (and since I have been following this crisis from close to the beginning in daily detail and been in dialogue with journalists and analysts who know the situation intimately, I think I am relatively qualified to make judgements as to who is trusted and who isn’t) – and if there was still some doubt attached to them, this is mentioned in the notes column. There were no attempts to categorise or otherwise analyse the events mentioned. This is because while it was thought that there would be organised attempts to map the violence and the humanitarian crisis, in practice the only non-OCHA, IOM, Enough Project or USAID mapping initiative was an abortive one, which was suspended after 2-3 days close to Christmas.  The purpose of the placename map therefore evolved to be a resource for either any media people who might seek to know where particular places were, or as the basis for assisting humanitarian mapping projects. One example of this were the maps I produced to help HOT in their identification of some of the priority areas for their South Sudan volunteer mapping response (in support of UNITAR/UNOSAT). It was never, and this is important to stress, intended as the basis for an event map or a violence map – the notes on what put that place “in the news” were just intended for context.

Which brings us to the specific claims that the mentioning of these places brought inherent danger with it to any people staying at those locations. The claim about people being put in danger because the location of a refugee camp is given doesn’t really withstand proper scrutiny – these refugee camps are BIG.  All of them with the exception of those at Minkamman and the UNMISS compounds are existing entities which are extensively documented (and mapped – see especially UNITAR’s collection of maps for South Sudan here) all over the Internet,  and it simply wouldn’t be possible to come into an area and talk to local people without becoming aware of them. The new ones have also been extensively publicised and mapped elsewhere (again, especially via UNITAR). Neither does it make any sense that mentioning e.g., a village which has been raided would make that village vulnerable to another attack in some way.

We spoke to a prominent humanitarian information officer in South Sudan and they said that they had seen no problem in mapping IDP locations and expressed no concern about mapping other locations included in the database.

We have honestly tried to conceive of (realistic!) scenarios whereby some bad actors would use this document to plan or inform their malfeasance, but we honestly couldn’t find any that belonged in the realm of commonsense.

Circulation

We have only recently put this up on the OpenCrisis site (although frankly you wouldn’t find it unless you knew to look for it), and the version there is published without any notes on the events associated with the placenames (though this is mainly because the metadocumentation of my agonising about where difficult-to-find places might be was considered to be probably rather tedious to casual visitors) and apart from the mention on Twitter of this version of the doc, it has otherwise had no circulation except to those involved directly in crisis mapping or media coverage of the crisis (e.g., OCHA in South Sudan, BBC, a couple of freelance journalists, MapAction, HOT). But, again we in OpenCrisis would like to stress that we see no a priori reason why individuals with legitimate interest in events in South Sudan should have less right to this information than those with organisational credentials. We believe in open data – while absolutely taking all due care that no harm is done – and by making these data available we hope to make a contribution, however small, to the deeper understanding and analysis of the complex recent events in South Sudan.

Which brings us on to the final and most important point – whether we have been sloppy in observing humanitarian criteria and being mindful of the safety of those who may be affected by the information in our document.

As the guidelines on the first page of the resource doc state – the overriding principle is to “do no harm”; and although it originally said “don’t identify people in-country,” it was felt that this was better and more practically phrased as “don’t give any details about people which may result in they (or their relations) being put at risk,” while maintaining the crucial first principle. Thus, we are extremely confident that nobody in any danger has been identified, i.e., all those named here are prominent on Twitter already (two possible exceptions are completely apolitical) and no personal information has been attached to either mappable data or radio station details. And, while verification of events associated with placenames has been limited to ensuring that only reports from trusted sources (e.g., OCHA, USAID, Radio Tamazuj, Gurtong Trust etc.) are noted, we feel that this has been to an appropriate level in view of the degree of risk attached to the publication of these names. We should have had a note explaining this for the document before, but we have now rectified this by adding such a clarification to the first page.

So, while acknowledging that it will not always be easy to reconcile the twin aims of making useful crisis data widely available and ensuring that no risk is thereby entailed, we honestly think that, at least for this project, we have managed to achieve a sensible balance.

Who Owns Crisis Data?


N.B. After investigating the compaint in detail (see this blogpost), we re-opened the resource doc containing the dataset discussed below later on 09 Feb.

This is one of several posts going up as a result of OpenCrisis investigations into a complaint about one of its datasets.  This post will concentrate on the ownership aspects of that complaint.

Please note that this is currently a ‘holding’ blogpost, so people affected can be updated on what’s happening (sadly, all work on this much-used dataset has ceased until we get this all straightened out) – we’ll be adding to it as we have time (we’re concentrating more on making sure the dataset isn’t breaking its stated objective of “first, do no harm”) and as we learn more about this important issue.

Some background:  starting late last year, OpenCrisis began assembling a dataset (South Sudan humanitarian data, geodatasets, Twitter, etc) for its own work, that it then shared with another group (lets call them “LovelyPeople’) that was collecting information for a journalism group (let’s call them ‘Z’) – this second collection was deemed sensitive by ‘Z’, so we carefully left their deployment off our list of groups working on this crisis (for the record, we do this a lot, and will continue to do it for anyone who asks us to).  OpenCrisis made some of its original data (anything considered sensitive was kept private) available to people working in South Sudan via a publicly-visible but not widely-advertised spreadsheet.

Unfortunately,  5 Twitter names  made their way  from ‘Z’s sheet into the new spreadsheet, and ‘Z’ or one of its representatives (it’s unclear which) is now threatening to sue two individuals in OpenCrisis for the reuse of ‘their’ data.  To put this in perspective, the contribution from OpenCrisis to ‘Z’ was roughly 20+ Facebook addresses, 20 blog addresses, 60 multimedia records,  virtually all the local media outlets cited by ‘Z’, virtually all the Twitter lists listed by ‘Z’, 50-70 Twitter names and a direct copy (credited) of the OpenCrisis crisis mapping page as it was at the time.  This is all made more confusing because a third group, LovelyPeople, were also involved, and the OpenCrisis member concerned (Brendan O’Hanrahan) believed that the work with LovelyPeople was on the basis of mutual benefit, because that was stated when he joined the project.

Just to be clear on the OpenCrisis position on this dataset: ‘Z’s specific problem appears to be with the list of Twitter users. There are many many Twitter lists containing the data in question now – so much so that OpenCrisis stopped updating their spreadsheet list back in January – and we have no problems with removing any content that we can’t prove is our own. 

But we don’t want to live in a world where data ownership and worrying about being sued is a concern for every mapper trying to improve the world.  We might get sued, but this isn’t about us.  The much more important thing is resolving (or starting to resolve) the issue of data ownership when that data has been generated collectively by multiple individuals and groups.

So, who owns crisis data?

The heart of this problem is ownership of community-generated data.  I have much reading and thinking to do before I can start to answer this question, but the use of agreements (even if it’s agreement that all data will be shared across the community) appears to be key.

The legal position in the US appears to be clear: “It is important to remember that even if a database or compilation is arranged with sufficient originality to qualify for copyright protection, the facts and data within that database are still in the public domain. Anyone can take those facts and reuse or republish them, as long as that person arranges them in a new way” (Uni of Michigan’s exceptions to copyrights page).  That’s actually a huge relief, because if verified (and IANAL), the constant work that we all do on existing crisis datasets will help us to keep them free to use.

So the issue now appears to be less of a legal one, and more of a moral and ethical one: when is it right to share data between groups, and when is it right to claim ownership?

Data Licences

Although ‘ownership’ of data for good is anathema to us, there is one reason why it can be good: reducing confusion about who can use what where, via licensing.  We often need to say that the data we produce can be used by anyone, and say it legally and publically, and that’s what open data licences do.  Fortunately, there are some good “you can go use this” licences out there (e.g. ODbL), but as OSM et al know from painful experience, picking the right data licence to be compatible with other people’s data gathering and use can be hard.

Privacy

The privacy of individuals is extremely important in our community.  When we were working through another issue raised by ‘Z’, we considered locking down the spreadsheet to subscribers only – only to realise that that would mean making a list of people (and emails of people) engaged in this work.  Which we’d also have to protect.  We’re still thinking about that one.

Legal protection

We can’t stress this enough: if you’re running a crisis data group, then seriously consider creating a nonprofit company for it. We hate having hierarchies and official registrations too, but without the protection of being an NJ non-profit, those two individuals (and all that they and their family own) would be at risk instead of this being an organisation-to-organisation thing. We’ve started an OpenCrisis page, who owns crisis data, for links and discussion on the ownership issue.  We’d love contributions of useful links and analysis for it.

Verification Handbook Review


The European Centre of Journalism’s Verification Handbook [1] was released online at http://verificationhandbook.com this week, with PDF, Kindle and Print versions to be released on 7 February, and an Arabic version soon after that.

The handbook discusses the processes of verifying user-generated content (e.g. pictures or information gathered from social media accounts in emergencies). It’s targeted at emergency journalists and aid workers, but is also a great resource for anyone wanting to learn the modus operandi of verification: it covers the basics of verification, is filled with lessons learned and examples, and can assist the reader in creating a verification checklist.

The length is short, the contents are to-the-point, and the collaborators have covered various topics related to authentication of user generated content through the entirety of of the verification process in an attempt to help the reader determine the best possible way to answer the age-old question: “How do you know that?”

The handbook cites lessons learned, in-field experience, and analysis of past emergent events.  Events cited include the violence in Jos, Nigeria in 2010, London’s July 7 Bombings in 2005, the Ukrainian Parliamentary Elections in 2012, and the Boston Marathon Bombings in 2013.  Studies directly referenced were Harkin 2012 on Syria [2], and Castillo 2012 on Predicting Information Credibility [3].

The Verification Handbook is expected by the European Centre of Journalism to have a significant impact on emergency journalism and aid workers.

References

OpenCrisis Townhall Meeting 23rd January 2014


What’s This?

Meeting: OpenCrisis TownHall

Date: 23rd January 2014

Agenda: a roundup of what we’ve been doing and deployments we’ve heard about in the past month; a check on what groups and people needed; and a vague plan for the coming month.

Last month: 20 December 2014 minutes

What’s Happened?

Past month: Deployments

 

  • What: South Sudan crisis

    • who:  HOT OSM, GISCorps, Ushahidi, OpenCrisis (unofficially)

    • where:  South Sudan

    • what:  OpenCrisis set up coordination skypechat and googledoc (http://bit.ly/1f9C457) for groups mapping the South Sudan crisis. HOT OSM has mapped several affected areas, in collaboration with UNITAR/UNOSAT, HIU (State Dept)  with assistance from GIScorps and, for area identification, OpenCrisis (BOH). Info4Disasters helped Internews develop an inventory and overview of local media and social media. Ushahidi set up southsudanwatch.ushahidi.com, but this initiative was stopped almost immediately after Christmas (possibly because of security concerns? – BOH). DHN call went out later for mapping in South Sudan  (to be carried out later in the year?) – Joseph shared the OpenCrisis googledoc with SBTF, to avoid duplication of effort.

    • Deployment dates:  24th December – continuing (contact Brendan or Sara)

 

  • What: Central African Republic crisis

    • who:  HOT OSM

    • where:  CAR

    • what:  HOT has been doing a lot of mapping – both settlements and infrastructure, since the crisis began

    • Deployment dates:  HOT has been active for CAR/RCA for over a year, but this activity has intensified since mid-late December 2013

 

  • Events with monitoring but not deployments:

    • USA cold.

    • Kyiv (Kiev) demonstrations – concern and willingness to map seen online, but no deployments as yet.

 

Past month: Activities

 

  • OpenGoodHacks

    • who: RHOK, Geeklist, Pat, Sara

    • what: Helped RHOK, Geeklist etc.with naming and creating a central neutral space for listing hackathons for good. Thea Clay is spearheading.

    • where: online

    • when: 22nd January 2014

 

  • Accademics

    • who: Joseph

    • what: Creating discussions spaces for academics in crisismapping (to discuss grant opportunities, create online course etc) and the SBTF (to improve SBTF training). The idea with Accademics is to enlarge the group by posting on the crisismappers googlegroup, and to create courses that we can offer credits for – together, creating joint courses; creating research consortiums and getting ideas flowing between top researchers.

    • where: online

    • when: January 2014 – continuing

 

Other activities:

  • Info4 and SBTF have partnered – Info4 will be the provider of ET/HR activities to SBTF.

  • OpenCrisis incorporation: OpenCrisis is now incorporated as a nonprofit in New Jersey, USA.  Thanks to everyone who helped make this happen.

  • OpenCrisis platforms: Long discussions about platform choices, all of which included some form of WordPress site. OpenCrisis.org is being migrated to a wordpress site, to give more community members an easy way to contribute writings about crisismapping.  The original Drupal site remains at opencrisis.com and opencrisis.net; other platform choices remain (but are wider now that OC is incorporated, e.g. we can ask Confluence for a wiki like wiki.ushahidi.com).

  • OpenCrisis calendar http://opencrisis.org/calendar/ created – this is for the entire crisis mapping community – not just OpenCrisis. Anybody who participates in the OpenCrisis discussion space can (or should be able to..if not, ping Brendan) enter events on it.

News, Announcements etc

AOB

  • Next TownHall meeting: 14th February 2014.   TownHalls are on the second Friday of every month (formerly Wednesdays), at 12pm EST / 5pm GMT unless otherwise stated.  Townhalls for 2014 are: 17th January, 14th February, 14th March, 11th April, 9th May, 13th June, 11th July, 8th August, 12th September, 10th October, 14th November, 12th December.

  • GDELT, the conflict data warehouse, has closed. This is a massive loss to our community (it’s a legal fight about ownership between the GDELT team and uni). And something we should fight to stop happening across the rest of our domain. If we have data, we should work on open licenses for it. GDELT, the huge datastore of everything conflict related, has closed. Apparently conflict between those who ran it and the university that was hosting it, and lending its datastore (may be significantly more complicated than that, judging from legal files associated with this fight…). NB recent new standard on data licenses just came out.

  • Andy Gimma has started digital humanitarian tools training in new york – first session is 25th january 2014 – https://www.facebook.com/events/569211419828560/

  • DHN meetup in Boston on 25th january 2014 too. https://www.eventbrite.com/e/dhnetwork-meetup-boston-tickets-9936047987?utm_campaign=order_confirm&ref=eemailordconf&utm_medium=email&utm_source=eb_email&utm_term=eventname

  • CDAC network report on SMEM is out: http://www.cdacnetwork.org/public/resource/101-seminar-report-social-media-emergencies

  • The Global Disaster Alert and Coordination System (GDACS) is now providing an additional service: Overview of ongoing satellite mapping events.This service provides a short overview of the identified ongoing satellite mapping activities related to humanitarian disasters. It is intended for disaster managers, operations centres, desk officers and others that need syntheses of what goes on in this field. The service is operated by the GDACS mapping & satellite imagery coordination mechanism: UNITAR Operational Satellite Applications Programme (UNOSAT). See http://portal.gdacs.org/Portals/1/GDACS_SatMapOverview_01_4Jan2014.pdf

 

What do we need to do?

Last month’s plan

  • Sara to make list of all the people and groups who email her about crisismapping (ongoing)

  • Platform discussion (DONE)

  • Incorporation discussion (DONE)

Needs

  • Blogposts for the new website – please write them!

 

Next month’s plan

  • Create agenda for next month (use template)

  • Sara to make list of all the people and groups who email her about crisismapping

  • Launch new opencrisis.org site on Saturday 25th January… continue to populate this, and explore complementary platform options.

  • Sara – write a page about open data licenses and how to do them right

  • Lillian to write blogpost about the maze of finding open data in Thailand

  • Brendan writing blogpost about ‘Geolocation in context’

  • Rose – summary of verification handbook? Verification Handbook with guidelines to verify digital, user generated content.  Will have guidelines, tools, checklist, etc. Supposed to be released January 2014 (sometime this month), freely available.  Will write summary (REM)

  • Sara – post about open data cambodia (but only with permission from team)

  • Sara – run training session on open data.

Crisismapping Meetups Jan-Feb 2014


This weekend is going to be a busy one for in-person crisismapping events: Digital Humanitarian Training is launching its first meetup in New York, and the Digital Humanitarian Network is running its first in-person meeting in Boston USA (they’re both on our shiny new crisismapping calendar).

As someone who dedicated years to helping crisiscamps around the world and the CrisismappersNYC meetup (spawned from the CrisisCampNY meetups), this makes me both nostalgic and hopeful at the same time.

I’m nostalgic because even the most collaborative groups like CrisisCamp London & Crisismappers NYC are difficult to keep going from a distance (e.g. if you find yourself working 3500 miles from London or even 50 from NYC). Though distance may be short on the map, no amount of tech can fit the enormous gap of quality in meeting-people time. Keeping people engaged in training on crisis mapping, connecting them to other mappers in different cities and handling logistics is a lot for any one person to shoulder. Indeed, the planning, staffing & training work required at an event speak nothing of the ground work involved in identifying venues or maintaining networks and individual connections.

And I’m hopeful to see the next generation of crisismapper meetup organisers come through.  They’ll learn, like we did, about the things that do and don’t work, and hopefully will find some of the things we left behind for them, like the Crisiscamp-in-a-box packs describing everything from what stationery is good to have (post-it notes are always useful) to how to organise training (backstory: Crisiscamp London had a real cardboard box that they stored all their stuff in between meetings).   But hopefully, unlike many of us old ‘uns, they won’t burn out trying to train and map and organise meets all at the same time.

I wish you both luck, Andy and Willow – and if you ever want to drink a pint and talk about all the things that did and didn’t work in the past, I’ll see you sometime in New York!

Sara.