https://wiki.responsibledata.io/api.php?action=feedcontributions&user=Willowbl00&feedformat=atomResponsible Data Wiki - User contributions [en]2024-03-29T02:30:21ZUser contributionsMediaWiki 1.23.4https://wiki.responsibledata.io/Codesign_resources_for_human_rights_documentationCodesign resources for human rights documentation2016-04-01T18:42:31Z<p>Willowbl00: cleaned up language, added more links, etc</p>
<hr />
<div>This page is for you if you've ever thought "We're wondering why our tools aren't being used, or (hopefully) we're about to build one and we want to increase the likelihood that it will be useful to the end users."<br />
<br />
'''Problem''': Tool builders don't know how to speak to users, users don't know how to speak to developers.<br />
<br />
'''"Solution"''': As much as there's ever a "solution" to anything, there is an entire field of study and practice around participatory design, which not only sets your tool to be closer to what the end users actually need and want, but also increases their ownership of the process and end product. And who doesn't love more social justice in with their methods?<br />
<br />
==Costs and benefits==<br />
Participatory design is often considered expensive because it involves bringing designers and developers into the situation for which they're building. However, is this more or less expensive than building a tool which won't be used?<br />
===Commercial sector approach===<br />
[[File:UserInteractiveTesting.jpg|600px]]<br />
<br />
In the commercial sector, market research, A/B testing, etc is considered standard. It doesn't guarantee success, but it does increase the likelihood. In the commercial sector, money and views/clicks are how success of a tool can be judged. While the first hurdle is often just ''getting people to your platform/tool'', the next questions about where usability is falling down can be broken in to "buckets". This is called bucket funneling. An example would be Amazon with a cart and things to buy, you break out the process into buckets and see what happens in each bucket, and what is preventing people from doing what we want in each bucket?<br />
* Are people even coming to the website?<br />
* If people are putting things into the shopping cart, but not purchasing, is there something ugly about that process we need to fix?<br />
* Each bucket needs a metric and a baseline.<br />
** Can make a funnel for each of those buckets, dive down deeper<br />
* A/B testing is just about testing things with hundreds of users<br />
* User groups is about asking people to go through a process and then asking them how they felt about it, what stood out, etc<br />
* Paper prototyping works for both groups<br />
<br />
This assumes LOTS of users, computational power, resources. It also assumes an extractive mindset -- the business/organization has determined what they want you doing, and are optimizing for you following a path to that outcome.<br />
<br />
===Responsible data===<br />
This doesn't work when we care about privacy (we're not using cookies to track every click, time spent on a thing, etc). We also care about consent. What if we can't assume we know what people want (in a new field or with a new population), nor do we want to impose our view on them? We are working for overall justice and equality, not optimizing for clicks. We tend to care more about people being empowered more than us being right. Metrics for us are more difficult. It's not just about clicks or money. '''Impact''' is so nebulous and difficult to measure. We often frame our success instead as outcomes tracking impact. Outputs are tangible things (workshops, downloads, etc) but (hopefully) lead to outcomes. So how can we involve our end users in our process?<br />
<br />
Who owns the tool and process? In codesign, it's the end users who feel obligation and passion in seeing it succeed. Also creators should be making ourselves obsolete. <br />
<br />
==External resources==<br />
* '''[http://codesigntoolkit.com Codesign Toolkit]''' : an overview of codesign and participatory practices, along with academic literature, case studies, and workshop templates.<br />
* '''[http://facilitation.aspirationtech.org Aspiration Facilitation Wiki]''' : how to try to establish a co-equal space through facilitation practices<br />
* '''[http://internetfreedom.secondmuse.com/intro-to-the-needfinding-framework/ Internet freedom need finding framework]''' : <br />
* '''[http://climatecentre.org/games Climate Centre games resources]''' : games to discover system dynamics and design new local interventions related to extreme climate<br />
<br />
==Practitioners==<br />
===For Hire===<br />
* '''[http://aspirationtech.org Aspiration]''' : how to create common language and clear expectations across discipline backgrounds through participant guidelines at events<br />
* '''[https://labs.robinhood.org/about/ Blue Fin Labs]''' : working with at-risk user groups to broker interactions with developers for design sessions<br />
* '''[http://http://openideo.com OpenIDEO]''' : <br />
* '''[http://www.frogdesign.com/ Frog Design]''' : <br />
* '''[http://secondmuse.com/ Second Muse]''' : <br />
* '''[http://climatecentre.org Climate Centre]''' : <br />
* '''[http://www.luma-institute.com Luma Institute]''' : <br />
<br />
===To Learn From===<br />
* '''[http://codesign.mit.edu Codesign Studio at MIT]''' : class projects with community partners, reflections of materials<br />
* '''[http://http://usdac.us US Department of Arts and Culture]''' : active engagement frameworks for hyper-local groups around what creative acts they want happening in their communities.<br />
* '''[http://rhok.org Random Hacks of Kindness in some places]''' : brings in "subject matter experts" (aka "end users") to help developers and designers think through what to build related to disaster and humanitarian response.<br />
* '''[http://www.digital-democracy.org Digital Democracy]''' : works with local communities to discover their needs, primarily around environmental justice, and then to deliver tech systems to solve those needs in a way which is locally held<br />
* '''[http://blog.bl00cyb.org/2015/06/professorship/ Digital Communities Class]''' : used codesign methodologies to work with local partners in Providence, RI on digital projects.<br />
* '''[https://museoaerosolar.wordpress.com/ Museo Areo Solar]''' : works with local communities to build giant art projects out of trash bags as an examination of environmental impact and joyful futures.<br />
<br />
==Gaps==<br />
Been able to compensate people before, been able to colocate with people. Difference between a survey and codesign is that.<br />
<br />
There are some resources out there, but people ''get phds in this'', so it can seem difficult to make it happen on your own.<br />
<br />
Current interaction methods often don't consider informed consent.<br />
<br />
How to first find your groups to work with<br />
<br />
Core misunderstandings about what is true in a place (and that people don't know what to tell you about, because it's their lived experience).<br />
<br />
How much time you have -- if you have an hour-long workshop, the first 45 minutes will be installing a thing<br />
<br />
Have to close feedback loops -- respond to feedback, let people know they're heard, why something was dropped.<br />
: "What did you expect?" ... "Instead, what happened?"<br />
<br />
Do people have time to give you feedback? Build in time to iterate with people, workshop trainings as bug hunting as well. Then have people you've worked to train, train someone else.<br />
<br />
==Case Studies==<br />
Documenting some use cases and making a meta documentation. Format -- PDFs don't do well (but ''can'' be so pretty!)<br />
* Fab riders<br />
* IDEO</div>Willowbl00https://wiki.responsibledata.io/RDF-HRDRDF-HRD2016-04-01T18:25:41Z<p>Willowbl00: /* Working Groups */</p>
<hr />
<div>[[File:HRD.png|thumb]]<br />
This wiki was created for the participants of the Responsible Data on human rights documentation in San Francisco (2.0 of the [[RDF Manila]] event in March of 2015, also alongside RightsCon). We will use this for ongoing creating, sharing and collaborating.<br />
<br />
== Work Areas ==<br />
[[RDF-HRD_Experimentation | Experimenting with new tools and methods responsibly]] - when you '''don't''' have ability/access to alter the tool. <br><br />
[[RDF-HRD_Codesign | Participatory project and tool design and creation]] - when the users are the implementers (and potentially the creators). <br><br />
[[RDF-HRD_Tool_Selection | Knowing when to use (which) tool(s)]] - (building off [[Working Group on Tool Selection | a previous discussion]])<br><br />
[[RDF-HRD_Localization | Accessibility in language (and other localization thoughts]] <br><br />
[[RDF-HRD_Sustainability | Long-term considerations for tool development]] <br><br />
[[RDF-HRD_Use_Cases | Use cases]] <br><br />
<br />
==Working Groups==<br />
[[Codesign resources for human rights documentation]]<br />
<br />
==Aggregated Info==<br />
<br />
<br />
<br />
<br />
== Information for participants ==<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: #responsibledata #humanrights</div>Willowbl00https://wiki.responsibledata.io/Codesign_resources_for_human_rights_documentationCodesign resources for human rights documentation2016-03-29T22:32:33Z<p>Willowbl00: </p>
<hr />
<div>This page is for you if you've ever thought "We're wondering why our tools aren't being used, or we're about to build one and we want to increase the likelihood that it will be useful to the end users."<br />
<br />
'''Problem''': Tool builders don't know how to speak to users, users don't know how to speak to developers. <br />
<br />
==Costs and benefits==<br />
Bringing people places is expensive. (But is it more or less expensive than building a tool which doesn't fit?)<br />
===Commercial sector approach===<br />
[[File:UserInteractiveTesting.jpg|600px]]<br />
In the commercial sector, market research, A/B testing, etc is considered standard. It doesn't guarantee success, but it does increase the likelihood. Money, views/clicks. Besides getting people to the application, but like Amazon with a cart and things to buy, you break out the process into buckets and see what happens in each bucket, and what is preventing people from doing what we want in each bucket?<br />
* Are people even coming to the website?<br />
* If people are putting things into the shopping cart, but not purchasing, is there something ugly about that process we need to fix?<br />
* Each bucket needs a metric and a baseline.<br />
** Can make a funnel for each of those buckets, dive down deeper<br />
* A/B testing is just about testing things with hundreds of users<br />
* User groups is about asking people to go through a process and then asking them how they felt about it, what stood out, etc<br />
* Paper prototyping works for both groups<br />
<br />
This assumes LOTS of users, computational power, resources.<br />
<br />
===Responsible data===<br />
This doesn't work when we care about privacy (we're not using cookies). We also care about consent. We also tend to not think of our problems as tractable. What if we can't assume we know what people want (in a new field or with a new population), nor do we want to impose our view on them. We are working for overall justice and equality. We tend to care more about people being empowered more than us being right. Metrics for us are more difficult. It's not just about clicks or money. '''Impact''' is so nebulous and difficult to measure. Outcomes track impact. Outputs are tangible things (workshops, downloads, etc) but (hopefully) lead to outcomes.<br />
<br />
Who owns the tool and process? In codesign, it's the end users who feel obligation and passion in seeing it succeed. Also creators should be making ourselves obsolete. <br />
<br />
==External resources==<br />
* '''[http://codesigntoolkit.com Codesign Toolkit]''' : an overview of codesign and participatory practices, along with academic literature, case studies, and workshop templates.<br />
* '''[http://facilitation.aspirationtech.org Aspiration Facilitation Wiki]''' : how to try to establish a co-equal space through facilitation practices<br />
* '''[http://internetfreedom.secondmuse.com/intro-to-the-needfinding-framework/ Internet freedom need finding framework]''' : <br />
* '''[http://climatecentre.org/games Climate Centre games resources]''' : games to discover system dynamics and design new local interventions related to extreme climate<br />
<br />
==Practitioners==<br />
===For Hire===<br />
* '''[http://aspirationtech.org Aspiration]''' : : how to create common language and clear expectations across discipline backgrounds through participant guidelines at events.<br />
* '''[https://labs.robinhood.org/about/ Blue Fin Labs]''' : working with at-risk user groups to broker interactions with developers for design sessions<br />
* '''[http://http://openideo.com OpenIDEO]''' : <br />
* '''[http:// Frogg Design]''' : <br />
* '''[http:// Second Muse]''' : <br />
* '''[http:// Climate Centre]''' : <br />
<br />
===To Learn From===<br />
* '''[http://codesign.mit.edu Codesign Studio at MIT]''' : class projects with community partners, reflections of materials<br />
* '''[http:// Luma Institute]''' : <br />
* '''[http://http://usdac.us US Department of Arts and Culture]''' : active engagement frameworks for hyper-local groups around what creative acts they want happening in their communities.<br />
* '''[http://rhok.org Random Hacks of Kindness in some places]''' : brings in "subject matter experts" (aka "end users") to help developers and designers think through what to build related to disaster and humanitarian response.<br />
* '''[http://www.digital-democracy.org Digital Democracy]''' : works with local communities to discover their needs, primarily around environmental justice, and then to deliver tech systems to solve those needs in a way which is locally held<br />
* '''[http://blog.bl00cyb.org/2015/06/professorship/ Digital Communities Class]''' : used codesign methodologies to work with local partners in Providence, RI on digital projects.<br />
* '''[http:// Museo Areo Solar]''' : <br />
<br />
==Gaps==<br />
Been able to compensate people before, been able to colocate with people. Difference between a survey and codesign is that.<br />
<br />
There are some resources out there, but people ''get phds in this'', so it's difficult to make it happen on your own.<br />
<br />
Current interaction methods often don't consider informed consent.<br />
<br />
How to first find your groups to work with<br />
<br />
Core misunderstandings about what is true in a place (and that people don't know what to tell you about, because it's their lived experience).<br />
<br />
How much time you have -- if you have an hour-long workshop, the first 45 minutes will be installing a thing<br />
<br />
Have to close feedback loops -- respond to feedback, let people know they're heard, why something was dropped.<br />
"What did you expect?" ... "Instead, what happened?"<br />
<br />
Do people have time to give you feedback? Build in time to iterate with people, workshop trainings as bug hunting as well. Then have people you've worked to train, train someone else.<br />
<br />
==Case Studies==<br />
Documenting some use cases and making a meta documentation. Format -- PDFs don't do well (but ''can'' be so pretty!)<br />
* Fab riders<br />
* IDEO</div>Willowbl00https://wiki.responsibledata.io/Codesign_resources_for_human_rights_documentationCodesign resources for human rights documentation2016-03-29T22:31:52Z<p>Willowbl00: </p>
<hr />
<div>This page is for you if you've ever thought "We're wondering why our tools aren't being used, or we're about to build one and we want to increase the likelihood that it will be useful to the end users."<br />
<br />
'''Problem''': Tool builders don't know how to speak to users, users don't know how to speak to developers. <br />
<br />
==Costs and benefits==<br />
Bringing people places is expensive. (But is it more or less expensive than building a tool which doesn't fit?)<br />
===Commercial sector approach===<br />
[[File:UserInteractiveTesting.jpg]]<br />
In the commercial sector, market research, A/B testing, etc is considered standard. It doesn't guarantee success, but it does increase the likelihood. Money, views/clicks. Besides getting people to the application, but like Amazon with a cart and things to buy, you break out the process into buckets and see what happens in each bucket, and what is preventing people from doing what we want in each bucket?<br />
* Are people even coming to the website?<br />
* If people are putting things into the shopping cart, but not purchasing, is there something ugly about that process we need to fix?<br />
* Each bucket needs a metric and a baseline.<br />
** Can make a funnel for each of those buckets, dive down deeper<br />
* A/B testing is just about testing things with hundreds of users<br />
* User groups is about asking people to go through a process and then asking them how they felt about it, what stood out, etc<br />
* Paper prototyping works for both groups<br />
<br />
This assumes LOTS of users, computational power, resources.<br />
<br />
===Responsible data===<br />
This doesn't work when we care about privacy (we're not using cookies). We also care about consent. We also tend to not think of our problems as tractable. What if we can't assume we know what people want (in a new field or with a new population), nor do we want to impose our view on them. We are working for overall justice and equality. We tend to care more about people being empowered more than us being right. Metrics for us are more difficult. It's not just about clicks or money. '''Impact''' is so nebulous and difficult to measure. Outcomes track impact. Outputs are tangible things (workshops, downloads, etc) but (hopefully) lead to outcomes.<br />
<br />
Who owns the tool and process? In codesign, it's the end users who feel obligation and passion in seeing it succeed. Also creators should be making ourselves obsolete. <br />
<br />
==External resources==<br />
* '''[http://codesigntoolkit.com Codesign Toolkit]''' : an overview of codesign and participatory practices, along with academic literature, case studies, and workshop templates.<br />
* '''[http://facilitation.aspirationtech.org Aspiration Facilitation Wiki]''' : how to try to establish a co-equal space through facilitation practices<br />
* '''[http://internetfreedom.secondmuse.com/intro-to-the-needfinding-framework/ Internet freedom need finding framework]''' : <br />
* '''[http://climatecentre.org/games Climate Centre games resources]''' : games to discover system dynamics and design new local interventions related to extreme climate<br />
<br />
==Practitioners==<br />
===For Hire===<br />
* '''[http://aspirationtech.org Aspiration]''' : : how to create common language and clear expectations across discipline backgrounds through participant guidelines at events.<br />
* '''[https://labs.robinhood.org/about/ Blue Fin Labs]''' : working with at-risk user groups to broker interactions with developers for design sessions<br />
* '''[http://http://openideo.com OpenIDEO]''' : <br />
* '''[http:// Frogg Design]''' : <br />
* '''[http:// Second Muse]''' : <br />
* '''[http:// Climate Centre]''' : <br />
<br />
===To Learn From===<br />
* '''[http://codesign.mit.edu Codesign Studio at MIT]''' : class projects with community partners, reflections of materials<br />
* '''[http:// Luma Institute]''' : <br />
* '''[http://http://usdac.us US Department of Arts and Culture]''' : active engagement frameworks for hyper-local groups around what creative acts they want happening in their communities.<br />
* '''[http://rhok.org Random Hacks of Kindness in some places]''' : brings in "subject matter experts" (aka "end users") to help developers and designers think through what to build related to disaster and humanitarian response.<br />
* '''[http://www.digital-democracy.org Digital Democracy]''' : works with local communities to discover their needs, primarily around environmental justice, and then to deliver tech systems to solve those needs in a way which is locally held<br />
* '''[http://blog.bl00cyb.org/2015/06/professorship/ Digital Communities Class]''' : used codesign methodologies to work with local partners in Providence, RI on digital projects.<br />
* '''[http:// Museo Areo Solar]''' : <br />
<br />
==Gaps==<br />
Been able to compensate people before, been able to colocate with people. Difference between a survey and codesign is that.<br />
<br />
There are some resources out there, but people ''get phds in this'', so it's difficult to make it happen on your own.<br />
<br />
Current interaction methods often don't consider informed consent.<br />
<br />
How to first find your groups to work with<br />
<br />
Core misunderstandings about what is true in a place (and that people don't know what to tell you about, because it's their lived experience).<br />
<br />
How much time you have -- if you have an hour-long workshop, the first 45 minutes will be installing a thing<br />
<br />
Have to close feedback loops -- respond to feedback, let people know they're heard, why something was dropped.<br />
"What did you expect?" ... "Instead, what happened?"<br />
<br />
Do people have time to give you feedback? Build in time to iterate with people, workshop trainings as bug hunting as well. Then have people you've worked to train, train someone else.<br />
<br />
==Case Studies==<br />
Documenting some use cases and making a meta documentation. Format -- PDFs don't do well (but ''can'' be so pretty!)<br />
* Fab riders<br />
* IDEO</div>Willowbl00https://wiki.responsibledata.io/File:UserInteractiveTesting.jpgFile:UserInteractiveTesting.jpg2016-03-29T22:31:22Z<p>Willowbl00: When considering how to work with your end users, there are several ways of setting up flow, metrics, and assessment.</p>
<hr />
<div>When considering how to work with your end users, there are several ways of setting up flow, metrics, and assessment.</div>Willowbl00https://wiki.responsibledata.io/Codesign_resources_for_human_rights_documentationCodesign resources for human rights documentation2016-03-29T22:30:19Z<p>Willowbl00: Created page with "This page is for you if you've ever thought "We're wondering why our tools aren't being used, or we're about to build one and we want to increase the likelihood that it will b..."</p>
<hr />
<div>This page is for you if you've ever thought "We're wondering why our tools aren't being used, or we're about to build one and we want to increase the likelihood that it will be useful to the end users."<br />
<br />
'''Problem''': Tool builders don't know how to speak to users, users don't know how to speak to developers. <br />
<br />
==Costs and benefits==<br />
Bringing people places is expensive. (But is it more or less expensive than building a tool which doesn't fit?)<br />
===Commercial sector approach===<br />
In the commercial sector, market research, A/B testing, etc is considered standard. It doesn't guarantee success, but it does increase the likelihood. Money, views/clicks. Besides getting people to the application, but like Amazon with a cart and things to buy, you break out the process into buckets and see what happens in each bucket, and what is preventing people from doing what we want in each bucket?<br />
* Are people even coming to the website?<br />
* If people are putting things into the shopping cart, but not purchasing, is there something ugly about that process we need to fix?<br />
* Each bucket needs a metric and a baseline.<br />
** Can make a funnel for each of those buckets, dive down deeper<br />
* A/B testing is just about testing things with hundreds of users<br />
* User groups is about asking people to go through a process and then asking them how they felt about it, what stood out, etc<br />
* Paper prototyping works for both groups<br />
<br />
This assumes LOTS of users, computational power, resources.<br />
<br />
===Responsible data===<br />
This doesn't work when we care about privacy (we're not using cookies). We also care about consent. We also tend to not think of our problems as tractable. What if we can't assume we know what people want (in a new field or with a new population), nor do we want to impose our view on them. We are working for overall justice and equality. We tend to care more about people being empowered more than us being right. Metrics for us are more difficult. It's not just about clicks or money. '''Impact''' is so nebulous and difficult to measure. Outcomes track impact. Outputs are tangible things (workshops, downloads, etc) but (hopefully) lead to outcomes.<br />
<br />
Who owns the tool and process? In codesign, it's the end users who feel obligation and passion in seeing it succeed. Also creators should be making ourselves obsolete. <br />
<br />
==External resources==<br />
* '''[http://codesigntoolkit.com Codesign Toolkit]''' : an overview of codesign and participatory practices, along with academic literature, case studies, and workshop templates.<br />
* '''[http://facilitation.aspirationtech.org Aspiration Facilitation Wiki]''' : how to try to establish a co-equal space through facilitation practices<br />
* '''[http://internetfreedom.secondmuse.com/intro-to-the-needfinding-framework/ Internet freedom need finding framework]''' : <br />
* '''[http://climatecentre.org/games Climate Centre games resources]''' : games to discover system dynamics and design new local interventions related to extreme climate<br />
<br />
==Practitioners==<br />
===For Hire===<br />
* '''[http://aspirationtech.org Aspiration]''' : : how to create common language and clear expectations across discipline backgrounds through participant guidelines at events.<br />
* '''[https://labs.robinhood.org/about/ Blue Fin Labs]''' : working with at-risk user groups to broker interactions with developers for design sessions<br />
* '''[http://http://openideo.com OpenIDEO]''' : <br />
* '''[http:// Frogg Design]''' : <br />
* '''[http:// Second Muse]''' : <br />
* '''[http:// Climate Centre]''' : <br />
<br />
===To Learn From===<br />
* '''[http://codesign.mit.edu Codesign Studio at MIT]''' : class projects with community partners, reflections of materials<br />
* '''[http:// Luma Institute]''' : <br />
* '''[http://http://usdac.us US Department of Arts and Culture]''' : active engagement frameworks for hyper-local groups around what creative acts they want happening in their communities.<br />
* '''[http://rhok.org Random Hacks of Kindness in some places]''' : brings in "subject matter experts" (aka "end users") to help developers and designers think through what to build related to disaster and humanitarian response.<br />
* '''[http://www.digital-democracy.org Digital Democracy]''' : works with local communities to discover their needs, primarily around environmental justice, and then to deliver tech systems to solve those needs in a way which is locally held<br />
* '''[http://blog.bl00cyb.org/2015/06/professorship/ Digital Communities Class]''' : used codesign methodologies to work with local partners in Providence, RI on digital projects.<br />
* '''[http:// Museo Areo Solar]''' : <br />
<br />
==Gaps==<br />
Been able to compensate people before, been able to colocate with people. Difference between a survey and codesign is that.<br />
<br />
There are some resources out there, but people ''get phds in this'', so it's difficult to make it happen on your own.<br />
<br />
Current interaction methods often don't consider informed consent.<br />
<br />
How to first find your groups to work with<br />
<br />
Core misunderstandings about what is true in a place (and that people don't know what to tell you about, because it's their lived experience).<br />
<br />
How much time you have -- if you have an hour-long workshop, the first 45 minutes will be installing a thing<br />
<br />
Have to close feedback loops -- respond to feedback, let people know they're heard, why something was dropped.<br />
"What did you expect?" ... "Instead, what happened?"<br />
<br />
Do people have time to give you feedback? Build in time to iterate with people, workshop trainings as bug hunting as well. Then have people you've worked to train, train someone else.<br />
<br />
==Case Studies==<br />
Documenting some use cases and making a meta documentation. Format -- PDFs don't do well (but ''can'' be so pretty!)<br />
* Fab riders<br />
* IDEO</div>Willowbl00https://wiki.responsibledata.io/RDF-HRD_CodesignRDF-HRD Codesign2016-03-29T21:25:02Z<p>Willowbl00: /* Where to from here? */</p>
<hr />
<div>Breakout discussion group at [[RDF-HRD | RDF Human rights documentation at RightsCon]] in SF March 2016<br />
<br />
==Why are you here?==<br />
* Working on participatory methods for tool building, but there's always a "where to exit?" "how to evaluate?" questions. How can we build tools around it? How should we be thinking of things? Considering risk factors, who to work with, etc<br />
* Came from for-profit world, participatory design was well-defined to maximize profit or reduce time. A-B testing. How do you judge your impact? What are you trying to maximize? How can you tell if something is successful?<br />
* Want to engage in a participatory process to understand how human rights defenders, specifically in Latin America, aren't using the tools which exist right now.<br />
* Multistakeholder, crowd sourced for ideas -- gov, private sector, etc. But want to evaluate how different stakeholders participate.<br />
* We build those tools, interested to see the other side's perspective (and also someone in the same boat but experiencing it differently).<br />
<br />
==Discussion==<br />
People are not sitting down with end users and asking them what they want. The things that we built for ourselves work<br />
<br />
We're showing up with pre-made tools, and then wondering why people aren't using them. We spent a lot of money building them. Do people not know about them? Is it too expensive? Not usable? Or are we building the wrong things? Everything is '''so''' contextual -- how can we ''possibly'' build something which will be useful in many different contexts?<br />
<br />
Who are we designing the tool for? Martus was built for people who are ''incredibly'' at risk -- the 1-5%. But we want to make it for the next 45% are able to use and communicate with others. How broadly do we want to design this?<br />
* How do we identify our users? There are human rights defenders all over.<br />
<br />
Failure -- commercial software also fails '''a lot'''. Cultural aspect is important, but maybe this is also about failing responsibility when working closely with a community. Working in a participatory way is expensive.<br />
<br />
If you design well, it's often a super simple implementation. Minimum technology maximally applied.<br />
<br />
==Where to from here?==<br />
* <strike>Do you need participatory design, and how to implement?</strike> - many already exist. Analysis of them is fine, or tweaking [http://www.codesigntoolkit.com what exists].<br />
* Case study on what goals might be, align to contexts, determining if you should implement an existing tool or design and create a new one<br />
* '''[[Codesign resources for human rights documentation | Build a resource list]]'''?<br />
* How do I attract users to be a part of the process? How do I explain myself, ask them to invest their time? Get people to be honest about it being a bad idea etc.<br />
* Examining what exists, selecting, filling gaps, getting human rights defenders to start using those tools.</div>Willowbl00https://wiki.responsibledata.io/RDF-HRD_CodesignRDF-HRD Codesign2016-03-29T20:18:13Z<p>Willowbl00: call notes</p>
<hr />
<div>Breakout discussion group at [[RDF-HRD | RDF Human rights documentation at RightsCon]] in SF March 2016<br />
<br />
==Why are you here?==<br />
* Working on participatory methods for tool building, but there's always a "where to exit?" "how to evaluate?" questions. How can we build tools around it? How should we be thinking of things? Considering risk factors, who to work with, etc<br />
* Came from for-profit world, participatory design was well-defined to maximize profit or reduce time. A-B testing. How do you judge your impact? What are you trying to maximize? How can you tell if something is successful?<br />
* Want to engage in a participatory process to understand how human rights defenders, specifically in Latin America, aren't using the tools which exist right now.<br />
* Multistakeholder, crowd sourced for ideas -- gov, private sector, etc. But want to evaluate how different stakeholders participate.<br />
* We build those tools, interested to see the other side's perspective (and also someone in the same boat but experiencing it differently).<br />
<br />
==Discussion==<br />
People are not sitting down with end users and asking them what they want. The things that we built for ourselves work<br />
<br />
We're showing up with pre-made tools, and then wondering why people aren't using them. We spent a lot of money building them. Do people not know about them? Is it too expensive? Not usable? Or are we building the wrong things? Everything is '''so''' contextual -- how can we ''possibly'' build something which will be useful in many different contexts?<br />
<br />
Who are we designing the tool for? Martus was built for people who are ''incredibly'' at risk -- the 1-5%. But we want to make it for the next 45% are able to use and communicate with others. How broadly do we want to design this?<br />
* How do we identify our users? There are human rights defenders all over.<br />
<br />
Failure -- commercial software also fails '''a lot'''. Cultural aspect is important, but maybe this is also about failing responsibility when working closely with a community. Working in a participatory way is expensive.<br />
<br />
If you design well, it's often a super simple implementation. Minimum technology maximally applied.<br />
<br />
==Where to from here?==<br />
* <strike>Do you need participatory design, and how to implement?</strike> - many already exist. Analysis of them is fine, or tweaking [http://www.codesigntoolkit.com what exists].<br />
* Case study on what goals might be, align to contexts, determining if you should implement an existing tool or design and create a new one<br />
* Build a resource list?<br />
* How do I attract users to be a part of the process? How do I explain myself, ask them to invest their time? Get people to be honest about it being a bad idea etc.<br />
* Examining what exists, selecting, filling gaps, getting human rights defenders to start using those tools.</div>Willowbl00https://wiki.responsibledata.io/RDF-HRDRDF-HRD2016-03-29T19:43:48Z<p>Willowbl00: /* Work Areas */</p>
<hr />
<div>[[File:HRD.png|thumb]]<br />
This wiki was created for the participants of the Responsible Data on human rights documentation in San Francisco (2.0 of the [[RDF Manila]] event in March of 2015, also alongside RightsCon). We will use this for ongoing creating, sharing and collaborating.<br />
<br />
== Work Areas ==<br />
[[RDF-HRD_Experimentation | Experimenting with new tools and methods responsibly]] - when you '''don't''' have ability/access to alter the tool. <br><br />
[[RDF-HRD_Codesign | Participatory project and tool design and creation]] - when the users are the implementers (and potentially the creators). <br><br />
[[RDF-HRD_Tool_Selection | Knowing when to use (which) tool(s)]] - (building off [[Working Group on Tool Selection | a previous discussion]])<br><br />
[[RDF-HRD_Localization | Accessibility in language (and other localization thoughts]] <br><br />
[[RDF-HRD_Sustainability | Long-term considerations for tool development]] <br><br />
[[RDF-HRD_Use_Cases | Use cases]] <br><br />
<br />
==Working Groups==<br />
<br />
==Aggregated Info==<br />
<br />
<br />
<br />
<br />
== Information for participants ==<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: #responsibledata #humanrights</div>Willowbl00https://wiki.responsibledata.io/RDF-HRDRDF-HRD2016-03-29T19:43:30Z<p>Willowbl00: /* Work Areas */</p>
<hr />
<div>[[File:HRD.png|thumb]]<br />
This wiki was created for the participants of the Responsible Data on human rights documentation in San Francisco (2.0 of the [[RDF Manila]] event in March of 2015, also alongside RightsCon). We will use this for ongoing creating, sharing and collaborating.<br />
<br />
== Work Areas ==<br />
[[RDF-HRD_Experimentation | Experimenting with new tools and methods responsibly]] - when you '''don't''' have ability/access to alter the tool. <br><br />
[[RDF-HRD_Codesign | Participatory project and tool design and creation]] - when the users are the implementers (and potentially the creators). <br><br />
[[RDF-HRD_Tool_Selection | Knowing when to use (which) tool(s)]] - (building off [[Working Group on Tool Selection | a previous discussion]]<br><br />
[[RDF-HRD_Localization | Accessibility in language (and other localization thoughts]] <br><br />
[[RDF-HRD_Sustainability | Long-term considerations for tool development]] <br><br />
[[RDF-HRD_Use_Cases | Use cases]] <br><br />
<br />
==Working Groups==<br />
<br />
==Aggregated Info==<br />
<br />
<br />
<br />
<br />
== Information for participants ==<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: #responsibledata #humanrights</div>Willowbl00https://wiki.responsibledata.io/RDF-HRDRDF-HRD2016-03-29T19:39:20Z<p>Willowbl00: /* Work Areas */</p>
<hr />
<div>[[File:HRD.png|thumb]]<br />
This wiki was created for the participants of the Responsible Data on human rights documentation in San Francisco (2.0 of the [[RDF Manila]] event in March of 2015, also alongside RightsCon). We will use this for ongoing creating, sharing and collaborating.<br />
<br />
== Work Areas ==<br />
[[RDF-HRD_Experimentation | Experimenting with new tools and methods responsibly]] - when you '''don't''' have ability/access to alter the tool. <br><br />
[[RDF-HRD_Codesign | Participatory project and tool design and creation]] - when the users are the implementers (and potentially the creators). <br><br />
[[RDF-HRD_Tool_Selection | Knowing when to use (which) tool(s)]] - (building off [[Working Group on Tool Selection | a previous discussion]]<br><br />
[[RDF-HRD_Localization | Accessibility in language (and other localization thoughts]] <br><br />
[[RDF-HRD_Sustainability | Long-term considerations for tool development]] <br><br />
<br />
==Working Groups==<br />
<br />
==Aggregated Info==<br />
<br />
<br />
<br />
<br />
== Information for participants ==<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: #responsibledata #humanrights</div>Willowbl00https://wiki.responsibledata.io/RDF-HRDRDF-HRD2016-03-29T19:37:58Z<p>Willowbl00: /* Work Areas */</p>
<hr />
<div>[[File:HRD.png|thumb]]<br />
This wiki was created for the participants of the Responsible Data on human rights documentation in San Francisco (2.0 of the [[RDF Manila]] event in March of 2015, also alongside RightsCon). We will use this for ongoing creating, sharing and collaborating.<br />
<br />
== Work Areas ==<br />
[[RDF-HRD_Experimentation | Experimenting with new tools and methods responsibly]] - when you '''don't''' have ability/access to alter the tool. <br><br />
[[RDF-HRD_Codesign | Participatory project and tool design and creation]] - when the users are the implementers (and potentially the creators). <br><br />
[[RDF-HRD_Tool_Selection | Knowing when to use (which) tool(s)]] <br><br />
[[RDF-HRD_Localization | Accessibility in language (and other localization thoughts]] <br><br />
[[RDF-HRD_Sustainability | Long-term considerations for tool development]] <br><br />
<br />
==Working Groups==<br />
<br />
==Aggregated Info==<br />
<br />
<br />
<br />
<br />
== Information for participants ==<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: #responsibledata #humanrights</div>Willowbl00https://wiki.responsibledata.io/User:Willowbl00User:Willowbl002016-03-29T15:29:33Z<p>Willowbl00: </p>
<hr />
<div>[[File:Willowbl00 drawing at TOG.jpg|thumb]]<br />
Community Leadership Strategist at [http://aspirationtech.org Aspiration]<br />
<br />
On the Internet:<br />
* [http://blog.bl00cyb.org Blog]<br />
* [http://viz.bl00cyb.org VizThink Catalogue]<br />
* [http://twitter.com/willowbl00 Twitter]<br />
etc. willowbl00 nearly anywhere.<br />
<br />
The drawings posted here I do mainly in Adobe Ideas on iPad. You can see the whole process [http://viz.bl00cyb.org/how-do-you-do-that/ here].</div>Willowbl00https://wiki.responsibledata.io/RDF-HRDRDF-HRD2016-03-29T15:28:33Z<p>Willowbl00: Created page with "thumb This wiki was created for the participants of the Responsible Data on human rights documentation in San Francisco (2.0 of the RDF Manila event in Ma..."</p>
<hr />
<div>[[File:HRD.png|thumb]]<br />
This wiki was created for the participants of the Responsible Data on human rights documentation in San Francisco (2.0 of the [[RDF Manila]] event in March of 2015, also alongside RightsCon). We will use this for ongoing creating, sharing and collaborating.<br />
<br />
== Work Areas ==<br />
<br />
==Working Groups==<br />
<br />
==Aggregated Info==<br />
<br />
<br />
<br />
<br />
== Information for participants ==<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: #responsibledata #humanrights</div>Willowbl00https://wiki.responsibledata.io/Main_PageMain Page2016-03-29T15:22:51Z<p>Willowbl00: /* Responsible Data Forums: */</p>
<hr />
<div>Welcome to the Responsible Data Forum wiki! We will use this space to collaborate on resources that help practitioners implement responsible data practices.<br />
<br />
What's responsible data? The responsible data community has developed a working definition. We have defined it as:<br />
<br />
The duty to ensure people's right to consent, privacy, security, and ownership around information processes of collection, analysis, storage, presentation and reuse of data, while respecting the values of transparency and openness. <br />
<br />
= Responsible Data Forums: =<br />
<br />
[[File:RDFvalidation.png|border|x50px]] [[RDF_Budapest | Responsible Data Resource Sprint]] - Budapest, September 30 to October 1, 2014<br />
<br />
[[File:RDFconsent.png|border|x50px]] [[RDF_Nairobi | Responsible Data in Consent and Crowdsourcing ]] - Nairobi, October 28, 2014<br />
<br />
[[File:HRD.png|border|x50px]] [[RDF_Manila | Responsible Data on Human Rights Documentation ]] - Manila, March 21 to 22, 2015<br />
<br />
[[File:RDF-photo.png|border|x50px]] [[RDLab_Photo | Responsible Data Lab on Documentary Photography ]] - New York, March 28, 2015<br />
<br />
[[File:RDFVIZ-icon.png|border|x50px]] [[Rdfviz | Responsible Data Forum on data visualization ]] - New York, January 15, 2016<br />
<br />
[[File:RDF-IHRFG.png|border|x50px]] [[RDF-IHRFG | Responsible Data Forum on human rights funders ]] - San Francisco, January 19, 2016<br />
<br />
[[File:HRD.png|border|x50px]] [[RDF-HRD | Responsible Data Forum on human rights documentation at RightsCon]] - San Francisco, March 29, 2016<br />
<br />
= Responsible Data Discussions: =<br />
<br />
[[File:Convo_bubbles.jpeg|x30px]] '''[https://responsibledata.io/discussion-on-the-risks-and-mitigations-of-releasing-data/ Discussion on the risks and mitigations of releasing data]''' <br />
<br />
Join us Wednesday, August 26 at 10am EDT to discuss the risks and mitigations of releasing data. Sara-Jayne Terp, Data Scientist at Thoughtworks, and formerly Director of Data Projects at Ushahidi, will serve as the fire-starter and facilitator for this discussion.<br />
<br />
>> [[Instructions to join the RDF online discussion | Instructions on how to join this event]]. <br />
<br />
Looking for past events? Here is a [[Responsible Data Hangouts | list of our past Responsible Data discussions]].<br />
<br />
= Responsible Data Resource Wiki Pages: =<br />
<br />
[[Responsible data storytelling index of resources | Responsible data storytelling index of resources]]<br />
<br />
<br />
----<br />
<br />
For more information on the Responsible Data Forum, visit our [https://responsibledata.io/ website].</div>Willowbl00https://wiki.responsibledata.io/Main_PageMain Page2016-03-29T15:22:23Z<p>Willowbl00: /* Responsible Data Forums: */</p>
<hr />
<div>Welcome to the Responsible Data Forum wiki! We will use this space to collaborate on resources that help practitioners implement responsible data practices.<br />
<br />
What's responsible data? The responsible data community has developed a working definition. We have defined it as:<br />
<br />
The duty to ensure people's right to consent, privacy, security, and ownership around information processes of collection, analysis, storage, presentation and reuse of data, while respecting the values of transparency and openness. <br />
<br />
= Responsible Data Forums: =<br />
<br />
[[File:RDFvalidation.png|border|x50px]] [[RDF_Budapest | Responsible Data Resource Sprint]] - Budapest, September 30 to October 1, 2014<br />
<br />
[[File:RDFconsent.png|border|x50px]] [[RDF_Nairobi | Responsible Data in Consent and Crowdsourcing ]] - Nairobi, October 28, 2014<br />
<br />
[[File:HRD.png|border|x50px]] [[RDF_Manila | Responsible Data on Human Rights Documentation ]] - Manila, March 21 to 22, 2015<br />
<br />
[[File:RDF-photo.png|border|x50px]] [[RDLab_Photo | Responsible Data Lab on Documentary Photography ]] - New York, March 28, 2015<br />
<br />
[[File:RDFVIZ-icon.png|border|x50px]] [[Rdfviz | Responsible Data Forum on data visualization ]] - New York, January 15, 2016<br />
<br />
[[File:RDF-IHRFG.png|border|x50px]] [[RDF-IHRFG | Responsible Data Forum on human rights funders ]] - San Francisco, January 19, 2016<br />
<br />
[[RDF-HRD | Responsible Data Forum on human rights documentation at RightsCon]] - San Francisco, March 29, 2016<br />
<br />
= Responsible Data Discussions: =<br />
<br />
[[File:Convo_bubbles.jpeg|x30px]] '''[https://responsibledata.io/discussion-on-the-risks-and-mitigations-of-releasing-data/ Discussion on the risks and mitigations of releasing data]''' <br />
<br />
Join us Wednesday, August 26 at 10am EDT to discuss the risks and mitigations of releasing data. Sara-Jayne Terp, Data Scientist at Thoughtworks, and formerly Director of Data Projects at Ushahidi, will serve as the fire-starter and facilitator for this discussion.<br />
<br />
>> [[Instructions to join the RDF online discussion | Instructions on how to join this event]]. <br />
<br />
Looking for past events? Here is a [[Responsible Data Hangouts | list of our past Responsible Data discussions]].<br />
<br />
= Responsible Data Resource Wiki Pages: =<br />
<br />
[[Responsible data storytelling index of resources | Responsible data storytelling index of resources]]<br />
<br />
<br />
----<br />
<br />
For more information on the Responsible Data Forum, visit our [https://responsibledata.io/ website].</div>Willowbl00https://wiki.responsibledata.io/EbolaABigDataDisasterEbolaABigDataDisaster2016-03-17T18:16:12Z<p>Willowbl00: Created page with ": For years, disaster and humanitarian response technologists, field agents, and policy makers have been pushing big data as a way to be self-reflexive and open data as a way..."</p>
<hr />
<div>: For years, disaster and humanitarian response technologists, field agents, and policy makers have been pushing big data as a way to be self-reflexive and open data as a way to break down the silos rife throughout the sector. While folk tend to talk a lot about ethics and responsibility in response and data, we rarely talk about law (which is those things codified). Ebola response was one more time for organizations, funders, and those affected to wonder what role data would play in their response, and the repercussions of those choices after the response was declared complete. Sean McDonald posted [http://cis-india.org/papers/ebola-a-big-data-disaster his paper Ebola: A Big Data Disaster] to the Responsible Data list, and it spurred a deep conversation about ''what'' data should be shared, how practioners who are also open data advocates make hard choices in pressing circumstances. We were all so excited that it made sense to have a real-time conversation about the topic.<br />
<br />
==Call Details==<br />
: March 15th 8 a.m. PST, 11 a.m. EDT, 3 p.m. GMT, 5 p.m. CET, 6 p.m. EAT<br />
: Hangout on air broadcast link: https://plus.google.com/events/cekgergp643cet3u834qfcf3qu4<br />
: Youtube link (live and recorded access): http://youtu.be/xcczOMLQBJM<br />
<br />
===Attendees===<br />
* Danna, engine room<br />
* Jen, HHI, NetHope<br />
* John, HHI, Global Pulse<br />
* Sean, Frontline SMS<br />
* Tim, O'Reilly<br />
* Zara, engine room<br />
* Willow, Aspiration<br />
* Paul C<br />
<br />
==Suggested reading==<br />
* http://cis-india.org/papers/ebola-a-big-data-disaster<br />
* http://datapopalliance.org/item/white-paper-the-law-politics-and-ethics-of-cell-phone-data-analytics/<br />
* http://odimpact.org/case-battling-ebola-in-sierra-leone.html<br />
<br />
==Review of the paper, how it instigated a conversation==<br />
Ebola: A Big Data Disaster is a brief history of the role tech played in the ebola crisis. Institutional concern, particularly around how info systems became a central actor. A percieved lack of good information led some intelligent, well meaning people to release call-detail records. Some of our most sensitive data. Vary in accuracy depending on source and external circumstances. <br />
<br />
An attempt to use data to scale contact tracing: valuable, but difficult to represent digitally. Danah Boyd asks "what is th edirection of this space?" Fighting the ecosystem prediction. Using how it's designed to harm, but these tools are designed to be helpful. Positive uses exist alongside terrifying uses. <br />
<br />
danna boyd: "Many activists will be looking to fight the ecosystem of prediction — and to regulate when and where prediction can be used. This is all fine and well when we’re talking about how these technologies are designed to do harm. But more often than not, these tools will be designed to be helpful, to increase efficiency, to identify people who need help. Their positive uses will exist alongside uses that are terrifying. What do we do?"<br />
<br />
"Technology is neither good nor bad... nor is it neutral. Mandated quarentine. That's scary!<br />
Practical and terrifying outcome is predictive quarantine. <br />
<br />
We talk a lot about ethics and responsibility, but what we rarely talk about is law. We have ways to police and prevent. Those are being catagorically ignored. Innovation + disruption = HOORAY. But wait. Lots of experimentation, transparency, accountability that needs to go into this practice area.<br />
<br />
===Feedback:===<br />
* Danna: Big gap: understanding legal framework, understanding how to act within the law as well as "ethically" adn "responsibly". Looking across legal jurisdictions becomes difficult.<br />
* Jen: Understanding and knowing the legal frameworks are super important. Staff face being pulled in so many directions! Legal frameworks are 45 pages long. How do I take something, hand it off to the team to bring it back, make it practical. Make it feel more feasible to integrate it. Open up the hood - we don't have a good playbook, but take the first steps to do so.<br />
* John: did work with World Bank on GeoNode. Including a legal person rarely happens. Learned that lesson the hard way. - leading research into UAVs, etc. Having lawyers into this function is something that enables the tech to find a lane that is possible to do, and legal. Other framing: lawyers need to know exact use case and how it will be applied in practice. Many technologies - eg. release of CDRs - don't get narrowed down enough. We need to be able to explain to a lawyer how exactly the data will contribute to a specific function (eg. contract tracing to send people a message on a phone?) - the modality matters. <br />
* Tim: Two things pushing the groups to ignore the law. "Disruption" and state of emergency. The culture of disruption. See also [https://theconversation.com/can-innovators-build-a-future-thats-both-disruptive-and-just-49871 Can innovators build a future that is both disruptive and just?]<br />
: idea that law is hard - doesn't mean that it's slow (or not useful!). Orgs competing for resources - looking to say "we're the go to org" for the next project, so it's imperative to come out well. Practicalities of laying out that we're getting resource X and it's going to lead to outcome Y - having a realistic notion that we're going to use things for this particular use. Purpose specificity isn't new but it's just as important. <br />
* Zara: The rush to do something, and the blind faith in "more data is better" in a situation where it's hard to argue against it (like Ebola). You're not going to make it worse, so... Implementing agencies versus just doing it with what you've got.<br />
* Willow: Lots of people who have been working on data sharing etc for YEARS. Worried that this will become a feather in the hat of people pushing against 'data sharing' <br />
<br />
==What did implementing in the Ebola context look like? Where and why were exceptions made?==<br />
If you look at individual medical records, quality metrics, it's decades of HIPPA policies and training. Patient-provider level. Policy, privacy, people. People are the central part. Can see why it's so complicated, we still make mistakes.<br />
Decades of training at the national level. <br />
<br />
==Existing open data efforts==<br />
''Many people have been working on the open data and coordination issues of disaster response for awhile. Why is this important? Are those efforts not enough? Are they incorrect? What's happening here?''<br />
The notion of call details in general is terrifying. <br />
<br />
Worked with them extensively at Global Pulse - element of creating a space to analyse CDR is usually related to analysing them for a specific purpose. Usually adding some kind of noise in the data to prevent re-identification (or to make it a bit more difficult) - and usually, if it's going to be combined with other data sets, there's a review: how do we protect the people reflected in those datasets. <br />
<br />
That's just for research. For epidemiology, we have to re-identify people for contact tracing. Makes the datasets radioactive from day one. Not something that will ever be shared. There are other mechanisms to protect the individual, the data, the country or operators with the data. How do we create the frameworks to create the specificly articulated tasks to notify folk they may be at risk. Can they chose, or is someone going to chose for them? Sharing CDRs with no anonymization is a non-starter in a <br />
<br />
Important to note that anonymization is delicate protection - even in research as John notes. CDRs are some of the most reidentifiable data sets that exist, meaning that once they're released in the while it can be very difficult to limit their use, re-identification, and potential harm. From a legal perspective, there are very few protections for organizations or mobile network operators that share this data without user consent. In Liberia, even when mobile networks share data because they've been compelled by a government using emergency powers, they're not immune to prosecution. <br />
<br />
Paul: two questions that come up for me are- what level the responsibility lies. Within NGO communities, very little legal expertise. <br />
especially in managing the data and what you do with it. Second: how to incorporate this into the work flow - policies and practices that we have are the result of years and years of training. Unlikely that we're going to get a system as robust as we like. So, if we assume that, how do we minimise what goes wrong - what does that look like from a legal/org perspective. <br />
<br />
Legality of data sharing - not the ethics - often we're working in areas/regimes where government/'the powers that be' are looking for reasons to STOP the work that's going on. If UN/whoever, isn't abiding by those laws, it can give them fuel to restrict civil society actions. Not experimenting in a way that could, in the long run, clamp down. <br />
<br />
Willow - I totally worry about this as well.<br />
<br />
Also: some national laws are legitimately abrogated during emergencies - this could work in favour of / against responsible data management<br />
<br />
Education focused on industry is focused on data siloes, combining your data to make more out of it. Then problems of anonymizing, what are the technical solutions? The idea of knowledge silos, have the data people not talking to the bio not talking to the law people.<br />
<br />
Zara: People working in the field have low to zero awareness of these issues<br />
<br />
John: Knowledge silos reflect organisational structures in field response<br />
<br />
Signals flowing in bureaucracies is up and down channels - but most of what we need to do in these cases is more flexible, informal, ad hoc. Form base on personal relationships, and yet they're the main way that things happen. Right now we're working against hte grain of how orgs get stuff done. <br />
<br />
How can we enable these informal channels? Have the data flow in legal mechanisms TO the problem solvers. Ideally in real time - not a small problem! <br />
<br />
===Knowledge silos===<br />
Data literacy? What does that mean for people in these contexts? (what do they think of as data/what not?) A certain data type might mean something to someone at the humanitarian level, something totally different to someone at the village level. (eg. GPS coordinates). In the will to data share, the process of data sharing and the people, can get lost. Understanding people, process + environment. Between agencies, local govt, national government, etc. <br />
<br />
There are a bunch of things which have been brought up. Specifically to silos, the informal mechanisms John talked about were really pervasive in Ebola response in Liberia. Social groups or friendly orgs determining who was participating in sharing. Rarely did that data make it back to the ministry of health. No culture of reporting. Even when there was, the format, commonality of definitions, etc made it very difficult to decipher or to get value out of the data that made it back.<br />
<br />
===On the paper, two points to touch on===<br />
# There are a lot of data literate people in humanitarian orgs - even if people don't have the right terminology, they know that the things they are doing are somewhat concerning. To operationally manage this data, you'd have to fundamentally re-organise the way an org manages their data (??) - even moving from one territorial jurisdiction to another, is a violation of a two types of data law (? -- @Sean please check this!) <br />
# Silos can be damaging when they're barriers to skills. But what data are you sharing, for what purpose? Who needs to see what? That kind of mapping very rarely gets done at the outset. Coordination has been an endemic problem of disaster response for a long time - data has potential to make that harder.<br />
<br />
Paul: capacity of 'clusters' is completely variable & can't be predicted. Informality of coordination: useful coordination is built out of informal coordination, not the formal structures. <br />
<br />
==Informal / formal sharing standards==<br />
John: HXL: http://hxlstandard.org/ is an acknowledgement that there will be no formal data standard to describe how we're all supposed to work. Let's describe how we all do it now, and create a mechanism to help us aggregate it a bit. Simple idea - put another # on columns you want to share (#s allow you to specify what that data type is), and the data that doesn't have a # doesn't get shared. <br />
<br />
Share, using the common tool of a spreadsheet - which humanitarians generally use, over email. HXL generally dealing with aggregate numbers, less ~individual/privacy<br />
<br />
==What next??==<br />
Sean: - a much more public, less technical, review of what are the component factors that make different algorithms/different data models, applicable to different things. eg. Flowminder, was also one of the most cited bodies of work for why we should be releasing CDRs, but all of the examples used were based on migration, where you can build probablistic models much easier than you can for eg. Ebola. There are commonalities between the factors of diseases that make a big difference. Quality control is a big, open, public interest area. Starting to see eg. Open AI (not the right answer for this community!) - take a step towards that. <br />
Having a public discussion about what makes a data model 'good', applicable - what are the bounds, what are the factors, being vocal about there being legal risks. Ethics are absolutely important, but if we're not talking about the legal risks, we're trading on the legal disempowerment of the people we are working to serve.<br />
<br />
Harmonising data systems particularly in health systems, with humanitarian systems - investment is hard to find, but easy to do. <br />
<br />
One fundamental tension is that WHO doesn't have emergency funds. When there is an emergency they have to respond to, they are dependent entirely on donations - so, they are subject to all of the fundraising & practical concerns around making sure the whole world know a disaster is happening. Understanding humanitarian response as a market, is another conversation we should be having more publicly. <br />
<br />
==Q and A==<br />
Q: Is there guidance on how to assess whether big data is really going to answer your question? <br />
: A: connecting between data people/biology people.. as per Sean's answer above.<br />
<br />
Q. Is there a risk assessment procedure that guides orgs to .... <br />
: A: There is, but Tim feels being in the data world rather than the humanitarian world -- people could be more open about. You have to go through, be working on an international scale, be more public about how we look at projects before we decide to take them on.<br />
: A: Opt-in data donor (like an organ donor) when you sign up for a phone plan. Solves consent problem, but not the demand problem. There are low-hanging fruits in this space.<br />
<br />
Q: Would having some ethical guidelines and standards for are there any existing guidelines for responsible data collection, storage, dissemination, and destruction could be helpful?<br />
: A: there are at least a dozen frameworks which say 'this is how we should be handling personal/public/ data. They have varying levels of "toothiness". <br />
: A: there are a good principles, and almost no really good practice -- at least when you get into operational contexts. We have a definitional set of problems around what kind of data does work, what are the cost trade offs, etc. We're in one of those situations where there are a big, big ethical questions (necessity, limitation in use) - but they are all very difficult to assess at present, even more difficult to enforce. Practical guidance would go a long way.<br />
<br />
Danna: consent is a place we go to mitigate risk, but it's really complicated, used to coat over issues. Yourself or an organization you're working with, what could a consent policy look like? How would it effect the way consent is given, taken away, etc? In humanitarian setting; are you able to actually get consent? If you're not, then we probably shouldn't be talking about consent. It's about the ethical - legal. Consent isn't always the right framework. Consent without the ability to enforce limitations of use is absolutely whitewash. If you're using data from providers and ICTs, if they didn't have a choice in using it (and thus consenting) At present, outside of research settings, there really isn't any means of protection or limitation Violation of consent is a great way to punish provable abuse - which I think is a useful first step but there aren't technical solutions, we're a long way from organizational solutions, and unfortunately the market (economic incentives) pulls everyone in the exact opposite direction<br />
<br />
Q: There's data.un.org - but is there already an umbrella org who has both political clout, and substantive knowledge to be able to say - let's all come to the table and come up with something to at least set some outer bounds and resolve some of the hardest issues?<br />
: A: UN is not a monolith - the agencies have very different attitudes towards data? eg. UNHCR, DESA, OCHA, Global Pulse - their approach to managing it is fundamentally different. As an 'institution' it's not set up to answer the question in that way. Can it set a standard, or function as a mediating org? (in many countries, the UN is not perceived as neutral.) Work can't be pushed off to one 'mediator' organisation, it's going to require all of us to do it - and it's going to be a long hard slog!! Mechanisms for convening the UN are powerful, but the mechanisms for implementing and putting into practice are a little bit more work. <br />
: A: in some contexts, INGOs, local NGOs, local gov't offices - that part of the data sharing can be fraught with more challenges.<br />
<br />
==Closing statements==<br />
* Danna: looking at the instruction. How do we make a legal analysis of this work, functional. Looking at a framework for legal + ethical data (not necessarily based in a consent framework) - is something I'd love to keep working on. Places where we can experiment a bit - we need to figure out different ways of working.<br />
* Jen: practical transformations of legal frameworks would be GREAT. netHope could bring to our 45 memebers. Want to talk about the practical aspecgts of this. We'll be setting up these practcal systems (for better or worse) in June at Humanitarian Tech Conference. We'll implement anyway.<br />
* John: Lots of practical steps that need to get taken: if we're dealing with CDRs (or other high sensitive data) - we need to work out ways of dealing with this data in compartmentalised ways. Those black boxes can't fully be black, we need to know the data has been protected. We need to talk with people who the data describes, and understand what we need to do in different contexts, in different legal regimes, different cultural contexts. Practical > theoretical. (doesn't jive well with very academic frameworks of international aid) - we need to take a different approach, get a lot closer to the ground. <br />
* Paul: John talking about coming from the ground up, that's a big task but part of the solution. From the top-down, it's a relatively simple landscape we've got. Limited number of orgs doing all this, limited units, limited people in those units. We could build that list (departments & individuals).<br />
* Sean: A thought from the future, and one from the past. Spoiler, both from the past. South Korea, a MERS outbreak meant they seized the CDRs for the whole country. Then imposed quarantine on 17k people. That messed up tourism and subsequent income. requiring a $9B recovery package. These things are happening. They have a real tangible life impact. Important that these next steps need to keep pace with practice in the other direction. 100 pieces of US legislation successfully ?drafted/introduced re chemicals being used in terrible ways, it was difficult to keep things in check and hold people accountable. Strong advocacy! Seeing everyone step up is exciting.<br />
* Tim: One of my favorite sayings about data from Deidre McCloskey "one of the problems with the discourse around data (Latin for "things given") when we should be talking about capta (things seized)." (e.g. from http://ejpe.org/pdf/7-2-art-4.pdf#page=2) Means different things to different people. Want to step back, take the data, make slow use of it. But that's not right for this. We've developed models for protecting research subjects, which works when it's "everyone," but we don't. (I didn't transpose that right).<br />
* Zara: So many people interested in this from so many different angles, baffling about where we can take this. Let's do events, calls. We might break this out into various working groups.<br />
<br />
==Resources:== <br />
Questions to Ask Frequently (QAFs) when working with Data and Marginalised Communities<br />
http://www.fabriders.net/qafs/<br />
<br />
See: responsible data wiki for consent framework guidance. https://wiki.responsibledata.io/Main_Page<br />
<br />
Geeks Without Bounds did a [http://star-tides.net/sites/default/files/documents/files/responsibleprojectlifecycles.pdf disaster data lifecycle] doc (PDF) - http://gwob.org/<br />
<br />
==EVENTS==<br />
Humanitarian Tech in Boston in June http://www.humanitariantechnology.org/<br />
<br />
HumTechFest (sibling event) also in June! humtechfest@aspirationtech.org June 4th & 5th MIT Cambridge, MA<br />
<br />
http://www.unglobalpulse.org/blog/data-privacy-day-roundup<br />
<br />
RightsCon Silicon Valley 3/30-4/1/2016 https://www.rightscon.org/<br />
<br />
==Where to from here?==<br />
# The Ebola context specifically. It seems like there's a great blend of first-person expertise and research interest (Stefaan, Chris?, me). This might be a book club kind of chat about the paper where people talk about their experience/research and ways that it compares and contrasts? If we can, it might be great to get someone to write a blog post on the back of this toward a RDF community history of the crisis? <br />
# Domain expertise. There's interest in exploring the intersection (and/or divergence) of data analysis and privacy - particularly in health/humanitarian contexts. It sounds like there are a lot of people who are better versed on the comparative methodologies around this subject than I am, so I'm happy to join, but would love it if someone else could frame and organize this one. <br />
# Strategic advocacy. This would focus on building an effective advocacy movement to channel current momentum into safer practice. Again, a list full of experts, so my preference would be to start with framing the pressures, markets, and institutional actors involved, and then maybe explore points of leverage/influence, and see whether there's a critical mass of folks interested in taking next steps. I'd love to help lead on this one, through there are a lot of experts here, so I'm sure it'd be a group effort. <br />
# Clear legal questions. Lawyers all over that would be likely willing to engage with us. Want a followup call around that. Danna is into it! Basic overview of legal frameworks for responders, as per JenC's request. Theories of litigation. We hear one hook, but we don't get to explore that hook so we get stuck. Each juristiction is going to be SO different.<br />
<br />
==Glossary of terms and acronyms==<br />
* CDR : Call Detail Records are a blanket term that refers to the data that mobile network operators collect in the course of providing telecommunications services. Although practice varies between operators, in order to both provide services and present billing statements, network operators store a customer’s name, address, billing status, account identifiers, payment information, log of incoming and outgoing phone calls, phone numbers attached to each call, length of each call, number of text messages sent and received, log of data use (including web sites visited, information transferred, apps used), and, where applicable, mobile money transactions history. Many mobile network operators record and store more information, but the above is typical. One other piece of information that mobile network operators require is location data.<br />
* ETC : Ebola Treatment Center<br />
* PII : Personally Identifying Information<br />
* Predictive quarantine: <br />
* ICTs: Information and Communications Technology/ies, umbrella term for any communication device/application: radio, television, cell phones, computer/ network hardware/software, satellite systems</div>Willowbl00https://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-11-14T05:17:28Z<p>Willowbl00: /* Visual Canvas */</p>
<hr />
<div>'''''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 />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
===Why Consent?===<br />
A document for use in persuading people why the consent framework is worthwhile and necessary. In progress [https://docs.google.com/a/theengineroom.org/document/d/1SRtv0YAbClY2C3o9Y5cO__iCYfOWhbkX1Q-xfVFrsGw/edit?usp=sharing here].<br />
<br />
===Checklist===<br />
'''Currently in progress. View and comment [https://docs.google.com/document/d/1PJxBAP1rFkjq9p7NuYcN_G5iomfCML-qiMTn5SPPHxE/edit?usp=sharing here].'''<br />
<br />
This checklist is designed to help projects that include an element of data collection to develop appropriate consent policies and practices. The checklist can be especially useful for projects using digital or mobile tools to collect, store or publish data, yet understand the importance of seeking the informed consent of individuals involved (the data subjects). This checklist does not address the additional considerations that would be necessary when obtaining the consent of groups or communities nor on how to approach consent in situations where there is no connection to the data subject.<br />
<br />
''How to use it:''<br />
<br />
This checklist is intended for use by project coordinators, and can ground conversations with management and project staff in order to identify risks and mitigation strategies during project design or implementation. It should ideally be used with the input of data subjects. All recommendations in this checklist include suggestions of issues and questions to consider when designing a consent policy and making related decisions, and should therefore be used as a guide to developing project specific consent policies.<br />
<br />
===Visual Canvas===<br />
[[File:ConsentFramework.jpg|800px|Inspired by Strategyzer's Business Model Canvas, this vizthink shows the components of the framework for consent policies proposed by Amnesty and worked on by @willowbl00 @cosgrovedent @taniaishungry @jasmeenpatheja @Ingleton]]<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
This conversation was definitely influenced by, and framed on, Feminist and Queer Theory. It was delightful. We ran it through an IRC use case, which likely exists typed up somewhere.<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* eR: Add left hand margin columns and make into pretty PDF<br />
* Write out use cases<br />
* Test against use cases<br />
* Training guides that don’t scare people away from the work<br />
* How to inform data handlers about consent obligations (guidelines? checklist? process suggestions?)<br />
* Community consent guidelines<br />
* How to address consent issues when there is no possibility of interaction with the data subject, i.e. data scraping?<br />
===Ongoing Questions===<br />
* Do you know of any upcoming projects that we could test drive this on? <br />
* Have we missed any of the major categories of consent? <br />
* Are there any projects that you don’t think this applies to?<br />
* Do you know of any other good consent forms or checklists?<br />
<br />
== Contributors ==<br />
[http://twitter.com/willowbl00 @willowbl00], [http://twitter.com/cosgrovedent @cosgrovedent], [http://twitter.com/taniaishungry @taniaishungry], [http://twitter.com/jasmeenpatheja @jasmeenpatheja], [http://twitter.com/ingleton @Ingleton]<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 />
[https://www.theengineroom.org/modeling-consent-policies-for-civil-society-data/ Blog post on outputs from the Ethics of Data conference]<br />
<br />
[http://gwob.org/wp-content/uploads/2014/07/responsibleprojectlifecycles.pdf GWOB's Responsible Project Lifecycles PDF]<br />
<br />
CDA Collective resources: [http://www.cdacollaborative.org/programs/do-no-harm/ Do No Harm], [http://www.cdacollaborative.org/programs/listening-program/ The Listening Project]<br />
<br />
[https://en.necessaryandproportionate.org International Principles on the Application of Human Rights to Communications Surveillance]</div>Willowbl00https://wiki.responsibledata.io/File:ConsentFramework.jpgFile:ConsentFramework.jpg2014-11-14T05:14:16Z<p>Willowbl00: </p>
<hr />
<div></div>Willowbl00https://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-06T13:17:25Z<p>Willowbl00: /* Resources (we <3 links!) */</p>
<hr />
<div>'''''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 />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
===Why Consent?===<br />
A document for use in persuading people why the consent framework is worthwhile and necessary. In progress [https://docs.google.com/a/theengineroom.org/document/d/1SRtv0YAbClY2C3o9Y5cO__iCYfOWhbkX1Q-xfVFrsGw/edit?usp=sharing here].<br />
<br />
===Checklist===<br />
'''Currently in progress. View and comment [https://docs.google.com/document/d/1PJxBAP1rFkjq9p7NuYcN_G5iomfCML-qiMTn5SPPHxE/edit?usp=sharing here].'''<br />
<br />
This checklist is designed to help projects that include an element of data collection to develop appropriate consent policies and practices. The checklist can be especially useful for projects using digital or mobile tools to collect, store or publish data, yet understand the importance of seeking the informed consent of individuals involved (the data subjects). This checklist does not address the additional considerations that would be necessary when obtaining the consent of groups or communities nor on how to approach consent in situations where there is no connection to the data subject.<br />
<br />
''How to use it:''<br />
<br />
This checklist is intended for use by project coordinators, and can ground conversations with management and project staff in order to identify risks and mitigation strategies during project design or implementation. It should ideally be used with the input of data subjects. All recommendations in this checklist include suggestions of issues and questions to consider when designing a consent policy and making related decisions, and should therefore be used as a guide to developing project specific consent policies.<br />
<br />
===Visual Canvas===<br />
[[File:Framework for Consent Policies.jpg|800px|Inspired by Strategyzer's Business Model Canvas, this vizthink shows the components of the framework for consent policies proposed by Amnesty and worked on by @willowbl00 @cosgrovedent @taniaishungry @jasmeenpatheja @Ingleton]]<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
This conversation was definitely influenced by, and framed on, Feminist and Queer Theory. It was delightful. We ran it through an IRC use case, which likely exists typed up somewhere.<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* eR: Add left hand margin columns and make into pretty PDF<br />
* Write out use cases<br />
* Test against use cases<br />
* Training guides that don’t scare people away from the work<br />
* How to inform data handlers about consent obligations (guidelines? checklist? process suggestions?)<br />
* Community consent guidelines<br />
* How to address consent issues when there is no possibility of interaction with the data subject, i.e. data scraping?<br />
===Ongoing Questions===<br />
* Do you know of any upcoming projects that we could test drive this on? <br />
* Have we missed any of the major categories of consent? <br />
* Are there any projects that you don’t think this applies to?<br />
* Do you know of any other good consent forms or checklists?<br />
<br />
== Contributors ==<br />
[http://twitter.com/willowbl00 @willowbl00], [http://twitter.com/cosgrovedent @cosgrovedent], [http://twitter.com/taniaishungry @taniaishungry], [http://twitter.com/jasmeenpatheja @jasmeenpatheja], [http://twitter.com/ingleton @Ingleton]<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 />
[https://www.theengineroom.org/modeling-consent-policies-for-civil-society-data/ Blog post on outputs from the Ethics of Data conference]<br />
<br />
[http://gwob.org/wp-content/uploads/2014/07/responsibleprojectlifecycles.pdf GWOB's Responsible Project Lifecycles PDF]<br />
<br />
CDA Collective resources: [http://www.cdacollaborative.org/programs/do-no-harm/ Do No Harm], [http://www.cdacollaborative.org/programs/listening-program/ The Listening Project]<br />
<br />
[https://en.necessaryandproportionate.org International Principles on the Application of Human Rights to Communications Surveillance]</div>Willowbl00https://wiki.responsibledata.io/User:Willowbl00User:Willowbl002014-10-02T14:43:08Z<p>Willowbl00: Created page with "thumb On the Internet: * [http://blog.bl00cyb.org Blog] * [http://viz.bl00cyb.org VizThink Catalogue] * [http://twitter.com/willowbl00..."</p>
<hr />
<div>[[File:Willowbl00 drawing at TOG.jpg|thumb]]<br />
<br />
On the Internet:<br />
* [http://blog.bl00cyb.org Blog]<br />
* [http://viz.bl00cyb.org VizThink Catalogue]<br />
* [http://twitter.com/willowbl00 Twitter]<br />
etc. willowbl00 nearly anywhere.<br />
<br />
The drawings posted here I do mainly in Adobe Ideas on iPad. You can see the whole process [http://viz.bl00cyb.org/how-do-you-do-that/ here].</div>Willowbl00https://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-02T14:34:42Z<p>Willowbl00: /* Resources (we <3 links!) */ consistent formatting</p>
<hr />
<div>'''''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 />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
===Why Consent?===<br />
A document for use in persuading people why the consent framework is worthwhile and necessary. In progress [https://docs.google.com/a/theengineroom.org/document/d/1SRtv0YAbClY2C3o9Y5cO__iCYfOWhbkX1Q-xfVFrsGw/edit?usp=sharing here].<br />
<br />
===Checklist===<br />
'''Currently in progress. View and comment [https://docs.google.com/document/d/1PJxBAP1rFkjq9p7NuYcN_G5iomfCML-qiMTn5SPPHxE/edit?usp=sharing here].'''<br />
<br />
This checklist is designed to help projects that include an element of data collection to develop appropriate consent policies and practices. The checklist can be especially useful for projects using digital or mobile tools to collect, store or publish data, yet understand the importance of seeking the informed consent of individuals involved (the data subjects). This checklist does not address the additional considerations that would be necessary when obtaining the consent of groups or communities nor on how to approach consent in situations where there is no connection to the data subject.<br />
<br />
''How to use it:''<br />
<br />
This checklist is intended for use by project coordinators, and can ground conversations with management and project staff in order to identify risks and mitigation strategies during project design or implementation. It should ideally be used with the input of data subjects. All recommendations in this checklist include suggestions of issues and questions to consider when designing a consent policy and making related decisions, and should therefore be used as a guide to developing project specific consent policies.<br />
<br />
===Visual Canvas===<br />
[[File:Framework for Consent Policies.jpg|800px|Inspired by Strategyzer's Business Model Canvas, this vizthink shows the components of the framework for consent policies proposed by Amnesty and worked on by @willowbl00 @cosgrovedent @taniaishungry @jasmeenpatheja @Ingleton]]<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
This conversation was definitely influenced by, and framed on, Feminist and Queer Theory. It was delightful. We ran it through an IRC use case, which likely exists typed up somewhere.<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* eR: Add left hand margin columns and make into pretty PDF<br />
* Write out use cases<br />
* Test against use cases<br />
* Training guides that don’t scare people away from the work<br />
* How to inform data handlers about consent obligations (guidelines? checklist? process suggestions?)<br />
* Community consent guidelines<br />
* How to address consent issues when there is no possibility of interaction with the data subject, i.e. data scraping?<br />
===Ongoing Questions===<br />
* Do you know of any upcoming projects that we could test drive this on? <br />
* Have we missed any of the major categories of consent? <br />
* Are there any projects that you don’t think this applies to?<br />
* Do you know of any other good consent forms or checklists?<br />
<br />
== Contributors ==<br />
[http://twitter.com/willowbl00 @willowbl00], [http://twitter.com/cosgrovedent @cosgrovedent], [http://twitter.com/taniaishungry @taniaishungry], [http://twitter.com/jasmeenpatheja @jasmeenpatheja], [http://twitter.com/ingleton @Ingleton]<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 />
[https://www.theengineroom.org/modeling-consent-policies-for-civil-society-data/ Blog post on outputs from the Ethics of Data conference]<br />
<br />
[http://gwob.org/wp-content/uploads/2014/07/responsibleprojectlifecycles.pdf GWOB's Responsible Project Lifecycles PDF]<br />
<br />
CDA Collective resources: [http://www.cdacollaborative.org/programs/do-no-harm/ Do No Harm], [http://www.cdacollaborative.org/programs/listening-program/ The Listening Project]</div>Willowbl00https://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-02T14:32:37Z<p>Willowbl00: /* Checklist */ omg formatting.</p>
<hr />
<div>'''''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 />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
===Why Consent?===<br />
A document for use in persuading people why the consent framework is worthwhile and necessary. In progress [https://docs.google.com/a/theengineroom.org/document/d/1SRtv0YAbClY2C3o9Y5cO__iCYfOWhbkX1Q-xfVFrsGw/edit?usp=sharing here].<br />
<br />
===Checklist===<br />
'''Currently in progress. View and comment [https://docs.google.com/document/d/1PJxBAP1rFkjq9p7NuYcN_G5iomfCML-qiMTn5SPPHxE/edit?usp=sharing here].'''<br />
<br />
This checklist is designed to help projects that include an element of data collection to develop appropriate consent policies and practices. The checklist can be especially useful for projects using digital or mobile tools to collect, store or publish data, yet understand the importance of seeking the informed consent of individuals involved (the data subjects). This checklist does not address the additional considerations that would be necessary when obtaining the consent of groups or communities nor on how to approach consent in situations where there is no connection to the data subject.<br />
<br />
''How to use it:''<br />
<br />
This checklist is intended for use by project coordinators, and can ground conversations with management and project staff in order to identify risks and mitigation strategies during project design or implementation. It should ideally be used with the input of data subjects. All recommendations in this checklist include suggestions of issues and questions to consider when designing a consent policy and making related decisions, and should therefore be used as a guide to developing project specific consent policies.<br />
<br />
===Visual Canvas===<br />
[[File:Framework for Consent Policies.jpg|800px|Inspired by Strategyzer's Business Model Canvas, this vizthink shows the components of the framework for consent policies proposed by Amnesty and worked on by @willowbl00 @cosgrovedent @taniaishungry @jasmeenpatheja @Ingleton]]<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
This conversation was definitely influenced by, and framed on, Feminist and Queer Theory. It was delightful. We ran it through an IRC use case, which likely exists typed up somewhere.<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* eR: Add left hand margin columns and make into pretty PDF<br />
* Write out use cases<br />
* Test against use cases<br />
* Training guides that don’t scare people away from the work<br />
* How to inform data handlers about consent obligations (guidelines? checklist? process suggestions?)<br />
* Community consent guidelines<br />
* How to address consent issues when there is no possibility of interaction with the data subject, i.e. data scraping?<br />
===Ongoing Questions===<br />
* Do you know of any upcoming projects that we could test drive this on? <br />
* Have we missed any of the major categories of consent? <br />
* Are there any projects that you don’t think this applies to?<br />
* Do you know of any other good consent forms or checklists?<br />
<br />
== Contributors ==<br />
[http://twitter.com/willowbl00 @willowbl00], [http://twitter.com/cosgrovedent @cosgrovedent], [http://twitter.com/taniaishungry @taniaishungry], [http://twitter.com/jasmeenpatheja @jasmeenpatheja], [http://twitter.com/ingleton @Ingleton]<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/<br />
<br />
[http://gwob.org/wp-content/uploads/2014/07/responsibleprojectlifecycles.pdf GWOB's Responsible Project Lifecycles PDF]<br />
<br />
CDA Collective resources: [http://www.cdacollaborative.org/programs/do-no-harm/ Do No Harm], [http://www.cdacollaborative.org/programs/listening-program/ The Listening Project]</div>Willowbl00https://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-02T14:31:52Z<p>Willowbl00: /* Outputs */</p>
<hr />
<div>'''''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 />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
===Why Consent?===<br />
A document for use in persuading people why the consent framework is worthwhile and necessary. In progress [https://docs.google.com/a/theengineroom.org/document/d/1SRtv0YAbClY2C3o9Y5cO__iCYfOWhbkX1Q-xfVFrsGw/edit?usp=sharing here].<br />
<br />
===Checklist===<br />
Currently in progress. View and comment [https://docs.google.com/document/d/1PJxBAP1rFkjq9p7NuYcN_G5iomfCML-qiMTn5SPPHxE/edit?usp=sharing here].<br />
<br />
'''This checklist is designed to help projects that include an element of data collection to develop appropriate consent policies and practices. The checklist can be especially useful for projects using digital or mobile tools to collect, store or publish data, yet understand the importance of seeking the informed consent of individuals involved (the data subjects). This checklist does not address the additional considerations that would be necessary when obtaining the consent of groups or communities nor on how to approach consent in situations where there is no connection to the data subject.'''<br />
<br />
''How to use it:''<br />
<br />
This checklist is intended for use by project coordinators, and can ground conversations with management and project staff in order to identify risks and mitigation strategies during project design or implementation. It should ideally be used with the input of data subjects. All recommendations in this checklist include suggestions of issues and questions to consider when designing a consent policy and making related decisions, and should therefore be used as a guide to developing project specific consent policies. <br />
<br />
===Visual Canvas===<br />
[[File:Framework for Consent Policies.jpg|800px|Inspired by Strategyzer's Business Model Canvas, this vizthink shows the components of the framework for consent policies proposed by Amnesty and worked on by @willowbl00 @cosgrovedent @taniaishungry @jasmeenpatheja @Ingleton]]<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
This conversation was definitely influenced by, and framed on, Feminist and Queer Theory. It was delightful. We ran it through an IRC use case, which likely exists typed up somewhere.<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* eR: Add left hand margin columns and make into pretty PDF<br />
* Write out use cases<br />
* Test against use cases<br />
* Training guides that don’t scare people away from the work<br />
* How to inform data handlers about consent obligations (guidelines? checklist? process suggestions?)<br />
* Community consent guidelines<br />
* How to address consent issues when there is no possibility of interaction with the data subject, i.e. data scraping?<br />
===Ongoing Questions===<br />
* Do you know of any upcoming projects that we could test drive this on? <br />
* Have we missed any of the major categories of consent? <br />
* Are there any projects that you don’t think this applies to?<br />
* Do you know of any other good consent forms or checklists?<br />
<br />
== Contributors ==<br />
[http://twitter.com/willowbl00 @willowbl00], [http://twitter.com/cosgrovedent @cosgrovedent], [http://twitter.com/taniaishungry @taniaishungry], [http://twitter.com/jasmeenpatheja @jasmeenpatheja], [http://twitter.com/ingleton @Ingleton]<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/<br />
<br />
[http://gwob.org/wp-content/uploads/2014/07/responsibleprojectlifecycles.pdf GWOB's Responsible Project Lifecycles PDF]<br />
<br />
CDA Collective resources: [http://www.cdacollaborative.org/programs/do-no-harm/ Do No Harm], [http://www.cdacollaborative.org/programs/listening-program/ The Listening Project]</div>Willowbl00https://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-02T14:27:28Z<p>Willowbl00: added a subtitle.</p>
<hr />
<div>'''''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 />
== Outputs ==<br />
''Description of a minimum viable product, aspirational output, stretch goals, etc.''<br />
===Why Consent?===<br />
A document for use in persuading people why the consent framework is worthwhile and necessary. In progress [https://docs.google.com/a/theengineroom.org/document/d/1SRtv0YAbClY2C3o9Y5cO__iCYfOWhbkX1Q-xfVFrsGw/edit?usp=sharing here].<br />
<br />
===Checklist===<br />
Currently in progress. View and comment [https://docs.google.com/document/d/1PJxBAP1rFkjq9p7NuYcN_G5iomfCML-qiMTn5SPPHxE/edit?usp=sharing here].<br />
<br />
===Visual Canvas===<br />
[[File:Framework for Consent Policies.jpg|800px|Inspired by Strategyzer's Business Model Canvas, this vizthink shows the components of the framework for consent policies proposed by Amnesty and worked on by @willowbl00 @cosgrovedent @taniaishungry @jasmeenpatheja @Ingleton]]<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
This conversation was definitely influenced by, and framed on, Feminist and Queer Theory. It was delightful. We ran it through an IRC use case, which likely exists typed up somewhere.<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* eR: Add left hand margin columns and make into pretty PDF<br />
* Write out use cases<br />
* Test against use cases<br />
* Training guides that don’t scare people away from the work<br />
* How to inform data handlers about consent obligations (guidelines? checklist? process suggestions?)<br />
* Community consent guidelines<br />
* How to address consent issues when there is no possibility of interaction with the data subject, i.e. data scraping?<br />
===Ongoing Questions===<br />
* Do you know of any upcoming projects that we could test drive this on? <br />
* Have we missed any of the major categories of consent? <br />
* Are there any projects that you don’t think this applies to?<br />
* Do you know of any other good consent forms or checklists?<br />
<br />
== Contributors ==<br />
[http://twitter.com/willowbl00 @willowbl00], [http://twitter.com/cosgrovedent @cosgrovedent], [http://twitter.com/taniaishungry @taniaishungry], [http://twitter.com/jasmeenpatheja @jasmeenpatheja], [http://twitter.com/ingleton @Ingleton]<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/<br />
<br />
[http://gwob.org/wp-content/uploads/2014/07/responsibleprojectlifecycles.pdf GWOB's Responsible Project Lifecycles PDF]<br />
<br />
CDA Collective resources: [http://www.cdacollaborative.org/programs/do-no-harm/ Do No Harm], [http://www.cdacollaborative.org/programs/listening-program/ The Listening Project]</div>Willowbl00https://wiki.responsibledata.io/Framework_for_consent_policiesFramework for consent policies2014-10-02T14:24:54Z<p>Willowbl00: added the contents.</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 />
===Why Consent?===<br />
A document for use in persuading people why the consent framework is worthwhile and necessary. In progress [https://docs.google.com/a/theengineroom.org/document/d/1SRtv0YAbClY2C3o9Y5cO__iCYfOWhbkX1Q-xfVFrsGw/edit?usp=sharing here].<br />
<br />
===Checklist===<br />
Currently in progress. View and comment [https://docs.google.com/document/d/1PJxBAP1rFkjq9p7NuYcN_G5iomfCML-qiMTn5SPPHxE/edit?usp=sharing here].<br />
<br />
===Visual Canvas===<br />
[[File:Framework for Consent Policies.jpg|800px|Inspired by Strategyzer's Business Model Canvas, this vizthink shows the components of the framework for consent policies proposed by Amnesty and worked on by @willowbl00 @cosgrovedent @taniaishungry @jasmeenpatheja @Ingleton]]<br />
<br />
== Connection to previous RDFs ==<br />
''Add links, any useful information''<br />
<br />
== Notes ==<br />
This conversation was definitely influenced by, and framed on, Feminist and Queer Theory. It was delightful. We ran it through an IRC use case, which likely exists typed up somewhere.<br />
<br />
[[File:RDFbuda_consent_WB.jpg | 800px]]<br />
<br />
== Audience ==<br />
''Personas, use cases, context''<br />
<br />
== Next steps ==<br />
* eR: Add left hand margin columns and make into pretty PDF<br />
* Write out use cases<br />
* Test against use cases<br />
* Training guides that don’t scare people away from the work<br />
* How to inform data handlers about consent obligations (guidelines? checklist? process suggestions?)<br />
* Community consent guidelines<br />
* How to address consent issues when there is no possibility of interaction with the data subject, i.e. data scraping?<br />
===Ongoing Questions===<br />
* Do you know of any upcoming projects that we could test drive this on? <br />
* Have we missed any of the major categories of consent? <br />
* Are there any projects that you don’t think this applies to?<br />
* Do you know of any other good consent forms or checklists?<br />
<br />
== Contributors ==<br />
[http://twitter.com/willowbl00 @willowbl00], [http://twitter.com/cosgrovedent @cosgrovedent], [http://twitter.com/taniaishungry @taniaishungry], [http://twitter.com/jasmeenpatheja @jasmeenpatheja], [http://twitter.com/ingleton @Ingleton]<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/<br />
<br />
[http://gwob.org/wp-content/uploads/2014/07/responsibleprojectlifecycles.pdf GWOB's Responsible Project Lifecycles PDF]<br />
<br />
CDA Collective resources: [http://www.cdacollaborative.org/programs/do-no-harm/ Do No Harm], [http://www.cdacollaborative.org/programs/listening-program/ The Listening Project]</div>Willowbl00https://wiki.responsibledata.io/RDF_BudapestRDF Budapest2014-10-01T10:42:28Z<p>Willowbl00: /* Round 2 */ spelling! (already did "move")</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 exploitation]]<br />
<br />
[[Responsible Data survey]]<br />
<br />
[[Human Rights documentation]]<br />
<br />
[[White paper on responsilble data standards]]</div>Willowbl00https://wiki.responsibledata.io/Code_of_ethics_in_sex_exploitationCode of ethics in sex exploitation2014-10-01T10:41:52Z<p>Willowbl00: Willowbl00 moved page Code of ethics in sex explotiation to Code of ethics in sex exploitation: spelling!</p>
<hr />
<div>We talked about how to respond to sex exploitation in solidarity, not paternalism. Our conversation assumed that some people can (and do) consent to sex work, and that targeting them through data collection is irresponsible. Things essentially boiled down to: '''Moral judgement is about a choice made, empowerment is about freedom to make choices.''' We advocate for ''asking'' people about if they are ok, and if your goals and methodologies are acceptable. A remaining question is: '''What data patterns are different between consensual versus trafficked sex workers?''' and feel it's difficult to see these differences until we are able to have a more nuanced conversation, meaning dealing with taboos and morals. We therefore think inclusion will lead to better data, which will lead to more accurate action.</div>Willowbl00https://wiki.responsibledata.io/Code_of_ethics_in_sex_explotiationCode of ethics in sex explotiation2014-10-01T10:41:52Z<p>Willowbl00: Willowbl00 moved page Code of ethics in sex explotiation to Code of ethics in sex exploitation: spelling!</p>
<hr />
<div>#REDIRECT [[Code of ethics in sex exploitation]]</div>Willowbl00https://wiki.responsibledata.io/Code_of_ethics_in_sex_exploitationCode of ethics in sex exploitation2014-10-01T10:27:33Z<p>Willowbl00: </p>
<hr />
<div>We talked about how to respond to sex exploitation in solidarity, not paternalism. Our conversation assumed that some people can (and do) consent to sex work, and that targeting them through data collection is irresponsible. Things essentially boiled down to: '''Moral judgement is about a choice made, empowerment is about freedom to make choices.''' We advocate for ''asking'' people about if they are ok, and if your goals and methodologies are acceptable. A remaining question is: '''What data patterns are different between consensual versus trafficked sex workers?''' and feel it's difficult to see these differences until we are able to have a more nuanced conversation, meaning dealing with taboos and morals. We therefore think inclusion will lead to better data, which will lead to more accurate action.</div>Willowbl00https://wiki.responsibledata.io/Code_of_ethics_in_sex_exploitationCode of ethics in sex exploitation2014-10-01T10:25:32Z<p>Willowbl00: content! it's a thing!</p>
<hr />
<div>We talked about how to respond to sex exploitation in solidarity, not paternalism. Our conversation assumed that some people can (and do) consent to sex work, and that targeting them through data collection is irresponsible. Things essentially boiled down to: '''Moral judgement is about a choice made, empowerment is about freedom to make choices.''' We advocate for ''asking'' people about if they are ok, and if your goals and methodologies are acceptable. A remaining question is: '''What data patterns are different between consensual versus trafficked sex workers?''' and feel it's difficult to see these differences until we are able to have a more nuanced conversation.</div>Willowbl00