What information would you like to view?
Quick start guide
WorkflowHub will help make your workflows findable and citable, and this guide will help you get started with that process.
1. Register yourself on WorkflowHub
Register on the sign up page if you do not have an account. You can also log in using your LS Login or GitHub credentials.
2. Decide which Space
you would like to create a Team
in
Figure 1 below highlights the basic structure of WorkflowHub, and examples of the three types of Spaces
where you could create a Team
. Learn more about Teams
and Spaces
here.
You can request to create a Team
in any or all of the following Spaces
:
- Independent teams: this is where you can create a team if you do not require a specific space
- A pre-existing space, for example:
- A new space: if a pre-existing space is not suitable, you can create a space. This is a good option if you represent a group, consortium, or community where multiple teams might want to register with WorkflowHub
Fig 1. Left - the relationship between the structural elements of WorkflowHub: Spaces, Teams and workflows. Right - examples of where you can create your new team on WorkflowHub.
3. Create a team or join an existing team
Go to the create and join a team page from WorkflowHub to do so. More information on how to join a team can be found on the how to create and join teams and spaces page
Figure 2 shows the minimum information required for a new team, which includes:
- Space - the space you selected or created in step 2 above
- Team name
- Team organization - the organization that should be linked to your team on WorkflowHub (e.g.
University of Melbourne
). If your organization is not yet on WorkflowHub, you can create an organization
Fig 2. Screenshot of required minimum information (numbered) that needs to be entered into the Create a New Team wizard on WorkflowHub.
4. Register workflow(s)
Workflows can be registered using the WorkflowHub wizard. There is an extensive guide to the workflow registration process available in the WorkflowHub documentation.