Link Search Menu Expand Document

What are the goals of the Ambassador program?

Find out about why we are running the Ambassador program and what we hoe to achieve.


Coming soon

THIS WORK IS UNDER DEVELOPMENT. MATERIALS WILL BE DEVELOPED WITH THE COMMUNITY WITH FEEDBACK FROM WIN MANAGEMENT

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. Can the 2018 EAB report be shared on intranet too? - yes. .

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 Added by CGVP. Much of the paradigms repo is pretty near unusable as so little documentation.

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 TBC and consider more

  • Number of Ambassadors
  • Number of users on mailing lists and number of messages Can we look back at this historically?
  • 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

  • Appreciate the value of open science practices in career development

OS-Survey 2019 slide 4

  • 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

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

OS-Survey 2019 slide 7

Create and share documentation

  • Empower the community to learn together as we explore these topics, and share their knowledge on this repository update when moved 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