DataSHIELD Community Governance Workshop

We invite members of the DataSHIELD community to participate in an online workshop to define the community governance and processes.

The objective of this participatory workshop is to discuss and agree issues related to DataSHIELD governance – specifically, governance of the community and community-level governance of data (e.g. quality assurance of DataSHIELD statistical code, preventing disclosure of individual participant data, and how to address the needs of Data Controllers). During the day we plan to work collaboratively on drafting texts that will guide the community structure.

Date and time: Thu, 17 March 2022, 09:30 – 15:30 UTC

Link to eventbrite sign up page:

There will be ample time for breaks!

1 Like

I have now posted the community structure that was agreed at the conference last year so that this can be used to guide discussions: DataSHIELD community structure and governance

1 Like

Here is some further information about the day.


The outline for the day will be as follows:

09:30 - Brief introduction (10-15 minutes) to explain the day

09:45 - ECOUTER session to get people’s input on values and code of conduct

10:00 - Breakout rooms to discuss/edit pre-prepared governance documents (each room focussed on one document and/or one section of a document) [This session will include 10-15 minute flexible break]

11:30 LUNCH

13:00 - Breakout rooms to review changes from the other rooms from the morning session

14:00 - BREAK

14:15 - Plenary session - reports back from the morning groups, including discussion session

15:30 - CLOSE

Background reading

In advance of the workshop, the DataSHIELD Advisory Board wanted to give attendees an opportunity to read some materials that will be the subject of discussion during the meeting.

Components of the DataSHIELD Constitution

  • Stakeholders, Roles, and Decision-Making Groups: MyPads

  • Steering Committee: MyPads

  • Decision-making and dispute resolution: MyPads

Each of these documents (above) will be discussed in one breakout room during the morning. In the afternoon session, participants will have the opportunity to review changes suggested by the other groups. There will then be a plenary session at the end of the day to allow everyone to discuss together. The hope is that these 3 components will be brought together into the DataSHIELD constitution defining governance in the DataSHIELD community… An example of how this could look in its entirety is at MyPads

Other documents

During the workshop we will also use Padlet ( - a virtual post it board tool - to explore DataSHIELD community shared values. Participation and comments in Padlet can be conducted anonymously requiring no registration, however if you are registered with Padlet contributions will have your name attributed to them. This feedback will be incorporated into the following draft DataSHIELD community documents:

  • Social contract: MyPads

  • Code of conduct: MyPads

  • Diversity and participation statement: MyPads

We look forward to welcoming you at the workshop, and shaping the future of the DataSHIELD community.


Registration for the event is now closed. However, if you wish to attend and didn’t get a chance to register, please contact me and we will add you to the list of participants and ensure you get the information (remember to include your email address!).

As a reminder, a diagram and brief explanation of the organisational structure that was agreed at the DataSHIELD conference in 2021 is displayed in the following thread:

Following a really productive Governance workshop yesterday, we wanted to thank everyone who participated - your contributions were very much appreciated. As developing these policies will take time, we also wanted to invite a member of the DataSHIELD Community to co-ordinate a working group to continue this work. If you’re interested, please post in the thread or contact Thank you.

Thanks for the recent workshop. I have come across FeatureCloud FeatureCloud, which has a lot of similarities with DataSHIELD. While I don’t want to get into the technical differences, it is interesting to note that they integrate community packages (they call them “apps”) by doing a audit of disclosure control, before they can be hosted in the app store.

It might be useful to see if they would share their experiences of the audit process?

I have also be pointed towards some contacts in the Galaxy project: The Galaxy Community - Galaxy Community Hub

They have a lot of experience about building this type of community so maybe we can also learn from them