Communications policies and processes – feedback requested

To help support a consistent approach to communications across the DataSHIELD community, we have developed a number of draft policies, processes and supporting resources. These have now been added to the Communications section of the Wiki for review.

:link: Communications Policies page: Community communications policies | DataSHIELD Community Wiki

These currently include:

  • Asset Library process (Zenodo)
  • Community website policy
  • LinkedIn policy
  • A number of draft communications policies, processes and decision trees

The aim of these documents is to provide a clear, consistent and supportive approach to managing DataSHIELD content, outputs and communications across the community.

We would be grateful if you could review these documents and provide any feedback, comments or suggested amendments by the Process Themes Meeting on 14 July 2026, so we can incorporate your input and move them forward towards final approval.

Please add your feedback directly within the documents where possible. Comments are encouraged to support the review process.

If you would like to contribute to the ongoing development of these policies and processes, please add your name to the list of contributors on the Communications Wiki page.

Your feedback will help ensure the guidance is practical, useful and appropriate for the wider DataSHIELD community.

Please note: Apologies that I haven’t been able to link directly to each individual document. As I’m still a new Wiki user, I’m currently limited to adding two links per post. Instead, I’ve linked to the Communications Policies page, where you’ll find an overview and access to all of the draft policies, processes and supporting documents.

Thank you in advance for your time and support.

Sian

Thanks for your message! I am currently on holidays from 25/05/26 until 30/06/26 and therefore not available. Your e-mail will not be forwarded.

Best regards, Florian Schwarz

Sian notifications@datashield1.discoursemail.com 29.6.26 15:17 >>>

Someone replied to a topic you are Watching.

| SianCunningham
29 June |

  • | - |

To help support a consistent approach to communications across the DataSHIELD community, we have developed a number of draft policies, processes and supporting resources. These have now been added to the Communications section of the Wiki for review.

:link:Communications Policies page: Community communications policies | DataSHIELD Community Wiki

These currently include:

  • Asset Library process (Zenodo)
  • Community website policy
  • LinkedIn policy
  • A number of draft communications policies, processes and decision trees

The aim of these documents is to provide a clear, consistent and supportive approach to managing DataSHIELD content, outputs and communications across the community.

We would be grateful if you could review these documents and provide any feedback, comments or suggested amendments by the Process Themes Meeting on 14 July 2026, so we can incorporate your input and move them forward towards final approval.

Please add your feedback directly within the documents where possible. Comments are encouraged to support the review process.

If you would like to contribute to the ongoing development of these policies and processes, please add your name to the list of contributors on the Communications Wiki page.

Your feedback will help ensure the guidance is practical, useful and appropriate for the wider DataSHIELD community.

Please note: Apologies that I haven’t been able to link directly to each individual document. As I’m still a new Wiki user, I’m currently limited to adding two links per post. Instead, I’ve linked to the Communications Policies page, where you’ll find an overview and access to all of the draft policies, processes and supporting documents.

Thank you in advance for your time and support.

Sian