---
title: "Case Study: Data Ethics and Reproducibility Symposium and Data Hazards Workshop"
source: The Turing Way
source_url: https://github.com/the-turing-way/the-turing-way
licence: CC-BY-4.0
domain: data-and-analysis
subdomain: turing-way
date_added: 2026-04-25
---

(er-datahazardscasestudy)=
# Case Study: Data Ethics and Reproducibility Symposium and Data Hazards Workshop 

As organisers, we (Ceilidh Welsh and Susana Roman Garcia) wanted to create an event that revolved around the {ref}`Data Hazards framework<er-datahazards>`. 
The event focused on showcasing how different people think about embedding ethics into the work that they do. 
As PhD students, we both felt the need to connect our interest in creating more ethical and reproducible work with our project's scientific questions. 
This passion for working more ethically brought us together, and we sought to see how other people are embedding ethics into their work. 
We hosted talks from PhD students who have been striving to make their work reproducible, how university lecturers might think of implementing Data Hazards into their material, and more (this is available in this {ref}`er-datahazardscasestudy-postevent-githubrepo`). 
We were able to connect with others, share knowledge and learn new skills throughout the process. 
In this chapter, we would like to share with you our experiences, including some of the challenges we faced, and provide tips for people hosting events in the future. 

(er-datahazardscasestudy-overview)=
## Overview 
The Data Ethics and Reproducibility (DER) Symposium was a one-day event held at the Alan Turing Institute on March 10th 2023. 
In total, we had eighteen attendees in person and eighteen attendees online, not including volunteers and hosts. 
This symposium aimed to showcase implementations of reproducibility and ethics for research, with a focus on Data Hazards.
The symposium structure included a variety of speakers, an interactive workshop and networking opportunities. 

A central part of this symposium was the {ref}`Data Hazards<er-datahazards>` Workshop to provide a collaborative training opportunity for attendees.
The workshop encourages attendees to explore, discuss and reflect on the ethical implications and wider societal impact of specific data-intensive projects. 
It was an opportunity for attendees to learn how to use the Data Hazards framework and see how it applies to different research projects.
This allowed attendees to appreciate that ethics is complex, situational and important to discuss in our own contexts.

```{note} 
**This case study is an account of our first-hand experiences organising and hosting an event. It may be useful to you if you would like to host or organise your own accessible workshop in data ethics and reproducibility (whether a Data Hazards workshop or not).**
```

For more detailed information and checklists, please see the Turing Way page for {ref}`Organising a Conference<cl-mec-organising-conferences>`.

(er-datahazardscasestudy-goals)=
### DER Symposium Goals

**Primary Goal:** to provide an open, inclusive and accessible space for attendees to learn from one another and discuss first-hand experiences applying ethics and reproducibility to their work. 
we hope to discuss the successes and challenges we might face, and importantly how to consider ethics as more than a tick-box exercise in a research project.

**Goals for Event Organisers:** 
To develop our skills in event management and organisation including:
-  hosting event platforms for attendee registration.
-  questionnaries and polls.
-  learn about accessibility considerations and requirements.
-  equality impact assessments. 

Importantly, we wanted to improve our collaborative, teamwork and networking skills with both volunteers and colleagues to provide a curated and thoughtful event.

**Goals for Event Attendees:** 
- Identify areas of research projects where wider ethical implications can be considered in different research contexts.
- Learn through a hands-on workshop how to embed ethics and reproducibility into current work or research.
- Discover what other attendees are working on in these areas.

(er-datahazardscasestudy-organising)=
## Organising the Event
Here we discuss the logistics for organising an event, from setting up and promoting the event on an external platform to collaborating with volunteers and speakers to help successfully run the event on the day. 

