alan-turing-institute / TuringDataStories

TuringDataStories: An open community creating “Data Stories”: A mix of open data, code, narrative 💬, visuals 📊📈 and knowledge 🧠 to help understand the world around us.
Other
39 stars 12 forks source link

Turing ethical approval process #118

Closed crangelsmith closed 3 years ago

crangelsmith commented 3 years ago

Summary

After discussing with @Ismael-KG we decided to go ahead with the Turing Ethics approval for the TDS project. In this approval from we have to:

Ismael’s secret guide to answering the EAC form: https://hackmd.io/DneAaMlYSnaPlsHqzskwDQ

What needs to be done?

Who can help?


Updates

crangelsmith commented 3 years ago

Notes from @samvanstroud

Adding Ethics to TDS

five safes: https://www.ukdataservice.ac.uk/manage-data/legal-ethical/access-control/five-safes

We can use the "five safes" framework as a reference, though it is not directly applicable. We can also use the questions in the EAC form and make sure these are represented in our review process (since our review process is effectively re-implementing the EAC form)

We should also make ethical considerations known at the beginning of story-writing, so that someone doesn't end up writing a story only to be told that it is not publishable.

Answering the EAC form

slack link to form: https://turingdatastories.slack.com/files/U01C263RDMF/F01JEDDRC5C/eag_application_practice_form.docx

crangelsmith commented 3 years ago

A comment from Kirstie in the slack to keep track of:

@Camila - if you can incorporate SUM and FAST that would be really great - they were developed here at the Institute and I think they should be a very useful frame work for you to build a process around. I'm worried that the document will make you feel like you (and the team) have to do huge amounts of work. I don't think that's true. The principles are primarily directed at companies and government algorithms. The Data Stories projects are not likely to carry anywhere near the harms associated with those implementations so you probably just need a lightweight implementation with an escalation process for ideas that aren't immediately easy to approve!

crangelsmith commented 3 years ago

Notes from meeting on the 20th of January:

For example, today we discussed a couple of ideas:

  1. We are focusing on the educational side of the material we are producing, so we can allow contributors to explore different ideas but we should be careful in allowing conclusions that can be controversial (go on the conservative side here).
  2. We hope that between the authors and reviewers all ethical concerns can be solved with discussion and suggestions on changing the narrative/conclusions.
  3. If reviewers and authors do not agree in a statement or analysis due to ethical concerns we could bring a third party to solve (who will be the third party?).
samvanstroud commented 3 years ago

Coming up with our ethical review process: https://hackmd.io/W-ZGyC-GQbCnMEcwRM4xlw

crangelsmith commented 3 years ago

Notes from meeting on 27th Jan:

Today @DavidBeavan , @samvanstroud and @crangelsmith gave it a go in writing the ethical guidelines for the submission of a TDS, in this document there is a first draft.

Next week we will continue working on the draft. Things that we need to do:

DavidBeavan commented 3 years ago

These published ethical approval requests are far bigger in scope that Turing Data Stories, but may be useful:

kevinxufs commented 3 years ago

Hi @crangelsmith @DavidBeavan @samvanstroud great work with the initial draft for the ethical approval. I think it is shaping up nicely and I just had a few small comments. They are mostly targeted at the following to check boxes:

The proposed data story aims to serve the public good and/or promote positive change and follow the SUM Values described in our code of conduct…

- [ ] Could conducting or promoting this data story create unintended negative outcomes, such as reputational harm?

I think we should be a bit more explicit here as to what we think are positive and negative outcomes. One might find 'public good' and 'positive' to be a bit vague and subjective. For example, perhaps to me just making true things known might constitute a 'public good', but one might instead think 'public good' involves focusing our stories specifically on making known injustices (e.g. Covid deprivation link). Similarly, I feel like reputational damage is one the lesser ethical concerns. Instead what we're presumably worried about are people taking our stories out of context and using it drive forward some sort of potentially discriminatory agenda. It gets messy here because we want to balanace our objective analysis with political considerations of how people might respond to them. There's a sense in which we also want to remain politically impartial in our analysis.

I suspect our best approach is to take a somewhat dogmatic stand here.

E.g.

Stories need to be truthful and clear about limitations of analysis (and potential biases in data). Reviewers should consider if there any obvious ways a story might be construed that would lead to negative social outcomes such as worsening discrimination, injustice, environment, personal attacks etc.

kevinxufs commented 3 years ago

@crangelsmith @DavidBeavan @samvanstroud

Many thanks all for the first draft on this document

Overall I think it looks really good. I've made some very slight wording changes and fixed a few typos, but the content is great.

I had a small question regarding section 5, under the heading: Where you identify risks, you should inform us how your research plans to minimise or eliminate them.

There are a number of questions here - were these questions part of the approval process, or were they suggested by us? If it is the latter, I think we just need a line saying Reviewers will be expected to consider the following kinds of ethical questions as part of their review process

crangelsmith commented 3 years ago

Hi @Ismael-KG, we have a first complete draft of the application form in this document (we plan to move all this text into the actual word document once we are happy with the content).

Could you give us your feedback on this draft before we submit the application? Comments on this issue or in the hackmd document are good. Thanks for your help :)