Ticket #9 (closed task: fixed)
Feedback from our Galaxy 'users in the loop' on milestone 1: basic Taverna-Galaxy integration
|Reported by:||M.Roos1@…||Owned by:||kostas.karasavvas@…|
|Priority:||major||Milestone:||Crude myExperiment to Galaxy|
|Component:||Script to convert workflow from myExperiment to Galaxy tool||Version:|
This task is to obtain feedback on our first 'crude' components to enable the use of Taverna workflows in Galaxy. These include:
- A script to convert a public workflow on myExperiment into a Galaxy tool.
- A Galaxy menu entry showing a list of workflow tools generated by the script in 1
- A working example using the 'BioAID protein discovery workflow' (text mining)
Is this sufficient for typical users of Galaxy and Galaxy tool developers? Is more needed for input, is more needed for output?
NB the goal is to enable the use of Taverna workflows in Galaxy in a manner that fits typical use of Galaxy, not nicer, not less nice.