(er-datahazardscasestudy-organising-agenda)=
### Creating an Agenda:
The first step was to put together some initial ideas for the agenda.
We worked together using Google Docs. 
We used Google Docs because it allowed us to easily share the documents with other people, and it was easy to access.
We made sure that no private or sensitive data was in any publicly shared Google Docs. 
Our finalised agenda is [here](https://docs.google.com/document/d/13buQgzAbTTSWVtONXC3cnjegWapJ0CBkL7TBkqNNRqU/edit).
What did this process look like for us?
 - brainstorming themed talks,
 - deciding on keynote speakers, 
 - practicalities of running the [Data Hazards Workshop](https://datahazards.com/contents/materials/workshop.html),
 - identifying the symposium's target audience, 
 - planning the event start and end times, including rest breaks*, 
 - catering options,
 - deciding whether to run a hybrid event (online and in-person). Guidelines for hybrid collaboration and events can be found [here](https://book.the-turing-way.org/collaboration/hybrid-collab).
 
*To make the event more accessible, it was important for us to **make sure there were enough 'bio breaks'** to allow people to stretch their bodies, use the toilet and take a breather.

**Speakers**
A major part of putting together the agenda was all about picking our speakers.
Speakers are what made our symposium come alive, so we were eager to connect with different people to make sure our event had a mix of perspectives.

When looking for speakers we:
- reached out directly to keynote speakers whose research area or field considered data ethics and reproducibility.
- invited speakers from both inside and outside our organisation to include a variety of experiences. 
- asked for abstracts and titles, providing potential speakers with an estimated length of talk (including time for questions) and session they would present in.


(er-datahazardscasestudy-organising-advertising)=
### Advertising the Event

**Choosing a date and gauging interest:** 
Before even asking for funding, we wanted to know if there was enough interest to organise a symposium. 
So we reached out to our community *before beginning to organise* the symposium to gauge interest and spread the word. 
This allowed us to know what other events were going on in The Alan Turing Institute and research field so that we could avoid clashes or busy times of the year.

**Eventbrite:** 
After finding an available date for our interested participants, we chose to advertise our event on Eventbrite. 
At the time of running our event, we could host it for free for 30 participants.
However, as of now (November 2023), Eventbrite only allows you to host your event for free with up to 25 participants, then it charges you. 
Some alternatives you may use could be [Humanitix](https://humanitix.com/us/pricing), [Lu.ma](https://lu.ma/) or [eventsforce](https://www.cvent.com/uk).
Because we were running a hybrid event, we created two event pages (one [in-person](https://www.eventbrite.co.uk/e/in-person-data-hazards-ethics-and-reproducibility-one-day-symposium-tickets-516803953537) and one [online-only](https://www.eventbrite.co.uk/e/online-data-hazards-ethics-and-reproducibility-one-day-symposium-tickets-517490858087?keep_tld=1)). 
Eventbrite worked well for us because:
- it could be accessed by everyone, not just those in our organisation. 
- we could use it to gather participant information (clearly explaining why we were asking for the sensitive information and how the data would be handled), including accessibility information participants wanted to declare and dietary requirements.

**Communications**
To make sure we kept attendees engaged and up to date, we emailed them before the event to:
- encourage those who could no longer attend to cancel their reserved slot so that someone else could attend in their place. 
- provide a small nudge and reminder that the event is happening.
- provide participants with a code of conduct and agenda in advance.
- provide a Zoom link for online participants (one week in advance) and directions to the location of the symposium for those attending in person. 

This is what a template email could look like:

> Dear Participants,
> Thank you for registering for the *(In person) Data Hazards, Ethics and Reproducibility One-Day Symposium*, on the *10th March 2023*. 
> We hope you are as excited as we are about this symposium!
> 
> **Checking in: can you still make it?**
> We ask you to please be considerate and kindly let us know in advance if you can no longer make it to the event.
> This will help us reduce waste when ordering catering as well as help with organizing room numbers.
> Due to the high demand for this event, we have people on a waiting list, so please cancel your ticket in advance if you cannot make it any more, in order to allow someone else to join instead. 
> Please cancel directly through Eventbrite or by emailing the organisers.
> 
> **Agenda**:
> Please find the tentative agenda here (add your own link here). It is mostly set up now, please keep your eyes open for the final details in the coming days. We are looking forward to showcasing these wonderful people and talks.
> 
> **Code of Conduct**:
> We ask all attendees to familiarize themselves with the code of conduct for the event (add your own link here). Please do have a read in your own time in order to allow for an open and welcoming environment among all participants. 
> 
> **How to reach the Alan Turing Institute, Enigma room**:
> Once you arrive at the main Alan Turing Reception area, there will be someone there to greet you and guide you towards the Enigma room.
> Instructions on how to get to the Turing Institute can be found here (add your own link here).


(er-datahazardscasestudy-organising-collaboration)=
### Collaboration: 
The DER symposium had two primary organisers, however it would not have been possible without the help of different collaborators. 
Here we discuss the steps we took to reach out to volunteers, symposium collaborators and speakers to help the event run smoothly. 

**Internal Teams**
We had several collaborators from within our [organisation](https://www.turing.ac.uk/) including:
- the **Skills Team** who assisted us with:
    - completing equity, diversity and inclusion assessment and data protection forms.
    - understanding the financial requirements of the event, from paying speaker travel expenses to setting up a purchase order for an event caterer. 
    - providing grassroots funding to cover event expenses.
- the **Facilities Team** who assisted with:
    - delivery of the catering on the day.
    - room bookings to host the event. 
    - microphone and audio-visual set-up for the room to host the hybrid event. 

**Volunteers**
Volunteers were an essential part of the day, and our event would not have been successful without their help! 
For clear communication with volunteers, we:
- **provided an availability form** for volunteers to fill in, indicating specific sessions or hours they could help, what they would like to do, and their own accessibility requirements. 
- **hosted an on-boarding call** to talk through the agenda and highlight the parts of the day where we would require help from volunteers.
- **created a dedicated volunteer's Slack channel**, so that volunteers could ask questions relating to the event, and we could easily deal with any troubleshooting during the event.
- [**created a final volunteer's task form**](https://hackmd.io/c2AnZHeRRtWaA_QRwobjsQ), so that all volunteers had been assigned tasks before the event began 


(er-datahazardscasestudy-organising-catering)=
### Catering 
For our event we choose a local, entirely vegan caterer, to align with the core values of the event. 
To ensure successful ordering and delivery of the catering on the day we: 
- estimated the number of attendees to provide catering - including volunteers, speakers and organisers. 
- received a quote from the caterers in advance and ensured we had the budget to cover the quote.
- collected dietary requirements to ensure that all attendees were catered for, and ensured the catering company received these requirements in advance. 
- arranged a delivery time and location.
- ensured payment to the catering company as per company and organisation policies.

Tip: make sure terms and conditions are read and timing requirements from different parties involved are clear from the beginning. 
It might be that the caterer you are ordering from requires a purchase order to be completed at a certain time to complete the order action.


(er-datahazardscasestudy-hosting)=
## Hosting the Event 
There is already a chapter on {ref}`cl-mec-organising-conferences` which includes an in-depth dive into requirements for accessibility. 
Likewise, there is also a section for {ref}`cm-comms-overview-accessibly`.
As well as on {ref}`cl-mec-hybrid-collab-guidelines`. 

From our experience, here are some extra tips on the day of the event.

(er-datahazardscasestudy-hosting-startingevent)=
### Starting the Event 
- As the hosts arrive in person at least 1 hour before start time ensure the Zoom link and audio-visual equipment (speakers, screens and microphones) are all working.
- Open the online call early to allow for: 
    - volunteers to settle in and open any breakout rooms.
    - participants to join in advance and set up break-out rooms for networking events and workshops later in the day.

(er-datahazardscasestudy-hosting-hybridevent)=
### Hybrid Event Tips
We chose to host the symposium in a hybrid format as this would allow attendance for those interested in the topic, and speakers who would be unable to attend in person.
 
There are a lot of tasks involved in running a hybrid event. 
Thanks to good communication with volunteers and preparing the room before the event, our hybrid format ran successfully without hiccups.
Here we share some tips that helped us!

To ensure a smooth hybrid event, we:
- tested the physical room audio-visual the day before and the day of the event, to ensure there were multiple microphones and the capability for live Zoom recordings.
- had in-person session chairs to introduce speakers and make sure people (both online and in-person) kept to agenda timings.
- made sure session chairs were aware of the hybrid set-up, including microphones, speakers and Zoom settings,
- made sure that there was always at least one person in the room who was comfortable with the hosting technology.
- set a non-disruptive 1min warning, using a 1min sign to hold up in-person, or type into the chat online, to signal the end of the talk.
- kept questions to the end of the talks to avoid disruptions and talks becoming longer.
- kept in contact with online hosts throughout the day to ensure both the presentations and the audio were working.
- had our online volunteers keep track of break-out rooms, host discussions, and keep track of questions for Q&A sessions.


(er-datahazardscasestudy-hosting-accessibility)=
### Accessibility
Below we provide some insight into what was important for us to consider during the event.

**Code of Conduct**
We put together a code of conduct for the event that reflected our values and the values of the community we aimed to create during the symposium. 
It also summarised the expectations of participants joining the symposium and laid out reporting guidelines and contact points for if the code of conduct was breached during the event.

Please find our code of conduct [here](https://hackmd.io/@7D_si7-qQwKdepUrj7_AzA/DER_CoC).

Additionally, overall, below we highlight some points that we actioned to ensure that the hybrid format and the event were accessible:

- collected accessibility requirements at the time of advertising, to help with planning.
- used [Otter.ai](https://otter.ai/), a speech-to-text transcription application using artificial intelligence and machine learning. 
  It shows captions for live speakers and generates written transcriptions. 
  Note: Otter.ai is not always sufficient as it has been trained on English and American accents, so further editing of subtitles or transcripts might be needed.
- ensured all participants in person were using microphones when speaking.
  Microphones can be helpful for all hearing requirements, both online and in-person (don't assume everyone can hear equally).
- provided regular accessibility breaks. 
- reminded all participants which sections of the day would be recorded.
- provided a space for participants to include their names and pronouns using name labels for in-person and Zoom names online.
- provided a code of conduct, and contact points for if the code of conduct was breached.
- used the raised-hand function in Zoom for direct questions, but included a session chair to monitor for questions in the chat. 

(er-datahazardscasestudy-hosting-workshop)=
## Hosting a Workshop: Data Hazards  
The Data Hazards workshop was a key part of the symposium. 
Participants engaged with a real-life research case study, presented by the researchers themselves, to evaluate the Data Hazards labels and which ones may apply. 
The researcher gave a five-minute presentation on whole-cell models of _E. coli_. 
Participants could then ask the researcher only factual questions about the project, for example, 'where did you collect your data from?'.
There were opportunities for attendees, volunteers and the researcher to discuss the ethical context of the project.
We split the attendees into smaller groups to facilitate discussion and provide a series of prompt questions. 
Each group then labelled the research project with the hazards they thought applied. 
These were then fed back to the researcher for broader group discussions. 
Details of the workshop run on the day are available in the {ref}`er-datahazardscasestudy-postevent-githubrepo`. 

(er-datahazardscasestudy-postevent)=
## Post Event 
Once the event had finished we collected feedback from participants. 
Below we provide information on how we did this.

(er-datahazardscasestudy-postevent-feedbackforms)=
### Feedback Forms 
To cover all avenues for feedback after the event we: 
- provided a QR code and link to the feedback form in the final session of the day and encouraged participants to complete this form. 
- emailed participants after the event to thank them for their attendance and share the feedback form again.
- collected slides and recordings from speakers. 
- created a public Git repository where all content is openly available for attendees and those interested in organising and hosting a similar event.

Feedback is really invaluable to ensure that future organisers can learn from previous events. 
In our case, this was our first symposium, so feedback from participants was really important! 
Here we provide some feedback we were given after the event.

**Positive Feedback:**
- Attendees who came to the symposium with no experience of the data hazards enjoyed the interactive nature of the workshop, saying that: *'the structure of the course made it very easy to follow, and the case study element was very interactive with lots of opportunities to ask questions.'*
- Attendees also enjoyed the wide applications of data ethics and reproducibility in the research space. 
- Attendees enjoyed networking over lunch, and our [vegan catering](http://yellowkitchen.co.uk/) got lots of compliments! 

**Constructive Feedback:**
- Some attendees struggled with people joining and leaving parts of the online event but recognised this was out of the organiser's control.  
- A consideration for future events would be to create initiatives to encourage people to stay online for the whole day.
- Attendees felt that an additional industry perspective would have been beneficial.

(er-datahazardscasestudy-postevent-githubrepo)=
### GitHub Repository 
To embody the topics of reproducibility and open science, we have shared symposium content on a public GitHub repository. 
The aim of this is to help anyone who wants to run a workshop or symposium in the future consider the different elements of event organisation and hosting. 

Find our full GitHub repository, including recordings of speakers, code of conduct, and forms [here](https://github.com/Susana465/der_symposium_20230310). 

(er-datahazardscasestudy-challenges)=
## Challenges
As this was the first event (on this scale!) that we had organised, there were several challenges that popped up throughout the process. 

The primary challenge was understanding the number of hours required to organise an event. 
This event took over 50 hours of organisational time over a period of three months, from requesting funding, form writing, code of conduct, creating the event page, advertisement, organising catering and so on. 
If this is the first time you are organising an event, different tasks may take longer than expected to complete. 
We would recommend you establish a large organising committee of passionate people, to work together and split tasks efficiently.  
It is also important to recognise the boundaries and constraints of how long you are willing to spend organising an event. 
Don't let perfection be the enemy of good! 
This also taught us that organising an event will **always** take longer than you expect, so plan accordingly! 
 
(er-datahazardscasestudy-reflections)=
## Reflections 
After the event, we realised that it is important to understand your organisation's guidelines and frameworks for hosting events, what support they can offer you, and reach out to ask for help where you need it. 

In our experience organising and hosting an event was both stressful and fun!

Hosting a hybrid event was challenging and required extra organisation and volunteers.
But after all the effort we put into it, it ran smoothly and we were very proud to have both online and in-person attendance. 

We also recognise the importance of {ref}`self reflection<er-self-reflection>` throughout the process of organising an event, and how our lived experiences gave us a particular lens on how we view the world. 
So ensuring we collaborated with others, and took on different points of view ensured a responsible, inclusive, and fair event!
