Commit 341a4cda authored by Cassandra Gould van Praag's avatar Cassandra Gould van Praag
Browse files

add docs

parent 74ad9b45
Pipeline #9421 passed with stages
in 1 minute and 41 seconds
title: Acknowledgements
parent: Home
has_children: false
nav_order: 4
# Acknowledgements
{: .fs-9 }
We are grateful to the following resources for inspiration and shared documentation used to develop this repository
{: .fs-6 .fw-300 }
Materials within this repository were developed with the support of the [Open Life Sciences (OLS) Mentoring Program](, with the kind assistance of [Naomi Penfold]( 🙏
The community strategy has been developed using materials shared by the [Center for Scientific Collaboration and Community Engagement - CSCCE]( - community of practice. Guidance in community management and support has been generously provided by members of CSCCE. 🙏
Other resources have also been developed following example materials developed by [The Turing Way]( 🙏
`The Turing Way Community, Becky Arnold, Louise Bowler, Sarah Gibson, Patricia Herterich, Rosie Higman, … Kirstie Whitaker. (2019, March 25). The Turing Way: A Handbook for Reproducible Data Science. Zenodo`
The Ambassadors scheme has been modelled on materials available from the [TU Delft Data Champions program]( 🙏
Resources for creating the our community documentation hackathons have been created using templates and structures devised for the [Organisation of Human Brain Mapping]( [Open Science Special Interest Group]( [Hackathon 2020]( 🙏
`Remi Gau, Liza Levitis, Dorien Huijser, Camille Maumet, Steffen Bollmann, Anibal Sólon, … Kanishk Kalra. (2020, August 25). ohbm/hackathon2020: post-hackathon-20200825 (Version v0.0.1). Zenodo.`
Figures have been created from images in the [Noun Project]( repository, contributed by [Alice Design](, [Andrejs Kirma](, [DinosoftLab](, [Luis Prado](, [Sergey Demushkin](, [Thuy Nguyen](, [vectlab](, and [Victor Llavata Bartual]( 🙏
title: Contributing
parent: Home
has_children: false
nav_order: 3
# Contributing
{: .fs-9 }
How to contribute to this repository
{: .fs-6 .fw-300 }
We want to ensure that every user and contributor feels welcome and included in the WIN Open Neuroimaging community. We ask all contributors and community members to follow the [code of conduct](/community/ in all community interactions.
**We hope that this guideline document will make it as easy as possible for you to get involved.**
Please follow these guidelines to make sure your contributions can be easily integrated in the projects. As you start contributing to the WIN Open Neuroimaging, don't forget that your ideas are more important than perfect [pull requests](
## 1. Contact us
In the first instance, we encourage you [connect with the Open WIN Community]( Let us know that you are reading the repository and you would like to contribute! You might like to introduce yourself on the #welcome channel on our [Slack workspace](! 👋
## 2. Check what we're working on
You can see the things we are working on in the [Open WIN Repository Trello board]( Have a look through and see where we have known gaps. You are also welcome to suggest any of your own improvements.
We also invite you to review our [roadmap](community/ and see how we are progressing against our community milestones.
## 3. Join us at a documentation hack!
We will be holding regular "documentation hacks", where you will be guided through the process of contributing to the repository, and can participate in a git tutorial if you'd benefit from this. Take a look at our [events page]( to find out when the next documentation hack will be held.
At the documentation hack, you will hear from members of the [Open Neuroimaging Project Working Groups]( and learn about the progress of each tool. You will learn how to use each tool, be invited to contribute feedback to the tool developers, and invited to write "how to" guides to walk novice users through the process of shearing their research outputs using the [Open WIN Tools](
We will also use the documentation hacks to plan as a community, learn about what policy or guidance we need to support working open at WIN, and think about how we would like to develop. This will include community-led planning of the [Open WIN Ambassadors scheme](
## Or, 4. Jump straight in!
If you are confident using git, markdown, and github pages, you are very welcome to [submit an issue to our github repository](, and [submit a pull request](
Coming soon
{: .label .label-yellow }
We will add git and contribution training materials after our first documentation hack, to be held in [October 2020](events/
title: License & Citation
parent: Home
has_children: false
nav_order: 5
# License and citing this repository
{: .fs-9 }
How to reuse and credit resources in this repository
{: .fs-6 .fw-300 }
The materials contained within this repository are distributed under [CC-BY-4.0](
**You are free to**:
- **Share**: copy and redistribute the material in any medium or format.
- **Adapt**: remix, transform, and build upon the material for any purpose, even commercially.
**As long as you**:
- **Attribute**: must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
# How to cite this project
Coming soon
{: .label .label-yellow }
A citable digital object identifier (DOI) for this repository will be created using [Zenodo]( Please check back for a complete citation, including contributing authors.
title: Open WIN Ambassadors
has_children: true
nav_order: 5
# Open WIN Ambassadors
{: .fs-9 }
Find out about our plans for the Open WIN Ambassadors scheme
{: .fs-6 .fw-300 }
The WIN Open Ambassadors will be a team of individuals who are significant contributors to the Open WIN Community. We intend to launch the Ambassador program in 2021, after we have worked with the community to devise the structure and expectations of the program.
**See the sections below or navigate on the sidebar to find out more about the proposed Open WIN Ambassadors.**
title: Benefits for Ambassadors
parent: Open WIN Ambassadors
has_children: false
nav_order: 6
# Benefits for Ambassadors
{: .fs-9 }
Find out about how the benefits of becoming an Open WIN Ambassador
{: .fs-6 .fw-300 }
In recognition of the time, skill and expertise it takes to be an Open Ambassador, you will receive a number of benefits for taking part. These may include:
- Ambassador profiles on this repository
- Named authorship on the repository citation
- Recognition of your contribution on your annual personal development review
- Opportunities to network with likeminded colleagues internally and externally
- Opportunity to shape the policy, structure and governance of the Open WIN Community
- Career advancement and exposure
- Access to a dedicated training and development fund to support your growth in open research or a related topic
- Approved time with your line manager to contribute to these activities
- Merchandise! You want a mug?! We could get mugs! ☕️ 😅
What else would you like? We're aiming to solve the problems which you face, or your barriers to working open. Why do you want to participate? What would motivate others like you?
## Career advancement and exposure
Engaging with open research is good for your CV as many funding and fellowship applications are now requesting and recognising research outputs other than solely papers. For example, preprints, code, datasets and documentation can all be referenced with a digital object identifier (doi) and cited as research outputs. Our hope is that any user of the Open WIN Tools will be able to produce some non-traditional research outputs, however we expect that Ambassadors will stand out as deeply committed to this work.
Ambassadors will have the opportunity to devise and deliver training on these tools, and potentially lead sub-teams who are working on a specific output. These are both excellent experience and opportunities to show leadership on your CV.
Active participation in this community is also evidence of "Good Citizenship" which can be discussed in new employment and promotion applications. It may involve engaging with Senior Management on committees, and you will have the opportunity to learn about background processes in academic life which early career researchers are often not exposed to.
title: Expectations of Ambassadors
parent: Open WIN Ambassadors
has_children: false
nav_order: 5
# Expectations of Ambassadors
{: .fs-9 }
The behaviours and activities we would like Ambassadors to commit to
{: .fs-6 .fw-300 }
We would like WIN Open Ambassadors to be aligned with the following activities:
- Commitment to learn about open research practices, understand own knowledge gaps and know where to signpost effectively
- Act as advisors/mentors to other researchers in their research groups, Department and WIN
- Advocate for open research practices an the use of Open WIN Tools in their research groups, Department and WIN
- Speak to researchers about their own experience with open research practices and infrastructure during research group and Departmental presentations and training events
- Participate in Ambassadors meetings once every two months
- Participate in termly co-working hack days where possible
- Engage in community activities for 2-8 hours per month, in addition to the above meeting schedule
In return for their time and commitment, various [rewards and incentives]( will be offered to those who become WIN Open Ambassadors.
We will work to support Ambassadors in all these activities, with communication channels, training, presentation materials and defined routes of development. This support will develop as the project grows, and you will have an open invitation to suggest any additional ways we could support you in growing our community.
title: Goals of the program
parent: Open WIN Ambassadors
has_children: false
nav_order: 2
# What are the goals of the Ambassador program?
{: .fs-9 }
Find out about why we are running the Ambassador program and what we hoe to achieve.
{: .fs-6 .fw-300 }
Coming soon
{: .label .label-yellow }
We have created the ambassador program to ensure as many people as possible can access the sharing infrastructure created by the Open Neuroimaging Project.
We would also like to create opportunities for our community to engage learn best practice in open research, connect with each other, develop their experience and boost their CVs with open research outputs!
We also wanted to create a feedback system where our community of users can shape the environment which they work in. We are at the leading edge of these initiatives, and we firmly believe that our users are excellently positioned to contribute to the future of such efforts.
We have specific goals for engagement which are driven by the project metrics which communicated to the [External Advisory Board (EAB)]( who are tasked with providing "an external and independent view on plans and progress" of WIN. <mark> Can the 2018 EAB report be shared on intranet too? - yes. </mark>.
We also have a goal to show a year-on-year growth in understanding and engagement with open research practices, as measured by the [WIN 2019 Open Science Survey]( and the
Based on these combined drivers, our initial goals are to:
## Demonstrate infrastructure engagement
Open Data
- Number of WIN researchers with database accounts
- Percentage of WIN researchers actively using the database
- Number of scans in the database
- Number of studies in the database
- Number of studies shared across WIN
- Number of studies shared externally
- Number of external requests to access studies
Open Paradigms
- Number of paradigms published on the website, potentially number of visits to the site
- Uplift in supporting documentation standards <mark>Added by CGVP. Much of the paradigms repo is pretty near unusable as so little documentation.</mark>
Open Protocols
- Number of protocols openly published in database
- Number of visits to the database and number of downloads
- Number of citations/acknowledgements of protocols used from the database
Open Tools
- Number of FSL tools that have singularity outputs
- Number of downloads of tools with singularity outputs
- Number of publications using singularity outputs
- Number of BIDS meetings attended
Open Community
<mark>TBC and consider more</mark>
- Number of Ambassadors
- Number of users on mailing lists and number of messages <mark>Can we look back at this historically?</mark>
- Number of users (active and inactive) on slack
- Number of contributors to this repository
- Number of enquires (and responses) made to Ambassadors
- Number of attendees at hack-day
- Feedback from hack-day
## Improve awareness and experience with open research practices
- Increase in the number of open access papers immediately available
- Improve awareness of open research practices, particularly registered reports and open educational materials.
- Encourage the community to share pre-prints of their papers.
![OS-Survey 2019 slide 3](../img/open-science-survey-results/Slide3.png)
- Appreciate the value of open science practices in career development
![OS-Survey 2019 slide 4](../img/open-science-survey-results/Slide4.png)
- Appreciate the value of open sharing of code.
- Encourage the community to realise the value of sharing data within the current limits of our [open data policy](, and equip them with the tools and knowledge to do so.
![OS-Survey 2019 slide 5](../img/open-science-survey-results/Slide5.png)
## Reduce barriers to engaging in open research practices
- Devise and promote positive incentives for open research within WIN.
- Clarify and communicate legal and ethical obligations fo data sharing.
- Promote and train the community to use the newly developed WIN Open Infrastructure for sharing [data](, [experimental paradigms](, [acquisition protocols]( and [analysis tools](
![OS-Survey 2019 slide 6](../img/open-science-survey-results/Slide6.png)
![OS-Survey 2019 slide 7](../img/open-science-survey-results/Slide7.png)
## Create and share documentation
- Empower the community to learn together as we explore these topics, and share their knowledge on this repository <mark>update when moved</mark> in the form of written documentation.
- Hold in-person and online training workshops and "hacks" where we can learn together and create documentation.
![OS-Survey 2019 slide 8](../img/open-science-survey-results/Slide8.png)
title: Logistics
parent: Open WIN Ambassadors
has_children: false
nav_order: 1
# Logistics
{: .fs-9 }
Find out about our proposed logistics of running and participating in the Ambassadors program
{: .fs-6 .fw-300 }
Below we have answered some questions about how the pilot Ambassadors program will be structured. Jump straight to one of the questions or go through them all!
* [How many Ambassadors will take part in the pilot program?](#how-many-ambassadors-will-take-part-in-the-pilot-program)
* [How will the Ambassadors work together?](#how-will-the-ambassadors-work-together)
* [How long will Ambassadors be in-post for?](#how-long-will-ambassadors-be-in-post-for)
* [Who can be an ambassador?](#who-can-be-an-ambassador)
* [How can I become an Ambassador?](#wow-can-i-become-an-ambassador)
# How many Ambassadors will take part in the pilot program?
In this pilot program, we will look to engage up to ten Ambassadors. Ultimately we would like to have an Ambassador in each of the WIN research groups.
# How will the Ambassadors work together?
While working on creating documentation, we would like to have teams of two people working on each of the four focus areas of the infrastructure tools and a team working explicitly on community and policies. In all these efforts, all Ambassadors will be invited to contribute to the material and efforts of other teams, if they so wish.
# How long will Ambassadors be in-post for?
The pilot program will run from September 2020 to September 2021. All recruited Ambassadors will be expected to remain engaged with the program for this period, and should have confirmed posts as WIN members during this whole period.
# Who can be an ambassador?
Anyone! Student, postdoc, core staff, professional services...
# How can I become an Ambassador?
A competitive application for this program will be launched in September 2020. As part of the application you will be expected to describe why you are interested in becoming and Ambassador, what you will bring to the Ambassadors team and wider community, and what you will gain from being an Ambassador. You will also be asked to produce a letter of confirmation from your Supervisor or line manager stating that they support your engagement with the program and will allow you time away from your existing duties to take part in events and contribute between meetings.
title: Open WIN Community
has_children: true
nav_order: 4
# Open WIN Community
{: .fs-9 }
Find out about the Open WIN Community, what we're doing, and how you can be a part of this effort.
{: .fs-6 .fw-300 }
## What are we doing?
We are a community built from around 250 members of the University of Oxford [Wellcome Centre for Integrative Neuroimaging (WIN)]( Our community exists to support open and inclusive researchers, to develop the tools, policies, governance and structures we would like in place to support us in practicing open science.
We are committed to supporting transparent and reproducible research practices within WIN, to improve the efficiency and accuracy of our research, and contribute to an equitable, diverse and inclusive research environment.
**See the sections below or navigate using the sidebar to find out more about the Open WIN Community.**
## Join the community
If you are interested in learning more about open research, incorporating open research practices in your research, or developing resources to make open research at WIN easier and well incentivised, you should be member of our community!
👋 Subscribe to the [Open WIN mailing list]( to find out about events and resources as they are shared.
👋 Say "hello" on our [Slack workspace]( to follow and contribute to discussions about the [Open WIN Tools](, [events]( or plans for the community.
👋 [Comment on this GitHub repository](, add an issue or submit a pull request to suggest changes to this documentation.
👋 [Email the Open WIN Community Coordinator]( to introduce yourself, or ask a question about any aspect of this repository or the work of the Open WIN Community or Working Groups.
title: Participation Guidelines
parent: Open WIN Community
has_children: false
nav_order: 7
# Participation Guidelines
{: .fs-9 }
How Open WIN Community members are expected to work, communicate and interact with each other, so we can all perform at our best.
{: .fs-6 .fw-300 }
## Guiding principles
We value the participation of every member of our community and want to ensure that every contributor has an enjoyable and fulfilling experience.
Accordingly, everyone who participates in the Open WIN Community is expected to show respect and courtesy to other community members at all times.
Cassandra Gould van Praag, as [Community Engagement Coordinator]( of this project, and all project members, are dedicated to a ***harassment-free experience for everyone***, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion or technology choices. **We do not tolerate harassment by and/or of members of our community in any form**.
## Traditionally under-represented groups
We are particularly motivated to support new and/or anxious contributors, people who are looking to learn and develop their skills, and anyone who has experienced discrimination in the past.
We invite all members of this community to actively support the participation of under-represented individuals through recognition of our own privilege and consideration of [how we can use our privilege to benefit others](
We work closely with the [WIN Member Networks]( to ensure that the behaviours we model and the materials we produce are aligned with best practice in establishing equality, diversity and belonging.
## Formal policy
This community is designed to serve individuals affiliated with WIN, and as such these individuals will all be expected to comply with [University of Oxford Harassment Policy]( and the reporting procedures detailed in that policy.
We will begin events with a reminder of the Harassment Policy and expected behaviours. Anyone who experiences or witnesses a violation of the Harassment Policy is encouraged to address the incident directly where they feel safe to do so, or follow the reporting guidelines to escalate where necessary.
**Advice on how this policy is implemented and where you can receive support in these matters is available from the [University Equality and Diversity Unit](**
## Being a responsible bystander
In this community we value efforts to promote a positive work environment, free from intimidation and all forms of violence. We are therefore pleased to support the University in enacting the Harassment Policy by acting as responsible bystanders, and doing what we can to promote a safe and conducive work environment. We encourage all community members to be responsible bystanders.
title: Accessibility statement
parent: Open WIN Community
has_children: false
nav_order: 8
# Accessibility statement
{: .fs-9 }
Accessibility Statement for the Wellcome Centre for Integrative Neuroimaging’s Open Science Websites
{: .fs-6 .fw-300 }
The Wellcome Centre for Integrative Neuroimaging (WIN) is committed to providing an accessible web presence that gives members of the public and members of the WIN community full access to centre information, courses and activities offered publicly through the web. Our [Equality Policy]( outlines our commitment to a culture which maintains a working, learning and social environment in which the rights and dignity of all its staff and students are respected.
This accessibility statement applies to University of Oxford, Wellcome Centre for Integrative Neuroimaging’s Open Science Websites listed below:
1. [](
2. [](
3. [](
## Our Aims
These websites are run by WIN’s Open Science team. We want as many people as possible to be able to use these websites. For example, that means you should be able to:
- Change colours, contrast levels and fonts
- Zoom in up to 300% without the text spilling off the screen
- Navigate most of the website using just a keyboard
- Navigate most of the website using speech recognition software
- Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
[AbilityNet]( has advice on making your device easier to use if you have a disability.
How accessible this website
We are aware that some parts of our website are not fully accessible.
These include:
- Not all images have a meaningful text alternative
- Some images include text as part of the image
- Some images do not include sufficiently detailed captions
- Hyperlinks throughout website have a low contrast
- Some hyperlinks are not described sufficiently for screen readers to identify
- Website cannot be effectively navigated by keyboard
- Some subheadings do not have the correct styling so cannot be read effectively by a screen reader
We are working to address areas where our accessibility needs improvement. Please see our ‘Known issues’ page for more details.
## Feedback and Contact Information
If you need information on this website in a different format, please contact WIN’s administrative team:
Email: [](
Postal address:
WIN Administration Team,
Wellcome Centre for Integrative Neuroimaging,
FMRIB Building, John Radcliffe Hospital,
OX3 9DU.
We will consider your request and get back to you within 14 days.
## Reporting accessibility problems with this website
We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact:
WIN Administration Team,
Wellcome Centre for Integrative Neuroimaging,
FMRIB Building, John Radcliffe Hospital,
OX3 9DU.
## Other accessibility resources
If you’d like more information about accessibility and resources for students, staff and visitors in Oxford more generally, please visit the [University of Oxford’s Equality and Diversity pages](
If you’re looking for information on building accessibility, please try the [Access Guide]( or the [University’s interactive map](
## Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the [Equality Advisory and Support Service (EASS)](
## Technical information about this website’s accessibility
The Wellcome Centre for Integrative Neuroimaging, University of Oxford is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
This website is partially compliant with the [Web Content Accessibility Guidelines version 2.1]( AA standard, due to the non-compliance and exemptions listed on our ‘Known Issues page’.
## Known Issues page
### Non-compliance with the accessibility regulations
The content listed below is non-accessible for the following reasons:
### Issues with images
#### Images
- Some images do not have a meaningful text alternative or sufficient captions, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1.
By October 2021, all images will have meaningful text alternative. Purely decorative images will have blank alternative text and infographics and charts will have a link to a full description of the content.
- Some images include text as part of the image, so people using a screen reader cannot access the information. This fails the WCAG 2.1 success criterion 1.4.5.
By October 2021, all images containing text will have a suitable text alternative to include the image text.
### Issue with hyperlinks, subheading formatting and keyboard operability
#### Hyperlinks
- Some hyperlinks throughout websites have too low of contrast, which can result in text being difficult to read, especially for people with low vision, poor eyesight or colour blindness. Additionally, some hyperlinks are not sufficiently describe making it difficult to determine purpose when using screen reader. This fails the WCAG 2.1 success criterion 1.4.1.
All hyperlinks will have a standard 3:1 contract ratio and will be sufficiently described by October 2021.
#### Subheading formatting
- Not all subheadings have been formatted correctly using styles, making the site more difficult for users of assistive technology such as screen readers to access. This fails the WCAG 2.1 success criterion 1.3.1.
Ensure all subheading have been formatted using styles by October 2021.
#### Keyboard operability
- Some menus, links, buttons, and other controls cannot be operated using the keyboard alone, which can cause problems for people who are blind, have low vision and/or hand tremors. This fails WCAG 2.1 success criterion 2.1.1.
We are working with our developers (GitHub) to implement fixes for these keyboard operability issues over the coming months.
#### Issues with Content Management System (CMS)
- The CMS code is being checked to ensure that it meets the robust accessibility criteria 4.1.1, 4.1.2 & 4.1.3.
This will be done as part of an accessibility review of the GitHub Content Management System to be completed in Autumn 2020.
#### Disproportionate burden
We do not consider any of the accessibility issues to be a disproportionate burden and aim to make the site fully compliant by October 2021.
#### Content that’s not within the scope of the accessibility regulations
##### Third-party content
Our site includes third party content and functionality. This may direct you to a related service, link to another site or supporting documentation. We are not responsible for the accessibility of third-party content or to other sites we link to.
This includes:
- Slack
- Google Calendar
- Mozilla GitHub
We will provide an accessible alternative to any third-party content that isn’t compliant.
##### Third party platforms
We often create content which is hosted on third party platforms. This includes:
- Content we create for social media
- Data we supply to national databases
We are responsible for ensuring the content we supply meets accessibility requirements. However, we are not responsible for the accessibility of the platform itself.
## What we’re doing to improve accessibility
We want to provide the best possible experience for all our website visitors. To achieve this, we will:
- Fix known issues
- Check all new features in the GitHub and WIN Content Management System (CMS), which is used to create this website, for accessibility before they are made available
- Check all new content for accessibility
- Train all content editors on accessibility
- Carry out periodic accessibility checks involving WIN’s accessibility forum, WIN Access
## Preparation of this accessibility statement
This statement was prepared on 22nd October 2020. It will be reviewed again in February 2021.
This website was last tested in October 2020. The test was carried out by the Wellcome Centre for Integrative Neuroimaging’s Administration Team using all pages. The CMS has been audited for accessibility by the suppliers (GitHub) and the Wellcome Centre for Integrative Neuroimaging Administration Team. A full copy of the audit results is available by request from the [Open Science Community Coordinator](
The pages were checked manually using a combination of the following methods:
- Checked against WCAG 2.1 guidelines, with a focus on the items in the [ WCAG 2.1 Primer Checklist](
- Viewed without style sheets
- Viewed on a small screen
- Checked using the WebAim’s Web Accessibility Evaluation Tool
- Google’s Lighthouse extension plug in application
title: Community Goals
parent: Open WIN Community
has_children: false
nav_order: 3
# Community Goals ⚽️
{: .fs-9 }
What we aim to achieve and how we will get there
{: .fs-6 .fw-300 }
# Why have we come together?
Funders and the Management Board of WIN have committed to develop both the infrastructure and culture to support ‘open neuroimaging’. There has been significant investment in computational infrastructure to support researchers in sharing their data, data acquisition methodology, experimental tasks and analysis code, in an open, transparent and reproducible manner.
As these stages near completion, we are entering the second phase of work to build awareness, provide training and increase uptake in the use of this infrastructure. The problem is that until now there have been no centralised resources, communication structures or identified community strategies in place to support researchers in using this new infrastructure.
# How will we achieve our goals?