Created as part of the EOSC-Life WP2 Tools Collaboratory, WorkflowHub is under development.
See a complete list on the acknowledgement page.
Aims of the project include:
- Evolvement of myExperiment that is workflow system agnostic, supports a repository of workflows in native and standardised form (e.g. CWL and the virtual aggregation of established tool, workflow and registries to support discovery over a fragmented ecosystem. The federated registry would support a common API to simplify access for tool developers.
- Standardised workflow identifiers and metadata descriptions needed for workflow discovery, reuse, preservation, interoperability and monitoring and metadata harvesting using standard protocols. Workflows are usually multi-component (requiring links to test data, example runs, explanatory documentation, etc) and used in collections for scientific use cases. We plan to use the Research Object specification for packaging workflows, which has already been combined with CWL and is part of the BioComputeObject specification.
- Workflow snapshot preservation, publishing, citation and monitoring, credit claiming and workflows part of the scholarly communication landscape partnering with platforms like DataCite and EOSC’s OpenAIRE and their Research Community Dashboards linking publications with workflows, associated datasets, software, etc.
- The workflow registry is planned to be based on the SEEK platform using Common Workflow Language and Research Objects to glue in federated workflow and tool descriptions across the research infrastructures.
The WorkflowHub has a sustainability plan that ensures the availability of its contributions and metadata up to and beyond 2026. If and when it reaches its end of service then the published contributions and metadata will be archived as RO-Crates and made available through a public repository, such as Zenodo, Figshare or another appropriate resource at that time.