deploy: ad4f190

very-good-science · May 30, 2024 · acc1086 · acc1086
1 parent ed31f24
commit acc1086
Show file tree

Hide file tree

Showing 257 changed files with 11,965 additions and 28,573 deletions.
diff --git a/.buildinfo b/.buildinfo
@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: 7d2843c3acac22679ddd25e80bc4a6ee
+config: 36e6e861293d1ba58caa04777c9a423d
 tags: 645f666f9bcd5a90fca523b33c5a78b7
diff --git a/.doctrees/about.doctree b/.doctrees/about.doctree
diff --git a/.doctrees/code-of-conduct.doctree b/.doctrees/code-of-conduct.doctree
diff --git a/.doctrees/contents/about.doctree b/.doctrees/contents/about.doctree
diff --git a/.doctrees/contents/code-of-conduct.doctree b/.doctrees/contents/code-of-conduct.doctree
diff --git a/.doctrees/contents/contact.doctree b/.doctrees/contents/contact.doctree
diff --git a/.doctrees/contents/contribute.doctree b/.doctrees/contents/contribute.doctree
diff --git a/.doctrees/contents/contribute/changelog.doctree b/.doctrees/contents/contribute/changelog.doctree
diff --git a/.doctrees/contents/contribute/contributors.doctree b/.doctrees/contents/contribute/contributors.doctree
diff --git a/.doctrees/contents/contribute/credit-for-contributions.doctree b/.doctrees/contents/contribute/credit-for-contributions.doctree
diff --git a/.doctrees/contents/contribute/how-to-contribute.doctree b/.doctrees/contents/contribute/how-to-contribute.doctree
diff --git a/.doctrees/contents/contribute/style-guide.doctree b/.doctrees/contents/contribute/style-guide.doctree
diff --git a/.doctrees/contents/data-hazards.doctree b/.doctrees/contents/data-hazards.doctree
diff --git a/.doctrees/contents/events.doctree b/.doctrees/contents/events.doctree
diff --git a/.doctrees/contents/events/2021-09-21_workshop.doctree b/.doctrees/contents/events/2021-09-21_workshop.doctree
diff --git a/.doctrees/contents/events/bristol-tech-fest.doctree b/.doctrees/contents/events/bristol-tech-fest.doctree
diff --git a/.doctrees/contents/events/coworking.doctree b/.doctrees/contents/events/coworking.doctree
diff --git a/.doctrees/contents/events/jgi-showcase-events.doctree b/.doctrees/contents/events/jgi-showcase-events.doctree
diff --git a/.doctrees/contents/events/mozfest2022.doctree b/.doctrees/contents/events/mozfest2022.doctree
diff --git a/.doctrees/contents/hazards/automates-decision-making.doctree b/.doctrees/contents/hazards/automates-decision-making.doctree
diff --git a/.doctrees/contents/hazards/danger-of-misuse.doctree b/.doctrees/contents/hazards/danger-of-misuse.doctree
diff --git a/.doctrees/contents/hazards/difficult-to-understand.doctree b/.doctrees/contents/hazards/difficult-to-understand.doctree
diff --git a/.doctrees/contents/hazards/direct-harm.doctree b/.doctrees/contents/hazards/direct-harm.doctree
diff --git a/.doctrees/contents/hazards/general-hazard.doctree b/.doctrees/contents/hazards/general-hazard.doctree
diff --git a/.doctrees/contents/hazards/hazard-template.doctree b/.doctrees/contents/hazards/hazard-template.doctree
diff --git a/.doctrees/contents/hazards/high-environmental-cost.doctree b/.doctrees/contents/hazards/high-environmental-cost.doctree
diff --git a/.doctrees/contents/hazards/lacks-community-involvement.doctree b/.doctrees/contents/hazards/lacks-community-involvement.doctree
diff --git a/.doctrees/contents/hazards/lacks-informed-consent.doctree b/.doctrees/contents/hazards/lacks-informed-consent.doctree
diff --git a/.doctrees/contents/hazards/ranks-classifies.doctree b/.doctrees/contents/hazards/ranks-classifies.doctree
diff --git a/.doctrees/contents/hazards/reinforces-biases.doctree b/.doctrees/contents/hazards/reinforces-biases.doctree
diff --git a/.doctrees/contents/hazards/risk-to-privacy.doctree b/.doctrees/contents/hazards/risk-to-privacy.doctree
diff --git a/.doctrees/contents/materials.doctree b/.doctrees/contents/materials.doctree
diff --git a/.doctrees/contents/materials/examples.doctree b/.doctrees/contents/materials/examples.doctree
diff --git a/.doctrees/contents/materials/misc/geno_to_pheno_example.doctree b/.doctrees/contents/materials/misc/geno_to_pheno_example.doctree
diff --git a/.doctrees/contents/materials/misc/proposal.doctree b/.doctrees/contents/materials/misc/proposal.doctree
diff --git a/.doctrees/contents/materials/misc/workshop-21092021.doctree b/.doctrees/contents/materials/misc/workshop-21092021.doctree
diff --git a/.doctrees/contents/materials/presenting.doctree b/.doctrees/contents/materials/presenting.doctree
diff --git a/.doctrees/contents/materials/seedcorn.doctree b/.doctrees/contents/materials/seedcorn.doctree
diff --git a/.doctrees/contents/materials/self-assessment.doctree b/.doctrees/contents/materials/self-assessment.doctree
diff --git a/.doctrees/contents/materials/teaching.doctree b/.doctrees/contents/materials/teaching.doctree
diff --git a/.doctrees/contents/materials/teaching/students.doctree b/.doctrees/contents/materials/teaching/students.doctree
diff --git a/.doctrees/contents/materials/workshop.doctree b/.doctrees/contents/materials/workshop.doctree
diff --git a/.doctrees/contents/materials/workshop/audience.doctree b/.doctrees/contents/materials/workshop/audience.doctree
diff --git a/.doctrees/contents/materials/workshop/facilitating.doctree b/.doctrees/contents/materials/workshop/facilitating.doctree
diff --git a/.doctrees/contents/materials/workshop/feedback.doctree b/.doctrees/contents/materials/workshop/feedback.doctree
diff --git a/.doctrees/contents/materials/workshop/project-owners.doctree b/.doctrees/contents/materials/workshop/project-owners.doctree
diff --git a/.doctrees/contents/materials/workshop/setup.doctree b/.doctrees/contents/materials/workshop/setup.doctree
diff --git a/.doctrees/contents/materials/workshop/structure.doctree b/.doctrees/contents/materials/workshop/structure.doctree
diff --git a/.doctrees/contents/mitigation-resources.doctree b/.doctrees/contents/mitigation-resources.doctree
diff --git a/.doctrees/contents/presenting/github-badge.doctree b/.doctrees/contents/presenting/github-badge.doctree
diff --git a/.doctrees/contents/presenting/image-app.doctree b/.doctrees/contents/presenting/image-app.doctree
diff --git a/.doctrees/contribute.doctree b/.doctrees/contribute.doctree
diff --git a/.doctrees/contribute/contributors.doctree b/.doctrees/contribute/contributors.doctree
diff --git a/.doctrees/contribute/credit-for-contributions.doctree b/.doctrees/contribute/credit-for-contributions.doctree
diff --git a/.doctrees/contribute/how-to-contribute.doctree b/.doctrees/contribute/how-to-contribute.doctree
diff --git a/.doctrees/contribute/style-guide.doctree b/.doctrees/contribute/style-guide.doctree
diff --git a/.doctrees/environment.pickle b/.doctrees/environment.pickle
diff --git a/.doctrees/events.doctree b/.doctrees/events.doctree
diff --git a/.doctrees/events/2021-09-21_workshop.doctree b/.doctrees/events/2021-09-21_workshop.doctree
diff --git a/.doctrees/events/bristol-tech-fest.doctree b/.doctrees/events/bristol-tech-fest.doctree
diff --git a/.doctrees/events/coworking.doctree b/.doctrees/events/coworking.doctree
diff --git a/.doctrees/events/jgi-showcase-events.doctree b/.doctrees/events/jgi-showcase-events.doctree
diff --git a/.doctrees/events/mozfest2022.doctree b/.doctrees/events/mozfest2022.doctree
diff --git a/.doctrees/hazards/automates-decision-making.doctree b/.doctrees/hazards/automates-decision-making.doctree
diff --git a/.doctrees/hazards/danger-of-misuse.doctree b/.doctrees/hazards/danger-of-misuse.doctree
diff --git a/.doctrees/hazards/difficult-to-understand.doctree b/.doctrees/hazards/difficult-to-understand.doctree
diff --git a/.doctrees/hazards/direct-harm.doctree b/.doctrees/hazards/direct-harm.doctree
diff --git a/.doctrees/hazards/general-hazard.doctree b/.doctrees/hazards/general-hazard.doctree
diff --git a/.doctrees/hazards/hazard-template.doctree b/.doctrees/hazards/hazard-template.doctree
diff --git a/.doctrees/hazards/high-environmental-cost.doctree b/.doctrees/hazards/high-environmental-cost.doctree
diff --git a/.doctrees/hazards/lacks-community-involvement.doctree b/.doctrees/hazards/lacks-community-involvement.doctree
diff --git a/.doctrees/hazards/lacks-informed-consent.doctree b/.doctrees/hazards/lacks-informed-consent.doctree
diff --git a/.doctrees/hazards/ranks-classifies.doctree b/.doctrees/hazards/ranks-classifies.doctree
diff --git a/.doctrees/hazards/reinforces-biases.doctree b/.doctrees/hazards/reinforces-biases.doctree
diff --git a/.doctrees/hazards/risk-to-privacy.doctree b/.doctrees/hazards/risk-to-privacy.doctree
diff --git a/.doctrees/index.doctree b/.doctrees/index.doctree
diff --git a/.doctrees/labels.doctree b/.doctrees/labels.doctree
diff --git a/.doctrees/materials.doctree b/.doctrees/materials.doctree
diff --git a/.doctrees/materials/examples.doctree b/.doctrees/materials/examples.doctree
diff --git a/.doctrees/materials/misc/geno_to_pheno_example.doctree b/.doctrees/materials/misc/geno_to_pheno_example.doctree
diff --git a/.doctrees/materials/misc/proposal.doctree b/.doctrees/materials/misc/proposal.doctree
diff --git a/.doctrees/materials/misc/workshop-21092021.doctree b/.doctrees/materials/misc/workshop-21092021.doctree
diff --git a/.doctrees/materials/mitigation-resources.doctree b/.doctrees/materials/mitigation-resources.doctree
diff --git a/.doctrees/materials/presenting.doctree b/.doctrees/materials/presenting.doctree
diff --git a/.doctrees/materials/seedcorn.doctree b/.doctrees/materials/seedcorn.doctree
diff --git a/.doctrees/materials/self-assessment.doctree b/.doctrees/materials/self-assessment.doctree
diff --git a/.doctrees/materials/teaching.doctree b/.doctrees/materials/teaching.doctree
diff --git a/.doctrees/materials/workshop.doctree b/.doctrees/materials/workshop.doctree
diff --git a/.doctrees/materials/workshop/audience.doctree b/.doctrees/materials/workshop/audience.doctree
diff --git a/.doctrees/materials/workshop/facilitating.doctree b/.doctrees/materials/workshop/facilitating.doctree
diff --git a/.doctrees/materials/workshop/feedback.doctree b/.doctrees/materials/workshop/feedback.doctree
diff --git a/.doctrees/materials/workshop/project-owners.doctree b/.doctrees/materials/workshop/project-owners.doctree
diff --git a/.doctrees/materials/workshop/setup.doctree b/.doctrees/materials/workshop/setup.doctree
diff --git a/.doctrees/materials/workshop/structure.doctree b/.doctrees/materials/workshop/structure.doctree
diff --git a/_images/hazardanatomy.png b/_images/hazardanatomy.png
diff --git a/_panels_static/panels-bootstrap.5fd3999ee7762ccc51105388f4a9d115.css b/_panels_static/panels-bootstrap.5fd3999ee7762ccc51105388f4a9d115.css
diff --git a/_panels_static/panels-main.c949a650a448cc0ae9fd3441c0e17fb0.css b/_panels_static/panels-main.c949a650a448cc0ae9fd3441c0e17fb0.css
diff --git a/_panels_static/panels-variables.06eb56fa6e07937060861dad626602ad.css b/_panels_static/panels-variables.06eb56fa6e07937060861dad626602ad.css
diff --git a/_sources/about.md.txt b/_sources/about.md.txt
@@ -0,0 +1,227 @@
+# About
+
+The image below describes the 'anatomy' of a Data Hazard label.   
+
+```{image} images/hazardanatomy.png
+:width: 70%
+:alt: All Hazard labels have an descriptive icon, title, description, examples and suggesed safety precautions.
+```
+<br>
+
+<!--
+TODO: Alt text is too long and gives 'bad yaml' error. "An example layout of a label that says: every label has an image that represents the concept the label is describing. Title: a short descriptor less than 5 words. Description: the description makes it clear where the label would apply and, if necessary, how it interacts with other labels. Examples: examples are of situations where this hazard would apply. These could be news articles, research projects or tools. Safety Precautions: the safety precautions are very important and describe how researchers and developers could mitigate the potential harm from this label. This may include links to tools that can help (e.g bias checking for machine learning models)."
+-->
+
+## How the project started 
+
+The Data Hazards project started in 2021.
+We (Natalie Zelenka and Nina Di Cara) spoke together about wanting a way to communicate what might 
+go wrong in data science projects, because we were frustrated by the repetitive themes we were seeing 
+in harmful technologies that we talked about in [Data Ethics Club](https://dataethicsclub.com).
+We were also concerned that many projects that have significant societal impact do not have those impacts 
+scrutinised by an ethics committee, because they do not technically have research participants. 
+
+After this conversation we came up with the idea of Hazard labels for communicating these potential harms, 
+and called them Data Hazards. 
+We decided they should be visual, like COSHH chemical hazards are, and that they should be a way for 
+people at all stages of data science technology development to communicate about the same potential 
+outcomes (no matter how far away those outcomes might seem).
+
+You can see [the current Data Hazard labels here](labels).  
+You can [read our original proposal here](materials/misc/proposal).  
+
+These days the project is bigger than just us, and we have many contributors who suggest new content, 
+changes to the labels, help us to teach others about ethical hazards or run their own events. 
+If you would like to get involved (we'd love you to!) then we've listed lots of ways 
+you could on our [Contributing page](contribute).
+
+Once we had thought of the original list of Hazards we wanted a way for researchers to think about them in 
+a format that encouraged them to reflect, invite different opinions and make them think more broadly about 
+the potential ethical concerns from their project. 
+This led to the development of our workshop format and [all the materials we have since made](materials) 
+for self-reflection and teaching. 
+All our resources are designed (and licensed) for re-use by others. 
+
+
+## Ethos
+
+The Data Hazards are currently intended to be used creatively and flexibly, in whatever way they are useful
+to the user.
+Sometimes this means they are flashcards for teaching students about ethics, sometimes they are displayed with
+new research to communicate potential harms, and sometimes they are used in workshops as prompts.   
+
+We believe it is important when using the Data Hazards to help investigate risks in a project, that people 
+beyond the original researcher are consulted on potential hazards. 
+This is because we believe that knowledge, including in the sciences, is not objective, and that our 
+perspectives are shaped by our lived socio-political experiences (this is based on [standpoint theory](https://en.wikipedia.org/wiki/Standpoint_theory)).
+This means that ethical problems are not going to have a single correct answer, and that to get a well-rounded understanding of the ethical issues of any new technology we need people from lots of different standpoints to analyse it from their perspective. 
+This is the best way we can understand the harms it could possibly cause.
+We also need to make sure that we are paying attention to how technology might be more likely to adversely affect people from minoritised backgrounds.
+
+We developed our [workshop format](materials/workshop) to help researchers to gather these different views.
+
+In summary, the Data Hazards exist to prompt discussion, reflection and thought. 
+They are not a checkbox exercise, and there is no requirement for a group to come to a consensus. 
+In an individual context you will likely come to a conclusion, but someone else may have a different view.
+We hope that the Data Hazards discussion and reflective activities will help researchers be aware of a broader variety of potential ethical risks in tech projects, and that ethics is complex, situational and worth discussing.
+
+
+## Contact 
+
+The Data Hazards Project was founded by Dr Natalie Zelenka and Dr Nina Di Cara, and is now co-led by Natalie, Nina and Dr Huw Day. Our details are provided below.  
+We're always keen to hear from people interested in the project, or wanting to get involved. Feel free to send us both an email, or you can find us on Twitter!
+
+```{list-table}
+:header-rows: 1
+
+* - __Nina Di Cara__
+  - __Natalie Zelenka__
+  - __Huw Day__
+* - Senior Research Associate, School of Psychological Science, University of Bristol
+  - Senior Research Fellow in Health Data Science, Institute of Health Informatics, University College London
+  - Data Scientist, Jean Golding Institute, University of Bristol
+* - GitHub: [@ninadicara](https://github.com/ninadicara)
+  - GitHub: [@NatalieZelenka](https://github.com/NatalieZelenka)
+  - GitHub: [@HuwWDay](https://github.com/HuwWDay)
+* - Twitter/X: [@ninadicara](https://twitter.com/ninadicara)
+  - Twitter/X: [@NatZelenka](https://twitter.com/NatZelenka)
+  - Twitter/X: [@disco_huw](https://twitter.com/disco_huw)
+* - Email: [nina.dicara@bristol.ac.uk](mailto:nina.dicara@bristol.ac.uk)
+  - Email: [n.zelenka@ucl.ac.uk](mailto:n.zelenka@ucl.ac.uk)
+  - Email: [huw.day@bristol.ac.uk](mailto:huw.day@bristol.ac.uk)
+```
+<!--
+(project-timeline)=
+## Project timeline
+
+Here's a rough project timeline that tells the rough history of the project, and sometimes what we have coming up! 
+
+````{panels}
+:container: timeline
+:column: col-6 p-0
+:card:
+
+---
+:column: +left
+---
+:column: +entry right
+
+__March-April 2021__: Behind the scenes plans
+^^^
+
+{fa}`check,text-success mr-1` Thinking, reading and planning.
+
+{fa}`check,text-success mr-1` Writing [proposal](materials/misc/proposal).
+
+{fa}`check,text-success mr-1` Getting feedback on initial ideas.
+
+---
+:column: +entry left
+
+__May-Aug 2021__: Prepare for first Data Hazards workshop 
+^^^
+
+{fa}`check,text-success mr-1` Launched the website.
+
+{fa}`check,text-success mr-1` Submitted ethics application.
+
+{fa}`check,text-success mr-1` Prepare materials and begin advertising.
+
+{fa}`check,text-success mr-1` Set up [Open Science Framework project](https://osf.io/3fv7t/) and [preregister](https://osf.io/pcv7j) analysis.
+
+---
+:column: +right
+---
+:column: +left
+
+---
+:column: +entry right
+
+__Sept 2021__ Run first Data Hazards workshops (academic-focused)
+^^^
+
+{fa}`check,text-success mr-1` Ran the [first Data Hazards workshop](events/2021-09-21_workshop) on __21st Sept 2021__.
+
+---
+:column: +entry left
+
+__Oct 2021__ Use workshop feedback to improve data hazards and present early results
+
+^^^
+
+{fa}`check,text-success mr-1` Presented early results from workshop at [AI Ethics Best Practices and the Future of Innovation](https://www.eventbrite.co.uk/e/ai-ethics-best-practices-and-the-future-of-innovation-tickets-173883098027) as part of [Bristol Tech Festival](https://bristoltechfest.org/) on __13th Oct 2021__ ([slides](events/bristol-tech-fest)).
+
+{fa}`check,text-success mr-1` Used workshop feedback to make improvements to the Hazard labels and workshop materials.
+
+---
+:column: +right
+
+---
+:column: +left
+
+---
+:column: +entry right
+
+__Jan 2021__ Awarded £20,000 Enhancing Research Culture funding
+^^^
+{fa}`check,text-success mr-1` Set up our new project to deliver a 'train-the-trainer' for Data Hazards.
+
+---
+:column: +entry left
+
+__Feb-May 2022__ Developed new labels and facilitator training materials
+^^^
+{fa}`check,text-success mr-1` Hired animator to create animated explainers for Data Hazards and new Hazard labels.
+
+{fa}`check,text-success mr-1` Developmed and released run-your-own workshop materials. 
+
+{fa}`check,text-success mr-1` We went to MozFest 2022 to run a Data Hazards workshop!
+---
+:column: +right
+
+---
+:column: +left
+
+---
+:column: +entry right
+
+__June 2022__: Run our facilitator workshops
+^^^
+{fa}`check,text-success mr-1` Ran a Data Hazards workshop as part of the Jean Golding Institute Showcase.
+
+{fa}`check,text-success mr-1` Ran our first Data Hazards facilitator workshop in-person as part of Bristol Data Week.
+
+{fa}`check,text-success mr-1` Ran our second (online) Data Hazards facilitator workshop.
+
+---
+:column: +entry left
+
+__July-Dec 2022__: Prepare for first version release
+^^^
+
+{fa}`check,text-success mr-1` Analyse all the results and feedback from five total workshops.
+
+{fa}`check,text-success mr-1` Applied (successfully) for launch event funding from [UKRN](https://www.ukrn.org/about/).
+
+{fa}`check,text-success mr-1` Collect all previous suggestions for the project and think about future versions. 
+
+---
+:column: +right
+
+---
+:column: +left
+
+---
+:column: +entry right
+
+__March 2023__: Version 1.0 Release!
+^^^
+
+{fa}`check,text-success mr-1` Attend AI UK 2023 as exhibitors!  
+
+- 29th March we will run the Data Hazards V1.0 Launch event! 
+
+- We will release a pre-print of our first paper about the project! 
+
+````
+-->
diff --git a/_sources/contents/code-of-conduct.md.txt → _sources/code-of-conduct.md.txt b/_sources/contents/code-of-conduct.md.txt → _sources/code-of-conduct.md.txt
@@ -32,7 +32,7 @@ The below Do-s and Don’t-s are guidelines to remind us all of best standards o
 
 ## Reporting Procedure
 If you have been subject to or witnessed unacceptable behaviour, either during a meeting or on this repository, then you can get in touch with either Natalie or Nina.  
-Natalie: natalie.zelenka@bristol.ac.uk  
+Natalie: n.zelenka@ucl.ac.uk  
 Nina: nina.dicara@bristol.ac.uk  
 If you would prefer to contact someone who is not directly involved in organising the group, then you can direct your concerns to John Newby ([JGI Manager](http://www.bristol.ac.uk/golding/people/team/)), at [John.Newby@bristol.ac.uk](mailto:John.Newby@bristol.ac.uk)