galaxyproject / galaxyproject/training-material

Update Workflow FAIRification tutorial

Open
#6,197 1 comment 0 reactions 0 assignees View on GitHub
galaxy-interface
Dominant language
HTML
Stars
367
Forks
1.1k
Avg merge
16h 27m
Merged PRs (30d)
49

Description

Idea to improve [Annotate, prepare tests and publish Galaxy workflows in workflow registries](https://training.galaxyproject.org/training-material/topics/galaxy-interface/tutorials/workflow-fairification/tutorial.html) tutorial :

- **Mention that test data can be deposited elsewhere than Zenodo:** The tutorial currently focuses on Zenodo for test data sharing, but it would be helpful to mention (e.g. as a comment or tip) that other repositories such as Figshare or institutional platforms are also acceptable.
- **Remove reference to mapping workflow:** The tutorial refers to a mapping workflow that is no longer used. This reference can be removed to avoid confusion.
- **Add alternative workflow publication paths (for non-IWC users):** Currently, the tutorial guides users through publishing via IWC, which then syncs automatically with WorkflowHub and Dockstore. However, for users less comfortable with Git and command-line tools, it could be useful to mention that workflows can also be submitted directly to [WorkflowHub](https://workflowhub.eu/) or [Dockstore](https://dockstore.org/) manually.
→ Suggest adding a [Choose Your Own Tutorial](https://training.galaxyproject.org/training-material/news/2022/04/12/cyot.html#new-tutorial-feature-choose-your-own-tutorial) section to offer both options (automated via IWC and manual upload).

Thanks for considering! 😊

Contributor guide

Open the contributing guide

Research direction

Start with the linked Workflow FAIRification tutorial and review its current sections on Zenodo, the mapping workflow, and IWC publication. Update the tutorial to mention alternative test-data repositories, remove the obsolete mapping-workflow reference, and explain both automated IWC and manual WorkflowHub or Dockstore publication paths. Done means the tutorial presents both options without the outdated reference.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.