"Published Workflows" missing from "All Workflows"
Hello all, This is to report a usability bug with workflows - specifically the curiously separate handling of "Published Workflows" in the user interface. 1. Log into your Galaxy account, 2. On the top ribbon, click on "Shared Data", "Published Workflows", and make a note of the entries. 3. Return to the main screen via the top ribbon entry "Analyse Data" 4. On the bottom of the left hand tool column, under "Workflows" click on "All workflows". Observe results. 5. On the top ribbon, click on "Workflows". Observe results. Actual result (in 4 and 5): Two sections, "Your workflows" and "Workflows shared with you by others" Expected result (in 4 and 5): Three sections, "Your workflows", "Workflows shared with you by others", "Published Workflows". i.e. "Published Workflows" are hidden or separated away from the others. This appears to be a design choice (like shared datasets they must be "imported" before use), but if so this could be clarified as follows: Suggested result (in 4 and 5): Two sections, "Your workflows" and "Workflows shared with you by others", plus a footnote (with link) saying something about additional workflows are available to import from "Published Workflows". Regards, Peter
i.e. "Published Workflows" are hidden or separated away from the others. This appears to be a design choice (like shared datasets they must be "imported" before use), but if so this could be clarified as follows:
This was a very old design choice that will be revisited in the (hopefully near) future. I see no reason that published workflows need to be imported before use. J.
On Mon, May 6, 2013 at 7:08 PM, Jeremy Goecks <jeremy.goecks@emory.edu> wrote:
i.e. "Published Workflows" are hidden or separated away from the others. This appears to be a design choice (like shared datasets they must be "imported" before use), but if so this could be clarified as follows:
This was a very old design choice that will be revisited in the (hopefully near) future. I see no reason that published workflows need to be imported before use.
That sounds good :) Peter
participants (2)
-
Jeremy Goecks
-
Peter Cock