Break
This is a time for you to get some refreshment and clear your mind a little in preparation for the next part of the workshop.
Break
This is a time for you to get some refreshment and clear your mind a little in preparation for the next part of the workshop.
Welcome!
Overview
Teaching: 5 min
Exercises: 5 minObjectives
Understand what we will cover in today’s workshop
Meet other people who are taking part in today’s workshop
Welcome to the WIN Paradigm Sharing workshop!
In today’s workshop, we’re going to introduce you to the GitLab and Pavlovia repositories for sharing your paradigms in WIN. We will then each try to create our own repositories!
The principles of the workshop are as follows:
- No homework for busy people! We want you to have the opportunity to create your first repository as part of the workshop, without needing to put in additional work.
- All abilities welcome! You’re welome to attend whether you’ve never touched git before, or if you’re a git power-user
The schedule of today’s workshop is:
- 10 mins: Welcome and introductions (what we’re doing right now!)
- 15 mins: Why share your tasks? A brief discussion on why task sharing is a good idea, and how to get started at WIN
- 25 mins: Live demo! A walkthrough, from start to finish, of setting up a repository on the WIN Gitlab server
- 40 mins: Make your own repository (part 1) - start to create a simple repository for your task, put a copy of the current version of your task in the repository, and make a simple readme file
- 10 mins: Break
- 15 mins: Live demo! How to add a license to your repository, and make it citable using Zenodo
- 40 mins: Make your own repository (part 2) - finish making your repositories, adding more detail to readme, add license
- 25 mins: Wrap up - everyone briefly says what they’ve made, and we address any final questions
Icebreaker time!
As this is an online workshop, we’d like everyone in the room to say:
- Their name
- Which group/department they’re working in
- What kind of task they’re planning on sharing
- What they wanted to be when they were 11 years old
For further information on WIN Open Science, we recommend visiting the WIN Open Community pages at https://cassgvp.github.io/WIN-Open-Neuroimaging-Community/. You can find specific information about sharing tasks within WIN at https://cassgvp.github.io/WIN-Open-Neuroimaging-Community/docs/tools/tasks.html. And you can always contact Laurence or Dejan with any specific questions you may have.
Key Points
In today’s workshop, we will introduce you to the WIN GitLab and Pavlovia repositories for paradigm sharing at WIN
By the end of today’s workshop, we will aim to have created a repository on WIN GitLab that contains one of our tasks
Template
Why share your tasks?
Overview
Teaching: 15 min
Exercises: 0 minQuestionsObjectives
What benefits might sharing your tasks bring, both to other researchers and to yourself?
What concerns might you have when sharing your tasks, and how could these be addressed?
By the end of this section, you should be familiar with the basic principles of task sharing, and some of the benefits it may bring
You will hopefully be motivated to share your own tasks, and to encourage others to do so as well!
Content placeholder
Content for the “Why share your tasks?” lesson goes here.
Three benefits of sharing your tasks:
- Benefit 1
- Benefit 2
- Benefit 3
Three possible concerns you may have:
- Concern 1
- Concern 2
- Concern 3
Wrap up
Overview
Questions</div>Objectives
What have you produced today?
In this section, we will briefly hear from everyone about the repository that they have produced
Content placeholder: wrap up
Now it’s time to share what we have learnt in today’s workshop!
Make your own repository (part 1)
Overview
Teaching: 0 min
Exercises: 40 minObjectives
By the end of this section, you will have begun to create a repository for your task on GitLab
You will also add a simple readme file to help researchers who haven’t used the task before
Content placeholder: create your own repository
Now it’s time to create your own repositories!
Make your own repository (part 2)
Overview
Teaching: 0 min
Exercises: 40 minObjectives
By the end of this section, you should have completed making your first repository, added a readme file/license, and shared it online
Content placeholder: create your own repository
Now it’s time to create your own repositories (part 2)!
Key Points
The readme file is very important for new researchers who may not be familiar with your experiment
Try sending a link to your repository to another researcher in your group, and seeing if they can get the experiment up and running on their computer without any further input from you
You are encouraged to make the repository “public”, so that other researchers around the world can see your work. However, you can also make the repository “internal” (only visible within WIN) or “private” (only visible to you) if you wish
Demonstration: Add a license to your repository, and make it citable
Overview
Teaching: 15 min
Exercises: 0 minQuestionsObjectives
What kind of license should you choose for your repository? How do you add this?
What should you do if you want to make your repository citable, and have a permanent DOI associated with it?
By the end of this section, you should be ready to add a license to your repository
You should also know how to make it citable, if you wish to do this
Content placeholder: licensing/citation demo
This will contain a demonstration of how to go about sharing your tasks at WIN. We will record a video of this and embed the recording here to make it viewable by people who couldn’t attend the workshop.
Demonstration: using the WIN GitLab server to share your task
Overview
Questions</div>Objectives
What is the WIN GitLab server, and how is it organised?
How do I sign in and create a repository?
By the end of this section, you will be ready to create your own repository on the WIN GitLab server
Content placeholder: task sharing demo
This will contain a demonstration of how to go about sharing your tasks at WIN. We will record a video of this and embed the recording here to make it viewable by people who couldn’t attend the workshop. Make a change here.