[TAV-559] Referenced nested workflow support should be more consistent/easier to use Created: 2007-07-30  Updated: 2008-04-17  Resolved: 2008-04-17

Status: Closed
Project: myGrid
Component/s: Taverna GUI
Affects Version/s: 1.5, 1.5.1, 1.5.1.1, 1.5.1.2, 1.5.1.3, 1.5.1.4, 1.5.1.5, 1.5.1.6, 1.5.2, 1.5.2.1
Fix Version/s: 1.7.1

Type: Improvement Priority: Minor
Reporter: Stian Soiland-Reyes Assignee: Stuart Owen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
has dependent TAV-574 Nested workflow location Closed

 Description   

Currently we secretly supports referenced nested workflow. Such a nested workflow is saved in the scufl as:

<s:processor name="get_orthologs">
        <s:workflow>

    <s:xscufllocation>file:/G:/toolkit/get_ko_pathways_3.xml</s:xscufllocation>
        </s:workflow>
</s:processor>

However, as pointed out by Paul Fisher to taverna-users on 2007-07-30, this means that if G: was your USB flash-drive at home, it might be at F: at work. If you are using it in a Linux or Mac OS X computer it would work even less.

In general our GUI doesn't show that a nested workflow is referenced, and doesn't give the user any control over when it is referenced or not.

Referenced workflows are generally very useful, as reported (offline) by Marco Roos, for utillity workflows/shims that can be built and maintained separately. Within their personal library of workflows they would generally like to use the latest version of that nested workflow, ie. the one stored behind the reference.

Currently if you start editing a nested workflow Taverna will make a copy of it and break the reference. This might or might not be what the user wants.

This Improvement request seeks a general clean-up of how Taverna handles referenced nested workflows and to improve the GUI to make referenced nested workflows more obvious and usable.

Most of Taverna's users probably don't even know that referenced nested workflows are possible, and keeping it secret is like not telling a fresh programmer about functions.



 Comments   
Comment by Stuart Owen [ 2008-04-17 ]

This was fixed for the 1.7.1 release by TAV-574

Generated at Wed Oct 28 05:18:32 GMT 2020 using JIRA 6.1.2#6157-sha1:98c729218aad6de1537eb8e98889ee5562c90d96.