https://wiki.responsibledata.io/api.php?action=feedcontributions&user=Rdfwikiperson&feedformat=atomResponsible Data Wiki - User contributions [en]2024-03-28T10:58:26ZUser contributionsMediaWiki 1.23.4https://wiki.responsibledata.io/Main_PageMain Page2014-10-06T18:53:00Z<p>Rdfwikiperson: Blanked the page</p>
<hr />
<div></div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-04T18:10:29Z<p>Rdfwikiperson: /* Farmer's Market Resources Lists */</p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
We will spend the next week collecting and posting resources and notes here in this wiki. Subscribe to our [http://lists.theengineroom.org/lists/info/rdfupdates RDF updates email list] to be updated when this wiki is ready!<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
<br />
Hashtags: RDFbuda and responsibledata<br />
<br />
Twitter links: [https://twitter.com/engnroom @engnroom] and [https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Document capturing ==<br />
<br />
[[The agenda wall]] - Lists of questions and topics that came from the event participants<br />
<br />
== Product outputs ==<br />
<br />
[[Primer on responsible data in development]] ''(Information currently being collected)''<br />
<br />
[[Responsible Data Risk Mapping]] - Categorizing harm levels on knowledge assets to inform mitigation and protection <br />
<br />
[[Atomized security plans for organizations]] ''(Information currently being collected)''<br />
<br />
[[Framework for consent policies]] - When interacting with people, it is important to gain their consent when at all possible. This page gives an overview of a framework for considering what level of consent is needed, what to consider when attempting to gain that consent, what responsibilities accompany consent, and the like. It is to be used for the creation of studies, campaigns, and programs.<br />
<br />
[[Newbie guide to select hosting]] - A guide for small to medium-sized NGOS on choosing a hosting provider for their website <br />
<br />
[[Digital first aid kit]] ''(Information currently being collected)''<br />
<br />
[[Resource creator manifesto]] - Declaration of values and commitments for resource-creators to hold ourselves and each other accountable to our stakeholders regarding the protection and preservation of resources developed from and for these stakeholders. <br />
<br />
[[Feeding empirical data into policy making]] - List of moments in policy process in which we can engage <br />
<br />
[[Practical de-identification guide]] - The Basic De-identification Solution Matrix is an editable Google Spreadsheet that list common variable types from the fields of health, education, finance, environmental, political, a list of de-identification solutions for these types of data, and some suggestions about what forms of de-identification are most useful for each type of data. <br />
<br />
[[Data in the project lifecycle]] - A lightweight tool for data project implementers to help plan their projects and check whether they are being responsible with their data at every step, both for planned and emerging risks.<br />
<br />
== Farmer's Market Resources Lists == <br />
<br />
Below are lists of resources collaboratively created by the RDF participants:<br />
<br />
*[[Responsible data checklists: existing and wishing existed]]<br />
<br />
*[[orgs working on responsible data]]<br />
<br />
*Responsible data [[policies]]: existing and wishing existed<br />
<br />
*Responsible data [[communities of practice]]<br />
<br />
*[[Voices already talking about responsible data]]<br />
<br />
*Responsible data [[wishlist]] ''(Information currently being collected)''<br />
<br />
*[[Upcoming events that should include responsible data]] ''(Information currently being collected)''<br />
<br />
*Responsible data [[harm stories]] ''(Information currently being collected)''<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]] the RDF outputs - Ideas for how we can package these RDF outputs for further collaboration and testing. <br />
<br />
[[Talking about harm]] - A visualization of a discussion on how to talk about harm responsibly.<br />
<br />
[[Collaboration software alternatives]] - Google Drive is not the only option!<br />
<br />
[[Video and photo evidence]] ''(Information currently being collected)''<br />
<br />
[[Responsible and/or open data]] - A visualization of the relationship between responsible and open data.<br />
<br />
[[Why should my NGO care about responsible data]] - A definition of 'responsible data' and incentives (carrots and sticks) for NGOs to care about it.<br />
<br />
[[Spreading the word]] ''(Information currently being collected)''<br />
<br />
=== Round 2 ===<br />
<br />
[[Frameworks for data sharing]] - Mapping out a possible decision tree for quite a specific scenario: where an NGO is approached with a request to use their data (still a work in progress).<br />
<br />
[[Piloting plan]] - Notes from a discussion on how we test the usefulness of the tools being developed in the Responsible Data Forum.<br />
<br />
[[Responsible Data campaign]] ''(Information currently being collected)''<br />
<br />
[[Responsible visualization]] ''(Information currently being collected)''<br />
<br />
[[Code of ethics in sex exploitation]] - Brief summary of a discussion on how to respond to sex exploitation in solidarity, not paternalism.<br />
<br />
[[Responsible Data survey]] ''(Information currently being collected)''<br />
<br />
[[Human Rights documentation]] ''(Information currently being collected)''<br />
<br />
[[White paper on responsilble data standards]] ''(Information currently being collected)''</div>Rdfwikipersonhttps://wiki.responsibledata.io/Communities_of_practiceCommunities of practice2014-10-04T17:59:06Z<p>Rdfwikiperson: </p>
<hr />
<div>{| class="wikitable"<br />
! style="font-weight: bold;" | Who<br />
! style="font-weight: bold;" | Why<br />
! style="font-weight: bold;" | Where<br />
! style="font-weight: bold;" | How<br />
|-<br />
| grow and build community of people experiencing violence<br />
police<br />
journalists<br />
courtrooms<br />
gynaecologists<br />
community leaders - religion<br />
| each community needs to be accountable to make its space safe for womena n individuals across gender spectrum<br />
| private sector<br />
| use data to develop solutions<br />
|-<br />
| education communities<br />
| to integrate responsible data practices and ethics right from the start: at education<br />
| universities/schools<br />
| connect to most relevant orgs (eg: journalist studies, international development) and teachers<br />
|-<br />
| peace and collaborative data network (PCDN)<br />
| check their website for online discussion forum PCDN<br />
| x<br />
| x<br />
|-<br />
| Journalists<br />
| they collect and publish data<br />
| personally! Online!<br />
| invite them!<br />
|-<br />
| aid workers (especially health aid)<br />
| they are only starting to scale up on tech - let's help them learn our lessons!<br />
| aid places etc<br />
| invite them! + speak to their engaged plantforms<br />
|-<br />
| humanitarian/academic researchers<br />
| most don't know about digital/ holistic security tools and tactics<br />
| everywhere, humanitarian crisis response<br />
| holistic security training (digital/ physical/psychosocial)<br />
|-<br />
| (data) journalists<br />
| x<br />
| DDJ mailinglist<br />
ICFJ <br />
GIJN<br />
| x<br />
|-<br />
| users! (radical, but hey…)<br />
| because they are data subjects and owners, not data objects<br />
| at the bottom of every project, platform, service, benefit, government, etc…<br />
| meanginfullly, respecting agency, recognizing when it doesn't exist, sensitively, with legal,policy defaults, best practices, dialogue…<br />
|-<br />
| Our media network<br />
IAMCR<br />
community communization sector<br />
| to connect with researchers<br />
| online lists - reach individuals who might be interested<br />
| x<br />
|-<br />
| citizen scientists, journalists, researchers<br />
| some citizen scientists are mapping politically sensitive env. Data without,necessarily being aware of the data collection context/ possible consequences<br />
| through existing cit sci umbrella organisations and individually curated projects eg,excites @ ULL<br />
| provide online training through the organisaers of the research<br />
|-<br />
| public labs<br />
| x<br />
| PL: Distributed, Cambridge MA<br />
| x<br />
|-<br />
| NGOs doing data driven campaigns<br />
| they use and collect data/ not very tech savvy, not aware of risks<br />
| x<br />
| x<br />
|-<br />
| Anti-corruption activists collecting info/complaints on corruption cases<br />
| collection of sensitive info on corruption without sometimes protecting,civtims/complainants enough<br />
| in countries (over 60) with advocacy + legal advice (transparency international)<br />
| -help spreading good methods / tools to collect data safely<br />
-sharing good practice of other documentations efforts<br />
|-<br />
| government!!<br />
| inform them for better policies/legislation<br />
| x<br />
| x<br />
|-<br />
| grant giving organisations<br />
| collecting a lot of (sometimes) highly sensitive data through the grant giving process<br />
| x<br />
| x<br />
|-<br />
| datakind (chapters, orgs, and volunteers)<br />
| force multiplier at more events and more organisations more often<br />
| online, anywhere, Bangalore, DC, NYC, SF, Dublin, UK, Singapore<br />
| Models developed at RDFs easy to use in events<br />
|-<br />
| Local Bloggers (city/municipality level)<br />
| they work with data to improve local communities without sometimes knowing they do,it and it is to make it better<br />
| x<br />
| x<br />
|-<br />
| School of Data trainers and fellows<br />
| they train data skills to journalists, CSOs and citizens<br />
| @ school of data<br />
| x<br />
|-<br />
| W3C<br />
| they work with standards on the web!<br />
| W3C's website!<br />
| online and local events<br />
|-<br />
| designers<br />
| help visualize data (make data accessible)<br />
| x<br />
| x<br />
|-<br />
| creatives of different kinds: graffiti artists/ film makers, etc<br />
| they have new "out of the box" ideas of data dissemination<br />
| creative hubs<br />
| open grants for them to work with data<br />
|-<br />
| NETHOPE<br />
| they represent IT teams across development orgs. Not very political but would be a,good way to reach out to more orgs in humanitarian/ disaster relief<br />
| based in DC<br />
| pose workshops @ conferences, reach out to the board, personal outreach<br />
|-<br />
| ALNAP<br />
| x<br />
| x<br />
| x<br />
|-<br />
| Survivors<br />
| to provide them with legal, medical, psychological support<br />
| in public sphere<br />
| through an online platform to report<br />
|-<br />
| European Coordination Comm. On Human Rights Documentation<br />
| 20+ years of experience with human rights<br />
| Europe<br />
| yearly meeting<br />
|-<br />
| Geographers Mappers<br />
| we just need to connect the issues with location/ jurisdiction + to see connections in terms of area affected<br />
| Universities<br />
Open Street Mappers<br />
local Oral History Clubs<br />
| join the club!<br />
|}</div>Rdfwikipersonhttps://wiki.responsibledata.io/Communities_of_practiceCommunities of practice2014-10-04T17:58:37Z<p>Rdfwikiperson: </p>
<hr />
<div>{| class="wikitable"<br />
! Who are they<br />
! What are they writing about<br />
! Where to find them<br />
|-<br />
| Maya Ganesh<br />
| Women's rights, privacy, dicital security, advocacy, storytelling<br />
| Tactical Technology Collective<br />
|-<br />
| GENDERLOG<br />
| gender rights/issues, violence against women<br />
| @genderlog and facebook<br />
|-<br />
| @pinthecreep (safecity.in)<br />
| gender based violence in India<br />
| @pinthecreep fb - safeciy.in<br />
|-<br />
| Carey Shenkman<br />
| Digital security training for human rights lawyers<br />
| Center for Constitutional Rights<br />
|-<br />
| Adam Harvey<br />
| Artist on anti-surveillance issues<br />
| Privacy Gif Shop; Undisclosed, Inc.<br />
|-<br />
| x<br />
| Dutch Researcher on use of data for immigration control (Dutch book title: "De Migratiemachine")<br />
| x<br />
|-<br />
| Rebecca McKinnon<br />
| Ranking Digital Rights Project<br />
| New Am. Foundation<br />
|-<br />
| Duncan Green from Poverty 2 Power (Oxfam)<br />
| Everything development<br />
| Blog, twitter<br />
|-<br />
| Fearless Colective<br />
| using art to raise GBV/VAW Issues<br />
| fb- fearless collective<br />
|-<br />
| Heather Leson<br />
| thinking data, ethics/ open, humanitarian<br />
| internet, OKFN<br />
|-<br />
| Marko Rakar<br />
| blogger, lots of diff. data proj.<br />
| Croatia<br />
|-<br />
| Association for Progressive Communication (APC)<br />
| feminist approach to VAW online<br />
| Based in South Africa<br />
|-<br />
| Fabiano Angelico<br />
| transparency research in Brazil<br />
| Twitter and facebook (slideshow)<br />
|-<br />
| Evgeny Morozov<br />
| the anti-christ of sylicon valley (author)<br />
| twitter, online talks, columns, website, DuckDuckGo him<br />
|-<br />
| Lucy Bernholz<br />
| x<br />
| x<br />
|}</div>Rdfwikipersonhttps://wiki.responsibledata.io/Voices_already_talking_about_responsible_dataVoices already talking about responsible data2014-10-04T17:38:01Z<p>Rdfwikiperson: </p>
<hr />
<div>{| class="wikitable"<br />
! style="font-weight: bold;" | Who are they<br />
! style="font-weight: bold;" | What are they writing about<br />
! style="font-weight: bold;" | Where to find them<br />
|-<br />
| Maya Ganesh<br />
| Women's rights, privacy, dicital security, advocacy, storytelling<br />
| Tactical Technology Collective<br />
|-<br />
| GENDERLOG<br />
| gender rights/issues, violence against women<br />
| @genderlog and facebook<br />
|-<br />
| @pinthecreep (safecity.in)<br />
| gender based violence in India<br />
| @pinthecreep fb - safeciy.in<br />
|-<br />
| Carey Shenkman<br />
| Digital security training for human rights lawyers<br />
| Center for Constitutional Rights<br />
|-<br />
| Adam Harvey<br />
| Artist on anti-surveillance issues<br />
| Privacy Gif Shop; Undisclosed, Inc.<br />
|-<br />
| x<br />
| Dutch Researcher on use of data for immigration control (Dutch book title: "De Migratiemachine")<br />
| x<br />
|-<br />
| Rebecca McKinnon<br />
| Ranking Digital Rights Project<br />
| New Am. Foundation<br />
|-<br />
| Duncan Green from Poverty 2 Power (Oxfam)<br />
| Everything development<br />
| Blog, twitter<br />
|-<br />
| Fearless Colective<br />
| using art to raise GBV/VAW Issues<br />
| fb- fearless collective<br />
|-<br />
| Heather Leson<br />
| thinking data, ethics/ open, humanitarian<br />
| internet, OKFN<br />
|-<br />
| Marko Rakar<br />
| blogger, lots of diff. data proj.<br />
| Croatia<br />
|-<br />
| Association for Progressive Communication (APC)<br />
| feminist approach to VAW online<br />
| Based in South Africa<br />
|-<br />
| Fabiano Angelico<br />
| transparency research in Brazil<br />
| Twitter and facebook (slideshow)<br />
|-<br />
| Evgeny Morozov<br />
| the anti-christ of sylicon valley (author)<br />
| twitter, online talks, columns, website, DuckDuckGo him<br />
|-<br />
| Lucy Bernholz<br />
| x<br />
| x<br />
|}</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:58:56Z<p>Rdfwikiperson: </p>
<hr />
<div>'''''Categorizing harm levels on knowledge assets to inform mitigation and protection'''''<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
== WTF ==<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
== Process for generating a Responsible Data Risk Map ==<br />
<br />
=== Types of Harm: ===<br />
* Psycho-Social / Emotional<br />
* Physical<br />
* Economic<br />
<br />
=== 1. Identify the Persons at Risk in the event of exposure ===<br />
Definition of Persons at Risk: Any entity at risk of being by the exposure. Therefore, not restricted to the data owner or collector.<br />
<br />
=== 2. Identify Knowledge Assets that can be extracted from the data collected ===<br />
Definition of Knowledge Assets: Discrete data points, information extracted from collections of discrete data points, information extracted from meta analysis of data points, information extracted from the mashup of the collected data and external data sources.<br />
<br />
=== 3. Evaluate the importance of each knowledge asset to the campaign ===<br />
The importance is used in combination with Risk assessment to determine what data to collect.<br />
Importance is rated on this scale:<br />
* Low Importance: knowledge assets that have little or no relevance to the success of the campaign<br />
* High Importance: knowledge assets that have significant relevance to the success of the campaign<br />
* '''Must Have''': knowledge assets that are crucial to the success of the campaign<br />
<br />
=== 4. For each Type of Harm: ===<br />
Evaluate probability and severity of harm for each type of harm for each person at risk by each knowledge asset<br />
<br />
Probability of Harm:<br />
* Low - Assessed as 49% or less probability of harm<br />
* High - Assessed as 50% or more probability of harm<br />
<br />
Severity of Harm<br />
* Low - Assessed as causing little to no harm to the Person at Risk<br />
* High - Assessed as causing moderate to severe harm to the Person at Risk<br />
* '''No Go''' - Assessed as causing catastrophic harm to the Person at Risk<br />
<br />
The output of this process is a high-level score for each Person at Risk, with detailed matrices for each Type of Harm as supporting documentation.<br />
<br />
== RISK PROFILES of data collectors and data owners ==<br />
<br />
# Severe/catastrophic risk: Clear, present, very high probability, direct threat with catastrophic impacts that cannot be mitigated. Severe risks include denial of civic rights, detainment, imprisonment, disabling physical injury, or death.<br />
<br />
# High risk: Clear, present or future, high probability, direct or indirect threat with medium to high impacts. High risks include denigration, exclusion, access to civic rights, psychosocial distress, social stigma, loss of reputation, loss of livelihood, economic deprivation, moderate to severe physical injury with temporary or permanent effects on basic life functions. High risks threats also include organizational infiltration; personal intimidation, persecution, harassment, targeting for rights violations. High risks also include organizational or team breakdown.<br />
<br />
# Low/moderate risk: Clear, present or future, low to medium probability, direct or indirect threat with low to moderate impacts. Risks with low to moderate impacts include verbal aggression, temporary psychosocial distress, temporary economic deprivation, discrediting, or temporary organizational or team breakdown.<br />
<br />
<br />
=== Migitation/Safety planning ===<br />
<br />
Responsible data practices require safety planning. This identifies actions you can take to address threats to data collectors and data owners. Questions that may help formulate your plan include:<br />
<br />
* What risks can be eliminated entirely?<br />
* Which risks can be mitigated?<br />
* Based on their likelihood and significance, which risks should be addressed first?<br />
* How can those risks be mitigated?<br />
<br />
It is assumed that data collectors and data owners will not be able to address all threats at once. They should be prepared to schedule work on risk-of-harm assessment as well as safety planning alongside project design, implementation, monitoring and evaluation activities, and across the data lifecycle. Risk assessment and safety planning should be repeated as changes come about in the project context or population of data collectors or owners. Safety plan implementation should be monitored for needed adjustments to the plan for different profiles of data collectors or data owners.<br />
<br />
=== THINGS TO KEEP IN MIND ===<br />
<br />
Be inclusive in your planning. A practitioner's own or participants' risks may depend on other people's habits. Having confidential discussions about organizational safety policies and practices is important.<br />
<br />
Be judicious with permissions and access to digital data, software or hardware: Does everyone in the office have access to all the data or devices in that office? Should they?<br />
<br />
== Use cases for validation and testing ==<br />
<br />
* '''NAZRA for human rights:''' piloting the mapping tool with their forthcoming data collection process<br />
* '''Zasto Ne:''' testing the tool against election monitoring data<br />
*<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
Darko Brkan, founder, Zasto Ne<br />
<br />
Jennifer Schulte, researcher<br />
<br />
Mahy Hassaan, campaign and ad-hoc coordinator, NAZRA for feminist studies<br />
<br />
Sajjad Anwar, software developer<br />
<br />
Tin Geber, project manager, the engine room<br />
<br />
Zack Halloran, director, Crowdmap<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:55:38Z<p>Rdfwikiperson: </p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
== Process for generating a Responsible Data Risk Map ==<br />
<br />
=== Types of Harm: ===<br />
* Psycho-Social / Emotional<br />
* Physical<br />
* Economic<br />
<br />
=== 1. Identify the Persons at Risk in the event of exposure ===<br />
Definition of Persons at Risk: Any entity at risk of being by the exposure. Therefore, not restricted to the data owner or collector.<br />
<br />
=== 2. Identify Knowledge Assets that can be extracted from the data collected ===<br />
Definition of Knowledge Assets: Discrete data points, information extracted from collections of discrete data points, information extracted from meta analysis of data points, information extracted from the mashup of the collected data and external data sources.<br />
<br />
=== 3. Evaluate the importance of each knowledge asset to the campaign ===<br />
The importance is used in combination with Risk assessment to determine what data to collect.<br />
Importance is rated on this scale:<br />
* Low Importance: knowledge assets that have little or no relevance to the success of the campaign<br />
* High Importance: knowledge assets that have significant relevance to the success of the campaign<br />
* '''Must Have''': knowledge assets that are crucial to the success of the campaign<br />
<br />
=== 4. For each Type of Harm: ===<br />
Evaluate probability and severity of harm for each type of harm for each person at risk by each knowledge asset<br />
<br />
Probability of Harm:<br />
* Low - Assessed as 49% or less probability of harm<br />
* High - Assessed as 50% or more probability of harm<br />
<br />
Severity of Harm<br />
* Low - Assessed as causing little to no harm to the Person at Risk<br />
* High - Assessed as causing moderate to severe harm to the Person at Risk<br />
* '''No Go''' - Assessed as causing catastrophic harm to the Person at Risk<br />
<br />
The output of this process is a high-level score for each Person at Risk, with detailed matrices for each Type of Harm as supporting documentation.<br />
<br />
== RISK PROFILES of data collectors and data owners ==<br />
<br />
# Severe/catastrophic risk: Clear, present, very high probability, direct threat with catastrophic impacts that cannot be mitigated. Severe risks include denial of civic rights, detainment, imprisonment, disabling physical injury, or death.<br />
<br />
# High risk: Clear, present or future, high probability, direct or indirect threat with medium to high impacts. High risks include denigration, exclusion, access to civic rights, psychosocial distress, social stigma, loss of reputation, loss of livelihood, economic deprivation, moderate to severe physical injury with temporary or permanent effects on basic life functions. High risks threats also include organizational infiltration; personal intimidation, persecution, harassment, targeting for rights violations. High risks also include organizational or team breakdown.<br />
<br />
# Low/moderate risk: Clear, present or future, low to medium probability, direct or indirect threat with low to moderate impacts. Risks with low to moderate impacts include verbal aggression, temporary psychosocial distress, temporary economic deprivation, discrediting, or temporary organizational or team breakdown.<br />
<br />
<br />
=== Migitation/Safety planning ===<br />
<br />
Responsible data practices require safety planning. This identifies actions you can take to address threats to data collectors and data owners. Questions that may help formulate your plan include:<br />
<br />
* What risks can be eliminated entirely?<br />
* Which risks can be mitigated?<br />
* Based on their likelihood and significance, which risks should be addressed first?<br />
* How can those risks be mitigated?<br />
<br />
It is assumed that data collectors and data owners will not be able to address all threats at once. They should be prepared to schedule work on risk-of-harm assessment as well as safety planning alongside project design, implementation, monitoring and evaluation activities, and across the data lifecycle. Risk assessment and safety planning should be repeated as changes come about in the project context or population of data collectors or owners. Safety plan implementation should be monitored for needed adjustments to the plan for different profiles of data collectors or data owners.<br />
<br />
=== THINGS TO KEEP IN MIND ===<br />
<br />
Be inclusive in your planning. A practitioner's own or participants' risks may depend on other people's habits. Having confidential discussions about organizational safety policies and practices is important.<br />
<br />
Be judicious with permissions and access to digital data, software or hardware: Does everyone in the office have access to all the data or devices in that office? Should they?<br />
<br />
== Use cases for validation and testing ==<br />
<br />
* '''NAZRA for human rights:''' piloting the mapping tool with their forthcoming data collection process<br />
* '''Zasto Ne:''' testing the tool against election monitoring data<br />
*<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
Darko Brkan, founder, Zasto Ne<br />
<br />
Jennifer Schulte, researcher<br />
<br />
Mahy Hassaan, campaign and ad-hoc coordinator, NAZRA for feminist studies<br />
<br />
Sajjad Anwar, software developer<br />
<br />
Tin Geber, project manager, the engine room<br />
<br />
Zack Halloran, director, Crowdmap<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:51:17Z<p>Rdfwikiperson: /* Process for generating a Responsible Data Risk Map */</p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
== Process for generating a Responsible Data Risk Map ==<br />
<br />
=== Types of Harm: ===<br />
* Psycho-Social / Emotional<br />
* Physical<br />
* Economic<br />
<br />
=== 1. Identify the Persons at Risk in the event of exposure ===<br />
Definition of Persons at Risk: Any entity at risk of being by the exposure. Therefore, not restricted to the data owner or collector.<br />
<br />
=== 2. Identify Knowledge Assets that can be extracted from the data collected ===<br />
Definition of Knowledge Assets: Discrete data points, information extracted from collections of discrete data points, information extracted from meta analysis of data points, information extracted from the mashup of the collected data and external data sources.<br />
<br />
=== 3. Evaluate the importance of each knowledge asset to the campaign ===<br />
The importance is used in combination with Risk assessment to determine what data to collect.<br />
Importance is rated on this scale:<br />
* Low Importance: knowledge assets that have little or no relevance to the success of the campaign<br />
* High Importance: knowledge assets that have significant relevance to the success of the campaign<br />
* '''Must Have''': knowledge assets that are crucial to the success of the campaign<br />
<br />
=== 4. For each Type of Harm: ===<br />
Evaluate probability and severity of harm for each type of harm for each person at risk by each knowledge asset<br />
<br />
Probability of Harm:<br />
* Low - Assessed as 49% or less probability of harm<br />
* High - Assessed as 50% or more probability of harm<br />
<br />
Severity of Harm<br />
* Low - Assessed as causing little to no harm to the Person at Risk<br />
* High - Assessed as causing moderate to severe harm to the Person at Risk<br />
* '''No Go''' - Assessed as causing catastrophic harm to the Person at Risk<br />
<br />
The output of this process is a high-level score for each Person at Risk, with detailed matrices for each Type of Harm as supporting documentation.<br />
<br />
== Use cases for validation and testing ==<br />
<br />
* '''NAZRA for human rights:''' piloting the mapping tool with their forthcoming data collection process<br />
* '''Zasto Ne:''' testing the tool against election monitoring data<br />
*<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
Darko Brkan, founder, Zasto Ne<br />
<br />
Jennifer Schulte, researcher<br />
<br />
Mahy Hassaan, campaign and ad-hoc coordinator, NAZRA for feminist studies<br />
<br />
Sajjad Anwar, software developer<br />
<br />
Tin Geber, project manager, the engine room<br />
<br />
Zack Halloran, director, Crowdmap<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:42:04Z<p>Rdfwikiperson: </p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
== Process for generating a Responsible Data Risk Map ==<br />
<br />
=== Types of Harm: ===<br />
* Psycho-Social<br />
* Physical<br />
* Economic<br />
<br />
*Identify the Persons at Risk in the event of exposure<br />
**Definition of Persons at Risk: Any entity at risk of being by the exposure. Therefore, not restricted to the data owner or collector.<br />
<br />
2. Identify Knowledge Assets that can be extracted from the data collected<br />
Definition of Knowledge Assets: Discrete data points, information extracted from collections of discrete data points, information extracted from meta analysis of data points, information extracted from the mashup of the collected data and external data sources.<br />
Evaluate the importance of each knowledge asset to the campaign<br />
The importance is used in combination with Risk assessment to determine what data to collect.<br />
Importance is rated on this scale:<br />
Low Importance: knowledge assets that have little or no relevance to the success of the campaign<br />
High Importance: knowledge assets that have significant relevance to the success of the campaign<br />
Must Have: knowledge assets that are crucial to the success of the campaign<br />
For each Type of Harm:<br />
Evaluate probability and severity of harm for each type of harm for each person at risk by each knowledge asset<br />
Probability of Harm:<br />
Low - Assessed as 49% or less probability of harm<br />
High - Assessed as 50% or more probability of harm<br />
Severity of Harm<br />
Low - Assessed as causing little to no harm to the Person at Risk<br />
High - Assessed as causing moderate to severe harm to the Person at Risk<br />
No Go - Assessed as causing catastrophic harm to the Person at Risk<br />
<br />
The output of this process is a high-level score for each Person at Risk, with detailed matrices for each Type of Harm as supporting documentation.<br />
<br />
<br />
== Use cases for validation and testing ==<br />
<br />
* '''NAZRA for human rights:''' piloting the mapping tool with their forthcoming data collection process<br />
* '''Zasto Ne:''' testing the tool against election monitoring data<br />
*<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
Darko Brkan, founder, Zasto Ne<br />
<br />
Jennifer Schulte, researcher<br />
<br />
Mahy Hassaan, campaign and ad-hoc coordinator, NAZRA for feminist studies<br />
<br />
Sajjad Anwar, software developer<br />
<br />
Tin Geber, project manager, the engine room<br />
<br />
Zack Halloran, director, Crowdmap<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:39:08Z<p>Rdfwikiperson: </p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
== Process for generating a Responsible Data Risk Map ==<br />
<br />
=== Types of Harm: ===<br />
* Psycho-Social<br />
* Physical<br />
* Economic<br />
<br />
*Identify the Persons at Risk in the event of exposure<br />
**Definition of Persons at Risk: Any entity at risk of being by the exposure. Therefore, not restricted to the data owner or collector.<br />
<br />
2. Identify Knowledge Assets that can be extracted from the data collected<br />
Definition of Knowledge Assets: Discrete data points, information extracted from collections of discrete data points, information extracted from meta analysis of data points, information extracted from the mashup of the collected data and external data sources.<br />
Evaluate the importance of each knowledge asset to the campaign<br />
The importance is used in combination with Risk assessment to determine what data to collect.<br />
Importance is rated on this scale:<br />
Low Importance: knowledge assets that have little or no relevance to the success of the campaign<br />
High Importance: knowledge assets that have significant relevance to the success of the campaign<br />
Must Have: knowledge assets that are crucial to the success of the campaign<br />
For each Type of Harm:<br />
Evaluate probability and severity of harm for each type of harm for each person at risk by each knowledge asset<br />
Probability of Harm:<br />
Low - Assessed as 49% or less probability of harm<br />
High - Assessed as 50% or more probability of harm<br />
Severity of Harm<br />
Low - Assessed as causing little to no harm to the Person at Risk<br />
High - Assessed as causing moderate to severe harm to the Person at Risk<br />
No Go - Assessed as causing catastrophic harm to the Person at Risk<br />
<br />
The output of this process is a high-level score for each Person at Risk, with detailed matrices for each Type of Harm as supporting documentation.<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
<br />
== Use cases for validation and testing ==<br />
<br />
* '''NAZRA for human rights:''' piloting the mapping tool with their forthcoming data collection process<br />
* '''Zasto Ne:''' testing the tool against election monitoring data<br />
*<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
Darko Brkan, founder, Zasto Ne<br />
<br />
Jennifer Schulte, researcher<br />
<br />
Mahy Hassaan, campaign and ad-hoc coordinator, NAZRA for feminist studies<br />
<br />
Sajjad Anwar, software developer<br />
<br />
Tin Geber, project manager, the engine room<br />
<br />
Zack Halloran, director, Crowdmap<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:36:53Z<p>Rdfwikiperson: /* Contributors */</p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
<br />
== Use cases for validation and testing ==<br />
<br />
* '''NAZRA for human rights:''' piloting the mapping tool with their forthcoming data collection process<br />
* '''Zasto Ne:''' testing the tool against election monitoring data<br />
*<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
Darko Brkan, founder, Zasto Ne<br />
<br />
Jennifer Schulte, researcher<br />
<br />
Mahy Hassaan, campaign and ad-hoc coordinator, NAZRA for feminist studies<br />
<br />
Sajjad Anwar, software developer<br />
<br />
Tin Geber, project manager, the engine room<br />
<br />
Zack Halloran, director, Crowdmap<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:32:55Z<p>Rdfwikiperson: /* Audience */</p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
<br />
== Use cases for validation and testing ==<br />
<br />
* '''NAZRA for human rights:''' piloting the mapping tool with their forthcoming data collection process<br />
* '''Zasto Ne:''' testing the tool against election monitoring data<br />
*<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:30:16Z<p>Rdfwikiperson: </p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
This output builds upon (and diverges from) work done in the RDF on private sector data.<br />
<br />
= The Output =<br />
<br />
== Assumptions ==<br />
=== Three-step process. ===<br />
We assume that the risk mapping will occur inside of a three-step process:<br />
<br />
# Data (and responsible data) literacy<br />
# '''Risk mapping'''<br />
# Mitigation<br />
<br />
==== Data literacy ====<br />
In order to be able to effectively utilise the risk mapping tool, it is assumed that the practitioners understand the basic concepts and components of data, such as metadata, collection strategies, formats and storage types (boolean, integer, geographic coordinates, etc), and that they are comfortable working with data wrangling tools such as spreadsheets. <br />
<br />
Practitioners should also understand the core Responsible Data (talk to Niels, and Mary) principles that apply when collecting data that might pose risks to entities providing the data (data owners). <br />
<br />
==== Mitigation ====<br />
<br />
The risk mapping tool only assesses the risks; it does not propose or recommend risk mitigation techniques. It is assumed that risk mapping will be followed by a concrete risk mitigation phase that will be informed by the results of the risk mapping. <br />
<br />
=== Audience ===<br />
The risk mapping is always tailored towards the audience. Thus, it assumes that whoever is using it has a deep knowledge of the audience, its needs and risks. As a recommendation, the audience should always be included in the risk mapping process.<br />
<br />
=== Data is inherently unsafe ===<br />
As indicated by the recent events, the overarching assumption throughout this process is that data is always under the risk of exposure. The Risk Mapping process is not intended to communicate or build awareness on how to secure data. We recommend reading and implementing best practices when it comes to collection, storage and dissemination of data <br />
<br />
=== Types of threats ===<br />
We also assume that the person using the risk mapping tool understands the basic concepts of digital and physical threat: understanding categories, the power of information, understands what threat modelling means and what it is for, etc.<br />
<br />
=== Types of harm ===<br />
To make the assessment a non-exhaustive exercise, we have broadly classified the harms:<br />
<br />
# '''Physical Harm:''' Identifies any harm that directly puts the owner of the data as a target and cause physical damage.<br />
# '''Psychosocial/Emotional Harm:''' Identifies any harm that cause emotional or social damage to the owner of the data or their acquaintances. <br />
# '''Economic Harm:''' Identifies any harm that cause damages to personal and financial assets.<br />
<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* development of a spreadsheet that automatically maps and colours content according to input, and created charts and visualizations of the broad picture to assist with decision making<br />
* <br />
<br />
== Contributors ==<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
Frontline Defenders, [http://www.scribd.com/doc/26756511/Digital-Rights-and-Security-Human-Rights-Defenders Digital Rights and Security for Human Rights Defenders]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T12:18:44Z<p>Rdfwikiperson: </p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
''Free text''<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
<br />
== Contributors ==<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
''Feel free to link any and all background material, additional info, useful resources, etc. The more the merrier!''</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T10:21:45Z<p>Rdfwikiperson: /* Product outputs */</p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Document capturing ==<br />
<br />
[[The agenda wall]]<br />
<br />
== Product outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Responsible Data Risk Mapping]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market == <br />
<br />
[[Responsible data checklists: existing and wishing existed]]<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practice]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]]<br />
<br />
[[Harm stories]]<br />
<br />
[[orgs working on responsible data]]<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]]<br />
<br />
[[Talking about harm]]<br />
<br />
[[Collaboration software alternatives]]<br />
<br />
[[Video and photo evidence]]<br />
<br />
[[Responsible and/or open data]]<br />
<br />
[[Why should my NGO care about responsible data]]<br />
<br />
[[Spreading the word]]<br />
<br />
=== Round 2 ===<br />
<br />
[[Frameworks for data sharing]]<br />
<br />
[[Piloting plan]]<br />
<br />
[[Responsible Data campaign]]<br />
<br />
[[Responsible visualization]]<br />
<br />
[[Code of ethics in sex explotiation]]<br />
<br />
[[Responsible Data survey]]<br />
<br />
[[Human Rights documentation]]<br />
<br />
[[White paper on responsilble data standards]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Safety_ranking_systemSafety ranking system2014-10-01T10:21:13Z<p>Rdfwikiperson: Rdfwikiperson moved page Safety ranking system to Responsible Data Risk Mapping</p>
<hr />
<div>#REDIRECT [[Responsible Data Risk Mapping]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Data_Risk_CheckerData Risk Checker2014-10-01T10:21:12Z<p>Rdfwikiperson: Rdfwikiperson moved page Safety ranking system to Responsible Data Risk Mapping</p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
''Free text''<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
<br />
== Contributors ==<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
''Feel free to link any and all background material, additional info, useful resources, etc. The more the merrier!''</div>Rdfwikipersonhttps://wiki.responsibledata.io/Responsible_and/or_open_dataResponsible and/or open data2014-10-01T10:09:44Z<p>Rdfwikiperson: Created page with " 800px"</p>
<hr />
<div>[[File:RDFbuda Openvsresponsible MM.jpg | 800px]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/File:RDFbuda_Openvsresponsible_MM.jpgFile:RDFbuda Openvsresponsible MM.jpg2014-10-01T10:08:50Z<p>Rdfwikiperson: </p>
<hr />
<div></div>Rdfwikipersonhttps://wiki.responsibledata.io/Main_PageMain Page2014-10-01T10:05:59Z<p>Rdfwikiperson: /* RDF Budapest Resource Sprint. */</p>
<hr />
<div>'''Welcome to the Responsible Data Wiki!'''<br />
<br />
== [[RDF Budapest | Click here for the RDF Budapest page]] ==</div>Rdfwikipersonhttps://wiki.responsibledata.io/Talking_about_harmTalking about harm2014-10-01T10:04:11Z<p>Rdfwikiperson: Created page with " 800px"</p>
<hr />
<div>[[File:RDFbuda Talking about harm WB.jpg | 800px]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/File:RDFbuda_Talking_about_harm_WB.jpgFile:RDFbuda Talking about harm WB.jpg2014-10-01T10:03:41Z<p>Rdfwikiperson: </p>
<hr />
<div></div>Rdfwikipersonhttps://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-01T10:02:17Z<p>Rdfwikiperson: </p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
''Free text''<br />
<br />
[[File:RDFbuda consent2 WB.jpg | 800px]]<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
<br />
== Contributors ==<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
''Feel free to link any and all background material, additional info, useful resources, etc. The more the merrier!''<br />
<br />
Blog post on outputs from the Ethics of Data conference: https://www.theengineroom.org/modeling-consent-policies-for-civil-society-data/</div>Rdfwikipersonhttps://wiki.responsibledata.io/File:RDFbuda_consent2_WB.jpgFile:RDFbuda consent2 WB.jpg2014-10-01T10:01:35Z<p>Rdfwikiperson: </p>
<hr />
<div></div>Rdfwikipersonhttps://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-01T10:00:41Z<p>Rdfwikiperson: /* Notes */</p>
<hr />
<div>'''''Subtitle: one sentence on what it does, who is it for, and what is its goal'''''<br />
<br />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
''Free text''<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
<br />
== Contributors ==<br />
<br />
== Food for thought ==<br />
* concepts, problems<br />
* questions to ask frequently<br />
* preventions: what do you actually do in concrete terms to prevent these things from happening<br />
* reactions: responsible responses for when things go wrong<br />
<br />
== Resources (we <3 links!) ==<br />
''Feel free to link any and all background material, additional info, useful resources, etc. The more the merrier!''<br />
<br />
Blog post on outputs from the Ethics of Data conference: https://www.theengineroom.org/modeling-consent-policies-for-civil-society-data/</div>Rdfwikipersonhttps://wiki.responsibledata.io/File:RDFbuda_consent_WB.jpgFile:RDFbuda consent WB.jpg2014-10-01T09:58:36Z<p>Rdfwikiperson: </p>
<hr />
<div></div>Rdfwikipersonhttps://wiki.responsibledata.io/PoliciesPolicies2014-10-01T09:56:07Z<p>Rdfwikiperson: </p>
<hr />
<div>== Policies that exist ==<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | Title<br />
! style="font-weight: bold;" | Organization/Group<br />
! style="font-weight: bold;" | What is it for<br />
|-<br />
| Data Ethics Policy<br />
| Oxfam<br />
| All data that all Oxfam uses<br />
|-<br />
| Research Ethics (pictures, videos, etc.), Consent<br />
| Oxfam<br />
| Research practices in Oxfam [OUTDATED]<br />
|-<br />
| Outcome on ECSA project governance framework<br />
| iilab/fpu/greenhost/chokepoint/others (EC-project)<br />
| Internet censorship and human rights data<br />
|-<br />
| Cash & Learning Partnership Principles for Protecting Privacy<br />
| CACP-consortium of NGOs<br />
| Financial/Registration/Accountability data<br />
|-<br />
| Interviewing/Researching Children Guidelines<br />
| UNICEF & Save<br />
| Specific considering working with children<br />
|-<br />
| Guidelines for ICTs regarding digital rights practices<br />
| Global Network Initiative<br />
| Sometimes just show, but it’s a start to engage companies in their responsibilities<br />
|-<br />
| 3rd Party Usage Policy<br />
| Twaweza East Africa<br />
| Guide 3rd party uses of our mobile phone panel survey on the use of the platform<br />
|-<br />
| Organizational Policies (for CSOs) on Collecting, Processing, Disseminating Data<br />
| N/A<br />
| <br />
|-<br />
| Photo and Video Consent Policy & Use Policy<br />
| Lots of People (HRW specifically cited)<br />
| Protecting subjects of photos and videos upholding ethical and protection standards<br />
|-<br />
| Whistle Blower Handling Policy<br />
| Hungarian CSO<br />
| Protecting whistleblowers and the organization<br />
|}<br />
<br />
== Policies we wish existed ==<br />
<br />
{| class="wikitable"<br />
! Who’s it for<br />
! What’s it for<br />
! What format<br />
|-<br />
| Owners of knowledge aggregator and dissemination platform<br />
| Standardizing safe collection and storage of sensitive data assets<br />
| Policy document and workflow enforcement<br />
|-<br />
| Funders/Grantees<br />
| Required data practices prior to receiving funding<br />
| Included in proposal / Call fro proposals; Parts of required things to sign<br />
|-<br />
| Small NGOs<br />
| Baseline data/digital security policy<br />
| Document or other legible thing<br />
|-<br />
| Small-medium groups<br />
| Data cycle – from collection to advocacy<br />
| Comic<br />
|-<br />
| All NGOs working on GBV/VAW<br />
| Standard data, Better statistics, Collection<br />
| Standardization of data collection and collaboration of all data sources<br />
|-<br />
| Data trainers (School of Data)<br />
| Ethical data sources for trainings<br />
| <br />
|}</div>Rdfwikipersonhttps://wiki.responsibledata.io/PoliciesPolicies2014-10-01T09:55:43Z<p>Rdfwikiperson: Created page with "=== Policies that exist === {| class="wikitable" ! style="font-weight: bold;" | Title ! style="font-weight: bold;" | Organization/Group ! style="font-weight: bold;" | What is..."</p>
<hr />
<div>=== Policies that exist ===<br />
{| class="wikitable"<br />
! style="font-weight: bold;" | Title<br />
! style="font-weight: bold;" | Organization/Group<br />
! style="font-weight: bold;" | What is it for<br />
|-<br />
| Data Ethics Policy<br />
| Oxfam<br />
| All data that all Oxfam uses<br />
|-<br />
| Research Ethics (pictures, videos, etc.), Consent<br />
| Oxfam<br />
| Research practices in Oxfam [OUTDATED]<br />
|-<br />
| Outcome on ECSA project governance framework<br />
| iilab/fpu/greenhost/chokepoint/others (EC-project)<br />
| Internet censorship and human rights data<br />
|-<br />
| Cash & Learning Partnership Principles for Protecting Privacy<br />
| CACP-consortium of NGOs<br />
| Financial/Registration/Accountability data<br />
|-<br />
| Interviewing/Researching Children Guidelines<br />
| UNICEF & Save<br />
| Specific considering working with children<br />
|-<br />
| Guidelines for ICTs regarding digital rights practices<br />
| Global Network Initiative<br />
| Sometimes just show, but it’s a start to engage companies in their responsibilities<br />
|-<br />
| 3rd Party Usage Policy<br />
| Twaweza East Africa<br />
| Guide 3rd party uses of our mobile phone panel survey on the use of the platform<br />
|-<br />
| Organizational Policies (for CSOs) on Collecting, Processing, Disseminating Data<br />
| N/A<br />
| <br />
|-<br />
| Photo and Video Consent Policy & Use Policy<br />
| Lots of People (HRW specifically cited)<br />
| Protecting subjects of photos and videos upholding ethical and protection standards<br />
|-<br />
| Whistle Blower Handling Policy<br />
| Hungarian CSO<br />
| Protecting whistleblowers and the organization<br />
|}<br />
<br />
=== Policies we wish existed ===<br />
<br />
{| class="wikitable"<br />
! Who’s it for<br />
! What’s it for<br />
! What format<br />
|-<br />
| Owners of knowledge aggregator and dissemination platform<br />
| Standardizing safe collection and storage of sensitive data assets<br />
| Policy document and workflow enforcement<br />
|-<br />
| Funders/Grantees<br />
| Required data practices prior to receiving funding<br />
| Included in proposal / Call fro proposals; Parts of required things to sign<br />
|-<br />
| Small NGOs<br />
| Baseline data/digital security policy<br />
| Document or other legible thing<br />
|-<br />
| Small-medium groups<br />
| Data cycle – from collection to advocacy<br />
| Comic<br />
|-<br />
| All NGOs working on GBV/VAW<br />
| Standard data, Better statistics, Collection<br />
| Standardization of data collection and collaboration of all data sources<br />
|-<br />
| Data trainers (School of Data)<br />
| Ethical data sources for trainings<br />
| <br />
|}</div>Rdfwikipersonhttps://wiki.responsibledata.io/Orgs_working_on_responsible_dataOrgs working on responsible data2014-10-01T09:52:48Z<p>Rdfwikiperson: Created page with "{| class="wikitable" ! who ! what ! why |- | Ushahidi | application developer | we work with data and othe rpeoples data |- | HURIDOCS | application developer | we work with d..."</p>
<hr />
<div>{| class="wikitable"<br />
! who<br />
! what<br />
! why<br />
|-<br />
| Ushahidi<br />
| application developer<br />
| we work with data and othe rpeoples data<br />
|-<br />
| HURIDOCS<br />
| application developer<br />
| we work with data and othe rpeoples data<br />
|-<br />
| People's Intelligence<br />
| Crowdseeding – feeding back, verification<br />
| forcing strict standards upon himself before going into practice<br />
|-<br />
| School of Data<br />
| training on data literacy<br />
| they know how to teach about data<br />
|-<br />
| world economic forum<br />
| facilitating responsible data dialogue between different actors and stakeholders<br />
| developing responsible data sharing frameworks<br />
|-<br />
| datakind<br />
| brings together data scientists w/ non profits<br />
| they can help with your data<br />
|-<br />
| orange<br />
| data for development<br />
| opeing up own datasets within different regions for development (analysis)<br />
|-<br />
| SEAleaks (to be launched)<br />
| FOI on sexual exploitation and abuse including trafficking<br />
| anonymous reporting platform for humanitarians<br />
|-<br />
| IATI (international AID transparency initiative)<br />
| create open source data platform for giving (bilateral and foundation data)<br />
| promoting open sharing of data<br />
|-<br />
| AID data<br />
| add coding to development data and make freely available<br />
| capture additional detail ? Of data in OECD DAC database<br />
|-<br />
| WINGS (world wide initiatives for grantmaker support)<br />
| creating philanthropic data charter<br />
| encourage transparency w/in philanthropy<br />
|-<br />
| iHub (research)<br />
| online dangerous speech<br />
| to better understand speech with potential to catalyze violence<br />
|-<br />
| international human rights funders group<br />
| tracking and visualizing the state of global human rights grantmaking<br />
| promote more strategic human rihgts grantmaking and greater transparency<br />
|-<br />
| Ariakse?<br />
| tracking and visualizing the state of global human rights grantmaking<br />
| promote more strategic human rihgts grantmaking and greater transparency<br />
|-<br />
| International network of women funds?<br />
| tracking and visualizing the state of global human rights grantmaking<br />
| promote more strategic human rihgts grantmaking and greater transparency<br />
|-<br />
| Foundation Center<br />
| tracking and visualizing the state of global human rights grantmaking<br />
| promote more strategic human rihgts grantmaking and greater transparency<br />
|-<br />
| HIVOS (SDI programme)<br />
| evidence based planning and accountability demands<br />
| real life grassroots level data utility and lessons on data grant making<br />
|-<br />
| Health care program (e.g. harvard medical school bioinformatics program)<br />
| safer collection and use of PII<br />
| clinician and research scientists<br />
|-<br />
| gender LDG<br />
| data repository of GBV/VAW and other human rights issues<br />
| online library/archive of info<br />
|-<br />
| Videre<br />
| combining collected activists data (video) w/ open source data<br />
| to identify patterns of abuse<br />
|}</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T09:52:21Z<p>Rdfwikiperson: /* Resource Lists / Farmer's Market */</p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Document capturing ==<br />
<br />
[[The agenda wall]]<br />
<br />
== Product outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market == <br />
<br />
[[Responsible data checklists: existing and wishing existed]]<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practice]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]]<br />
<br />
[[Harm stories]]<br />
<br />
[[orgs working on responsible data]]<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]]<br />
<br />
[[Talking about harm]]<br />
<br />
[[Collaboration software alternatives]]<br />
<br />
[[Video and photo evidence]]<br />
<br />
[[Responsible and/or open data]]<br />
<br />
[[Why should my NGO care about responsible data]]<br />
<br />
[[Spreading the word]]<br />
<br />
=== Round 2 ===<br />
<br />
[[Frameworks for data sharing]]<br />
<br />
[[Piloting plan]]<br />
<br />
[[Responsible Data campaign]]<br />
<br />
[[Responsible visualization]]<br />
<br />
[[Code of ethics in sex explotiation]]<br />
<br />
[[Responsible Data survey]]<br />
<br />
[[Human Rights documentation]]<br />
<br />
[[White paper on responsilble data standards]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Responsible_data_checklists:_existing_and_wishing_existedResponsible data checklists: existing and wishing existed2014-10-01T09:51:02Z<p>Rdfwikiperson: </p>
<hr />
<div>=== Responsible data checklists that exist ===<br />
<br />
{| class="wikitable"<br />
! name<br />
! publisher<br />
! why it's useful<br />
|-<br />
| responsible development data – practitioners guide (list of ethical questions)<br />
| RDF oakland output<br />
| helps practitioners implementing projects w/ data components<br />
|-<br />
| Umbrella app, security (digital and physical)<br />
| security first<br />
| all the security info you can get into your pocket<br />
|-<br />
| informed consent checklist for research staff<br />
| Amnesty International<br />
| I'm not sure if it's useful. Guidance to researchers<br />
|-<br />
| CALP (cash and learning partnership) protect beneficiary data<br />
| cash and learning partnership NGO coalition<br />
| financial and registration data principles<br />
|-<br />
| protection/informed consent<br />
| ICRC<br />
| guidelines on ensuring thos ewe extract data from are aware of its use/do no harm<br />
|-<br />
| capture the ocean<br />
| group of NGOs via Simlab<br />
| legal advice in different contexts more accessible and understandable<br />
|-<br />
| security in a box and me and my shadow<br />
| tactical tech<br />
| user friendly guide to security, ways to trace your digital footprint, links to existing tools and products<br />
|}<br />
<br />
=== Responsible data checklists we wish existed ===<br />
<br />
{| class="wikitable"<br />
! What it would be<br />
! What it would help you do<br />
|-<br />
| Top 5 issues describing what responsible data is (talking points)<br />
| talk about responsible data<br />
|-<br />
| identity protection checklist for data assets<br />
| more safely share narratives and statistics at an aggregate and individual level<br />
|-<br />
| responsible hosting checklist<br />
| make sure you are keeping hosted data secure<br />
|-<br />
| responsible data publishing, collecting, managing<br />
| double check steps and milestones in data processes<br />
|-<br />
| transfer process, destruction or retension of anmot (anaolog?) material??<br />
| think about privacy issues concerning anmot sources of data such as surveys<br />
|}<br />
<br />
=== Other resources ===<br />
Here is a spreadsheet of tools/guides/checklists that the engine room has found:<br />
<br />
https://docs.google.com/a/theengineroom.org/spreadsheet/ccc?key=0AstZ6Hn7MaXHdE5UWmlCdk1WczVQbWFRY3dlNzlrMFE&usp=drive_web#gid=0</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T09:46:47Z<p>Rdfwikiperson: /* Resource Lists / Farmer's Market */</p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Document capturing ==<br />
<br />
[[The agenda wall]]<br />
<br />
== Product outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market == <br />
<br />
[[Responsible data checklists: existing and wishing existed]]<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practice]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]]<br />
<br />
[[Harm stories]]<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]]<br />
<br />
[[Talking about harm]]<br />
<br />
[[Collaboration software alternatives]]<br />
<br />
[[Video and photo evidence]]<br />
<br />
[[Responsible and/or open data]]<br />
<br />
[[Why should my NGO care about responsible data]]<br />
<br />
[[Spreading the word]]<br />
<br />
=== Round 2 ===<br />
<br />
[[Frameworks for data sharing]]<br />
<br />
[[Piloting plan]]<br />
<br />
[[Responsible Data campaign]]<br />
<br />
[[Responsible visualization]]<br />
<br />
[[Code of ethics in sex explotiation]]<br />
<br />
[[Responsible Data survey]]<br />
<br />
[[Human Rights documentation]]<br />
<br />
[[White paper on responsilble data standards]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/The_agenda_wallThe agenda wall2014-10-01T09:45:22Z<p>Rdfwikiperson: Created page with "{| class="wikitable" ! Language and terms ! Ethics ! Funders ! tech/software ! ownership ! sharing ! agency, consent ! low tech ! Policies and standards ! data verification !..."</p>
<hr />
<div>{| class="wikitable"<br />
! Language and terms<br />
! Ethics<br />
! Funders<br />
! tech/software<br />
! ownership<br />
! sharing<br />
! agency, consent<br />
! low tech<br />
! Policies and standards<br />
! data verification<br />
! regional/local<br />
! censorship<br />
! collaboration<br />
! community engagement<br />
! training<br />
! open data vs responsible data<br />
! <br />
! Sensitive data<br />
! Mobile<br />
! government<br />
! historical data<br />
! project cycle, project mgt<br />
! <br />
! reshaping data process<br />
! who should care?<br />
! Communications<br />
! Awareness and advocacy<br />
! blind spots<br />
! academics and research<br />
! actor roles<br />
|-<br />
| different meanings of open<br />
| connection between info sec and ethical data issues<br />
| how can funder relationships be more accountable for bad data practices<br />
| transparent software development processes<br />
| who owns the data and metadata?<br />
| how to mobilize people around data and privacy issues?<br />
| voice and agency coming constantly from marginalised communities<br />
| how to be responsible with data in a non-digitized environment?<br />
| RD and govts: what are the guidelines?<br />
| data verification of evidence submitted on corruption driving trafficking are challenging<br />
| how do we replicate this to a regional / city level?<br />
| when does responsibility become self-censorship?<br />
| connecting orgs to data experts and resources<br />
| how can we include a community in creation of resources that are for them<br />
| training methodologies for RD<br />
| what is the balance between individual rights and historical value?<br />
| <br />
| how do we protect those collecting data?<br />
| what are harm stories of mobile in low income countries?<br />
| what are the difference between being responsible with data in public and non-public sectors?<br />
| there is a lot of focus on contemporary data / human rights data: what about historical data?<br />
| what does the end stage of a project look like?<br />
| <br />
| strategies for letting people own their data again<br />
| are there any NGOs who don't need to freak out? Let's not assume anything<br />
| elevator pitch - what is data and whyshould my NGO care<br />
| how do we engage stakeholders in a dialogue around responsibleuse of perosonal health data?<br />
| how to involve unusual partners - creatives, artists, etc<br />
| would like to see and discuss more about responsible data in academia amond researchers<br />
| should data practices change between rights- and needs- based orgs?<br />
|-<br />
| we need to translate those concepts to real language<br />
| we collect info / data from orgs we don't talk to, how can we do that responsibly?<br />
| how can we get funding and resources for holistic security training for humanitarian and development researchers<br />
| tyranny of algorithms transparency of technology behind the scenes<br />
| sensitive data about third parties, what are their rights?<br />
| can our intention to be responsible be at odds with other instructions?<br />
| how to keep up with evolving risks<br />
| are there any specific methodologies for digitising and sharing data collected in a low-tech way?<br />
| how do we create standards guidelines for responsible data across such different contexts?<br />
| we need a method of verification to an online platform to report sexual violence incidents from spam by the police<br />
| checklists / toolkits for working with data at more than local / regional contexts<br />
| <br />
| how to involve more industrie into resp data?<br />
| how to mae non-specialists more able to interpret and communicate data?<br />
| responsible practices embedded in training pracices<br />
| how to prevent govt from stopping data disclosing on the basis of being responsible?<br />
| <br />
| how do we create effective resources that will help engage communities around the implications of collected stored data about them<br />
| mobile and its dangers: how to protect yourself when you are the product?<br />
| how to recapture civil society space when govt takes it?<br />
| <br />
| data lifecycle and evolving responsible data challenges<br />
| <br />
| how do we make data processes less extractive and more empowering?<br />
| elevator pitch - what is RDF and why should I care?<br />
| how will we package, share, collaborate, disseminate outputs<br />
| what are or should be our advodcacy strategies?<br />
| who is missing?<br />
| would it be relevant to bring RD concepts to formal education?<br />
| should data pracices change in high stress / fatality situations?<br />
|-<br />
| how do we speak the same language across fields?<br />
| who are we collecting data for?<br />
| when not to collect data at all?<br />
| defaults in tech and policy/law<br />
| emancipation of data that is locked into platforms<br />
| externalities of data use? Unintended harm<br />
| can consent be revoked after collection?<br />
| <br />
| what policies do we need?<br />
| verification when sources of data are practically anonymous<br />
| <br />
| <br />
| how to work wth what a lot of people use to communicate? Like FB<br />
| what are the knowledge needs of CS advocates?<br />
| we need gender, privacy and digisec trainings for humanitarian who work on GBV<br />
| we need to have a very good and secure system for the online platform to report sexual violence incidents<br />
| <br />
| collecting sensitive data without means to ensure security of data<br />
| <br />
| <br />
| <br />
| what are feasible data storare practices for poorly funded NGOs with a variety of threat models?<br />
| <br />
| collection of out of the box unconventional methods of working with RD<br />
| <br />
| make sure to keep focussed on people and actual problems - people centered approach<br />
| strategies and methodologies for fighting data-hoarding entities<br />
| who else should be here? How do we get thm here?<br />
| more case studies, guidance on doing informed consent wih vulnerable populations in emergency settings<br />
| what can lawyers do?<br />
|-<br />
| a glossary on data-related terms<br />
| code of ethics needed on reporting sexual exploitation and abuse in humanitarian response contexts<br />
| disclaimers? Or something better with unverified or poorly verified data<br />
| building data infrastructure responsibly<br />
| who owns the data? Can the data building contributors be co creators and coowneers?<br />
| how can we use SCODA to disseminate RD resources<br />
| getting consent about using data collected<br />
| <br />
| are responsible data standards floors or ceilings?<br />
| how to collect and share and store video and photo evidence, security<br />
| <br />
| <br />
| what collaboration tools do we use? Not google docs!<br />
| <br />
| we need capacity development on follow the money anti-corruption research in isalimic finance contexts<br />
| how do we address the exploitative nature of open data<br />
| <br />
| how do we protect those who give us data?<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do we evaluate resources after they are reversed<br />
| <br />
| how to talk about RD to funders<br />
| how to create civil resistance, civic disobedience to mobilise people? Motivate<br />
| what is the cost of RDF? $, time, effort, tech<br />
| can data be used to examine corruption while being responsible? I hate the term corruption<br />
| what is private setor role and how to engage it (data brokers)<br />
|-<br />
| we need a common, inclusive, non-technical lingo to talk about data<br />
| basic code of ethics that is simple and shareable<br />
| how do we create funder buy-in?<br />
| how do we better enable orgs to deal with tech issues around resp data, if they don't have tech resources<br />
| group / collective privacy vs protecting individual<br />
| how to develop responsible data sharing frameworks?<br />
| how can consent be ensured across all levels of the data supply chain?<br />
| <br />
| how do we create standards?<br />
| how does the human rights field strike a balance between transparency and security?<br />
| <br />
| <br />
| how do we share institutional knowledge across the RD movement?<br />
| <br />
| we ned usable tools for self-assessment<br />
| how do we engage NGOs to share and use shared data and not be competitive?<br />
| <br />
| how do we ensure responsible collection and use of sensitive envronmental monitoring data?<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do we appeal to groups outside HR<br />
| how to engage actors / stakeholders in the debate that are not yet involved?<br />
| I want a concept of what RD means for journalism - in traiditional news rooms and NGOs doing ournalistic work<br />
| how can researchers help meet knowledge needs?<br />
| how does media become more aware of handling / using data more responsibly?<br />
|-<br />
| <br />
| level of responsible versus feasibility of acting responsibly<br />
| should responsible data be a requirement for receiving a grant?<br />
| how do we lower the tech entry barrier for digital security?<br />
| collecting and transmitting data from conflict zones what is RD<br />
| <br />
| <br />
| <br />
| what are the practices and needs around PII?<br />
| is geo data an identifier of the source of data?<br />
| <br />
| <br />
| should there be a right to data ownership and privacy charter for all the people we work with<br />
| <br />
| how to guide W&D's to berrer resource their programs with data components?<br />
| what is the balance between open data and RD - will RD slow down OD? Is that good or bad?<br />
| <br />
| regional / global / local secual violence data collection and verification<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do we engage the cultural sector with RD? to raise understanding and best practices<br />
| how do citizens get awareness on RD?<br />
| <br />
| develop more resources outreach for humanitarian practitioners that are accessible - multiple languages, plain speak<br />
| how do we engage all actors involved with data collection and visualization? Funders, archivists, designers, coders<br />
|-<br />
| <br />
| do we need to reform or expand the IRB?<br />
| data audits for grantees<br />
| connection between security and transparency<br />
| how ensure all actors better protect their own data as well as the data of those they protect?<br />
| <br />
| <br />
| <br />
| will we make "minimum" and "deluxe" standards for data hosting and gatehring? #icons #standards<br />
| <br />
| <br />
| <br />
| we need collaborators to further design new platform on sexual exploitation and abuse, whistleblowing around war zones, militarty bases<br />
| <br />
| <br />
| open data not just about sharing data it's about being open and transparent about data collection, consent, security and privacy<br />
| <br />
| how does data mapping expose the source of data?<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| is responsible the best word? Conceptually yes, but maybe not rhetorically<br />
| how to frame and package the ethics conversation in different settings<br />
| <br />
| increased numbers of LAY researchers<br />
| <br />
|-<br />
| <br />
| IRB equivalent for digital, P2P, human rights<br />
| focus on process what about outcome result<br />
| <br />
| orgs come and go but data never dies<br />
| <br />
| <br />
| <br />
| get ideas for our data ethics policy and see if others have things we can use<br />
| <br />
| <br />
| <br />
| what are the priorities of collecting data and responsibilities to people collected from<br />
| <br />
| <br />
| how open is data really?<br />
| <br />
| de-anonymizable metadata - how can you really clean data?<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do you make data talk colloquial?<br />
| what makes data relevant t us?<br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| keep the privacy of WHRD & survivals<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do we engage people to adhere to standards?<br />
| <br />
| <br />
| <br />
| how to share best and worst practices as well as lessons learned?<br />
| <br />
| <br />
| <br />
| <br />
| it would be helpful to have a standard risk assessment for data collection connected to the various data collection tools<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how to make Rd practices desirable? Fun cool<br />
| how to protect people joining and supporting sensitive cmpaigns?<br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| we need standards for data collection<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do we address data protection insurance issues<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| what ar the comms tools and tstrategy needs for CS orgs?<br />
| strategies to cope with data risks<br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| we need guidelines for people on the ground collecting data<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| find a balance between the need for transparency and the need for data protection<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| what could follow up post buda look like?<br />
| how to guide orgs to have kill dates on data sets but still absorb and share learning and knowledge<br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how are each of us personally connected with data? What makes us passionate about data and why?<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how can we go about anomyzing data for transfer and or when using it for public messaging<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how to build RDF into organisational culture and normalise good practice<br />
| making sure people actually use the resources<br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how long do you use or store data? Data life - should there be an end to data?<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| linking org security with dta privacy enpoint security data mgt<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how to make data and data analysis understandable?<br />
| making advocacy strategy responsible<br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| can we have an IRB for civil society<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| do crowdsourced data leave out the most vulnerable cases?<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do we outreach to social justice orgs already working in similar issues?<br />
| <br />
| <br />
| <br />
|-<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| how do we pressure donors to seek more RD practices?<br />
| <br />
| <br />
| <br />
|}</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T09:41:51Z<p>Rdfwikiperson: </p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Document capturing ==<br />
<br />
[[The agenda wall]]<br />
<br />
== Product outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market == <br />
<br />
[[Responsible data checklists: existing and wishing existed]]<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practice]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]]<br />
<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]]<br />
<br />
[[Talking about harm]]<br />
<br />
[[Collaboration software alternatives]]<br />
<br />
[[Video and photo evidence]]<br />
<br />
[[Responsible and/or open data]]<br />
<br />
[[Why should my NGO care about responsible data]]<br />
<br />
[[Spreading the word]]<br />
<br />
=== Round 2 ===<br />
<br />
[[Frameworks for data sharing]]<br />
<br />
[[Piloting plan]]<br />
<br />
[[Responsible Data campaign]]<br />
<br />
[[Responsible visualization]]<br />
<br />
[[Code of ethics in sex explotiation]]<br />
<br />
[[Responsible Data survey]]<br />
<br />
[[Human Rights documentation]]<br />
<br />
[[White paper on responsilble data standards]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T09:30:02Z<p>Rdfwikiperson: /* Day 2 morning conversations */</p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market ==<br />
This section is collecting all resources that come up during the <br />
<br />
[[Responsible data checklists: existing and wishing existed]] (Kristin)<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practices]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]] (Alix)<br />
<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]]<br />
<br />
[[Talking about harm]]<br />
<br />
[[Collaboration software alternatives]]<br />
<br />
[[Video and photo evidence]]<br />
<br />
[[Responsible and/or open data]]<br />
<br />
[[Why should my NGO care about responsible data]]<br />
<br />
[[Spreading the word]]<br />
<br />
=== Round 2 ===<br />
<br />
[[Frameworks for data sharing]]<br />
<br />
[[Piloting plan]]<br />
<br />
[[Responsible Data campaign]]<br />
<br />
[[Responsible visualization]]<br />
<br />
[[Code of ethics in sex explotiation]]<br />
<br />
[[Responsible Data survey]]<br />
<br />
[[Human Rights documentation]]<br />
<br />
[[White paper on responsilble data standards]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T09:29:46Z<p>Rdfwikiperson: /* Day 2 morning conversations */</p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market ==<br />
This section is collecting all resources that come up during the <br />
<br />
[[Responsible data checklists: existing and wishing existed]] (Kristin)<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practices]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]] (Alix)<br />
<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]]<br />
<br />
[[Talking about harm]]<br />
<br />
[[Collaboration software alternatives]]<br />
<br />
[[Video and photo evidence]]<br />
<br />
[[Responsible and/or open data]]<br />
<br />
[[Why should my NGO care about repsonsible data]]<br />
<br />
[[Spreading the word]]<br />
<br />
=== Round 2 ===<br />
<br />
[[Frameworks for data sharing]]<br />
<br />
[[Piloting plan]]<br />
<br />
[[Responsible Data campaign]]<br />
<br />
[[Responsible visualization]]<br />
<br />
[[Code of ethics in sex explotiation]]<br />
<br />
[[Responsible Data survey]]<br />
<br />
[[Human Rights documentation]]<br />
<br />
[[White paper on responsilble data standards]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T09:28:08Z<p>Rdfwikiperson: </p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market ==<br />
This section is collecting all resources that come up during the <br />
<br />
[[Responsible data checklists: existing and wishing existed]] (Kristin)<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practices]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]] (Alix)<br />
<br />
<br />
== Day 2 morning conversations ==<br />
<br />
=== Round 1 ===<br />
[[Packaging]]<br />
[[Talking about harm]]<br />
[[Collaboration software alternatives]]<br />
[[Video and photo evidence]]<br />
[[Responsible and/or open data]]<br />
[[Why should my NGO care about repsonsible data]]<br />
[[Spreading the word]]<br />
<br />
=== Round 2 ===<br />
[Frameworks for data sharing]]<br />
[[piloting plan]]<br />
Responsible DataRD campaign Dirk<br />
visualization mushon<br />
code of ethics sex explotiation willow<br />
suvey chris<br />
HR doc friedhelm<br />
white paper standards niels</div>Rdfwikipersonhttps://wiki.responsibledata.io/PackagingPackaging2014-10-01T08:45:16Z<p>Rdfwikiperson: </p>
<hr />
<div>== Possible types of outputs ==<br />
<br />
* passive consumption documents (digital, print)<br />
* interaction <br />
** forms and checklists (interactive)<br />
* curation: lists of resources<br />
* graphic and visualizations (static, interactive)<br />
* process diagrams<br />
* pictures and video, multimedia<br />
* cards, flash cards, active support material<br />
* group activities, exercises<br />
* training modules, education materials<br />
* artwork (any type of art)<br />
* promo / comms materials<br />
* campaign (strategy)<br />
<br />
== Final versus iterative ==<br />
* working groups, communities of practice, support groups<br />
* who to get in touch with and where<br />
* contact list<br />
* use of collaborative tools like github, wiki, google docs, dropbox, hackpad etc <br />
** connect with the OOGLE group for more tools<br />
<br />
* metadata of single output versus collection of outputs<br />
<br />
== Metadata == <br />
check * [[http://dublincore.org/documents/dcmi-terms/ DUBLIN CORE METADATA ELEMENT SET VERSION 1.1]]<br />
<br />
* Title (*)<br />
* Author (*)<br />
* A very clear and concise description telling us (*):<br />
** what it is<br />
** what it does<br />
** for whom<br />
* Publisher (*)<br />
* Contributor (*)<br />
* PUT A DATE ON IT (*)<br />
**date created, date last modified<br />
**use by date * expiration date * not good after date<br />
* Format (see possible types of output) (*)<br />
**supported platforms<br />
* Source (URL, original non*translated version, master of forks etc) (*)<br />
* Language (*)<br />
* Keywords / tags (*)<br />
<br />
* use cases<br />
* target audience(s)<br />
** to flesh out in free form<br />
* location, target location<br />
<br />
* LICENSE<br />
<br />
== Containers / Capsules ==<br />
Depends on audience.<br />
<br />
CURATION IS KEY<br />
<br />
UPDATE IS ALSO KEY<br />
<br />
MANAGEMENT IS EVEN MORE KEY<br />
<br />
=== List of containers ===<br />
* github repo<br />
** documents can also live on github, but be packaged and presented through other containers<br />
* website<br />
** splash page (indepdendent)<br />
** institutional website, curated/guided (by collaborator or publisher or RD partner)<br />
* print<br />
* wiki<br />
** RD wiki<br />
** ad hoc wikis<br />
* social networks (example: visualization that gets pushed throug twitter without it living anywhere specific)<br />
* email lists<br />
* physical archives<br />
* graffiti, stencil, street art, tattoos<br />
<br />
== Tools - TBD ==<br />
* example: Security in a box<br />
<br />
== Questions ==<br />
* how to track revisions?<br />
* how to make sure outputs created during the RDF can be shared for iterative collaboration?</div>Rdfwikipersonhttps://wiki.responsibledata.io/PackagingPackaging2014-10-01T08:39:17Z<p>Rdfwikiperson: </p>
<hr />
<div>== Possible types of outputs ==<br />
<br />
* passive consumption documents (digital, print)<br />
* interaction <br />
** forms and checklists (interactive)<br />
* curation: lists of resources<br />
* graphic and visualizations (static, interactive)<br />
* process diagrams<br />
* pictures and video, multimedia<br />
* cards, flash cards, active support material<br />
* group activities, exercises<br />
* training modules, education materials<br />
* artwork (any type of art)<br />
* promo / comms materials<br />
* campaign (strategy)<br />
<br />
== Final versus iterative ==<br />
* working groups, communities of practice, support groups<br />
* who to get in touch with and where<br />
* contact list<br />
* use of collaborative tools like github, wiki, google docs, dropbox etc <br />
<br />
* metadata of single output versus collection of outputs<br />
<br />
== Metadata == <br />
check * [[http://dublincore.org/documents/dcmi-terms/ DUBLIN CORE METADATA ELEMENT SET VERSION 1.1]]<br />
<br />
* Title (*)<br />
* Author (*)<br />
* A very clear and concise description telling us (*):<br />
** what it is<br />
** what it does<br />
** for whom<br />
* Publisher (*)<br />
* Contributor (*)<br />
* PUT A DATE ON IT (*)<br />
**date created, date last modified<br />
**use by date * expiration date * not good after date<br />
* Format (see possible types of output) (*)<br />
**supported platforms<br />
* Source (URL, original non*translated version, master of forks etc) (*)<br />
* Language (*)<br />
* Keywords / tags (*)<br />
<br />
* use cases<br />
* target audience(s)<br />
** to flesh out in free form<br />
* location, target location<br />
<br />
* LICENSE<br />
<br />
== Containers / Capsules ==<br />
Depends on audience.<br />
<br />
CURATION IS KEY<br />
<br />
UPDATE IS ALSO KEY<br />
<br />
MANAGEMENT IS EVEN MORE KEY<br />
<br />
=== List of containers ===<br />
* github repo<br />
** documents can also live on github, but be packaged and presented through other containers<br />
* website<br />
** splash page (indepdendent)<br />
** institutional website, curated/guided (by collaborator or publisher or RD partner)<br />
* print<br />
* wiki<br />
** RD wiki<br />
** ad hoc wikis<br />
* social networks (example: visualization that gets pushed throug twitter without it living anywhere specific)<br />
* email lists<br />
* physical archives<br />
* graffiti, stencil, street art, tattoos<br />
<br />
== Tools - TBD ==<br />
* example: Security in a box<br />
<br />
== Questions ==<br />
* how to track revisions?<br />
* how to make sure outputs created during the RDF can be shared for iterative collaboration?</div>Rdfwikipersonhttps://wiki.responsibledata.io/PackagingPackaging2014-10-01T08:32:23Z<p>Rdfwikiperson: Created page with "== Possible types of outputs == * passive consumption documents (digital, print) * interaction ** forms and checklists (interactive) * curation: lists of resources * graphic..."</p>
<hr />
<div>== Possible types of outputs ==<br />
<br />
* passive consumption documents (digital, print)<br />
* interaction <br />
** forms and checklists (interactive)<br />
* curation: lists of resources<br />
* graphic and visualizations (static, interactive)<br />
* process diagrams<br />
* pictures and video, multimedia<br />
* cards, flash cards, active support material<br />
* group activities, exercises<br />
* training modules, education materials<br />
* artwork (any type of art)<br />
* promo / comms materials<br />
* campaign (strategy)<br />
<br />
== Final versus iterative ==<br />
* working groups, communities of practice, support groups<br />
* who to get in touch with and where<br />
* contact list<br />
<br />
* metadata of single output versus collection of outputs<br />
<br />
== Metadata == <br />
check * [[http://dublincore.org/documents/dcmi-terms/ DUBLIN CORE METADATA ELEMENT SET VERSION 1.1]]<br />
<br />
* Title (*)<br />
* Author (*)<br />
* A very clear and concise description telling us (*):<br />
** what it is<br />
** what it does<br />
** for whom<br />
* Publisher (*)<br />
* Contributor (*)<br />
* PUT A DATE ON IT (*)<br />
**date created, date last modified<br />
**use by date * expiration date * not good after date<br />
* Format (see possible types of output) (*)<br />
**supported platforms<br />
* Source (URL, original non*translated version, master of forks etc) (*)<br />
* Language (*)<br />
* Keywords / tags (*)<br />
<br />
* use cases<br />
* target audience(s)<br />
** to flesh out in free form<br />
* location, target location<br />
<br />
* LICENSE<br />
<br />
== CONTAINERS / CAPSULES ==<br />
* depends on audience<br />
<br />
* CURATION IS KEY<br />
* UPDATE IS ALSO KEY<br />
* MANAGEMENT IS EVEN MORE KEY<br />
<br />
* website<br />
** splash page (indepdendent)<br />
** institutional website, curated/guided (by collaborator or publisher or RD partner)<br />
* print<br />
* wiki<br />
** RD wiki<br />
** ad hoc wikis<br />
* github repo<br />
* social networks (example: visualization that gets pushed throug twitter without it living anywhere specific)<br />
* email lists<br />
* physical archives<br />
* graffiti, stencil, street art, tattoos<br />
<br />
== Questions ==<br />
* how to track revisions?<br />
* how to make sure outputs created during the RDF can be shared for iterative collaboration?</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T08:23:36Z<p>Rdfwikiperson: </p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
RDFbuda<br />
<br />
responsibledata<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists / Farmer's Market ==<br />
This section is collecting all resources that come up during the <br />
<br />
[[Responsible data checklists: existing and wishing existed]] (Kristin)<br />
<br />
[[Wishlist]] <br />
<br />
[[Communities of practices]]<br />
<br />
[[Voices already talking about responsible data]]<br />
<br />
[[Upcoming events that should include responsible data]]<br />
<br />
[[Policies]] (Alix)<br />
<br />
<br />
== Day 2 morning conversations ==<br />
<br />
[[Packaging]]</div>Rdfwikipersonhttps://wiki.responsibledata.io/Main_PageMain Page2014-09-29T16:20:35Z<p>Rdfwikiperson: /* We are currently in Budapest for the RDF Budapest Resource Sprint. */</p>
<hr />
<div>'''Welcome to the Responsible Data Wiki!'''<br />
<br />
== [[RDF Budapest]] Resource Sprint. ==</div>Rdfwikipersonhttps://wiki.responsibledata.io/Main_PageMain Page2014-09-29T16:20:13Z<p>Rdfwikiperson: </p>
<hr />
<div>'''Welcome to the Responsible Data Wiki!'''<br />
<br />
== We are currently in Budapest for the [[RDF Budapest]] Resource Sprint. ==</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-09-29T16:17:43Z<p>Rdfwikiperson: </p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
== Information for facilitators ==<br />
Please make sure to send all notes and materials that are not already captured in the wiki to [mailto:notes@responsibledata.io notes@responsibledata.io]<br />
<br />
== Hashtags and Twitter accounts ==<br />
'''#RDFbuda'''<br />
<br />
'''#responsibledata'''<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists ==<br />
This section is collecting all resources that come up during the forum</div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-09-29T16:12:20Z<p>Rdfwikiperson: </p>
<hr />
<div>[[File:RDFvalidation.png|thumb]]<br />
This is a living page that is collecting information about the event as we are working on them.<br />
<br />
=== Hashtag ===<br />
'''#RDFbuda'''<br />
<br />
'''#responsibledata'''<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists ==<br />
This section is collecting all resources that come up during the forum</div>Rdfwikipersonhttps://wiki.responsibledata.io/File:RDFvalidation.pngFile:RDFvalidation.png2014-09-29T16:10:52Z<p>Rdfwikiperson: </p>
<hr />
<div></div>Rdfwikipersonhttps://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-09-29T16:08:31Z<p>Rdfwikiperson: </p>
<hr />
<div>This is a living page that is collecting information about the event as we are working on them.<br />
<br />
=== Hashtag ===<br />
'''#RDFbuda'''<br />
<br />
'''#responsibledata'''<br />
<br />
Twitter links:<br />
<br />
[https://twitter.com/engnroom @engnroom]<br />
[https://twitter.com/aspirationtech @aspirationtech]<br />
<br />
== Outputs ==<br />
<br />
[[Primer on responsible data in development]]<br />
<br />
[[Safety ranking system]]<br />
<br />
[[Atomized security plans for organizations]]<br />
<br />
[[Framework for consent policies]]<br />
<br />
[[Newbie guide to select hosting]]<br />
<br />
[[Digital first aid kit]]<br />
<br />
[[Resource creator manifesto]]<br />
<br />
[[Feeding harm stories and empirical data into policy making]]<br />
<br />
[[Opening government data]]<br />
<br />
[[Practical de-identification guide]]<br />
<br />
[[Data in the project lifecycle]]<br />
<br />
== Resource Lists ==<br />
This section is collecting all resources that come up during the forum</div>Rdfwikipersonhttps://wiki.responsibledata.io/MediaWiki:SidebarMediaWiki:Sidebar2014-09-29T16:05:43Z<p>Rdfwikiperson: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
<br />
* RDF Budapest<br />
** RDF Budapest|Main Page<br />
<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Rdfwikipersonhttps://wiki.responsibledata.io/MediaWiki:SidebarMediaWiki:Sidebar2014-09-29T16:03:47Z<p>Rdfwikiperson: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
<br />
* RDF Budapest<br />
** RDF Budapest|Main Page<br />
** Primer on responsible data in development|Primer on responsible data in development<br />
** Safety ranking system|Safety ranking system<br />
** Atomized security plans for organizations|Atomized security plans for organizations<br />
** Framework for consent policies|Framework for consent policies<br />
** Newbie guide to select hosting|Newbie guide to select hosting<br />
** Digital first aid kit|Digital first aid kit<br />
** Resource creator manifesto|Resource creator manifesto<br />
** Feeding harm stories and empirical data into policy making|Feeding harm stories and empirical data into policy making<br />
** Opening government data|Opening government data<br />
** Practical de-identification guide|Practical de-identification guide<br />
** Data in the project lifecycle|Data in the project lifecycle<br />
<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Rdfwikipersonhttps://wiki.responsibledata.io/MediaWiki:SidebarMediaWiki:Sidebar2014-09-29T16:03:32Z<p>Rdfwikiperson: </p>
<hr />
<div><br />
* navigation<br />
** mainpage|mainpage-description<br />
** recentchanges-url|recentchanges<br />
** randompage-url|randompage<br />
** helppage|help<br />
<br />
* RDF Budapest<br />
** RDF Budapest|'''Main Page'''<br />
** Primer on responsible data in development|Primer on responsible data in development<br />
** Safety ranking system|Safety ranking system<br />
** Atomized security plans for organizations|Atomized security plans for organizations<br />
** Framework for consent policies|Framework for consent policies<br />
** Newbie guide to select hosting|Newbie guide to select hosting<br />
** Digital first aid kit|Digital first aid kit<br />
** Resource creator manifesto|Resource creator manifesto<br />
** Feeding harm stories and empirical data into policy making|Feeding harm stories and empirical data into policy making<br />
** Opening government data|Opening government data<br />
** Practical de-identification guide|Practical de-identification guide<br />
** Data in the project lifecycle|Data in the project lifecycle<br />
<br />
* SEARCH<br />
* TOOLBOX<br />
* LANGUAGES</div>Rdfwikiperson