Open neoformit opened 1 year ago
I remember discussing ideas along these lines during the hackathon of probably GCC2016, it would be really nice to have!
Finally, this UI layout might be implemented as a "View" that the user can toggle on/off (or select from multiple). The conventional dataset view may still be preferred in some situations.
This would be key, especially to not disrupt existing user expectations.
I completely agree, this to me seems like a very good and simple enhancement, and was always my first alternative Proposition to a graph view for histories.
Not a replacement for this idea (which I love) but related is https://github.com/galaxyproject/galaxy/pull/15237 / https://github.com/galaxyproject/galaxy/pull/13893 - I wanted to generalize the jobs grids so they have parity with invocations and we can put a list of jobs in the user menu. If we had a handle on jobs in the UI we could do some really great filtering and such outside the context of histories - the way we do with invocations. Using both jobs and invocations to tame large histories is also a great idea though - and like @mvdbeek I always bring this up as my alternative to graph view.
After receiving feedback from a number of Galaxy users (and through my own use) I wonder if there could be a more intuitive layout for the history UI. I have spend some time fleshing out this concept (as requested by @bgruening) but there may be areas of the UI where I haven't considered the implications of this layout - feedback please :)
I think something like this could lead to a much more intuitive, cleaner experience for the history.
Current implementation:
Proposed implementation:
job xyz > dataset 1
Run
button)Screenshots/wireframes:
Current implementation
First, an example to demonstrate where the current history layout gets real confusing. Here is a history where I repeated a job on the same dataset with different parameters. It's not clear where one job's outputs end and the next one starts:
Now, a second example I manufactured as a use-case. A user has uploaded 6 raw read files, cleaned them with Trimmomatic and then assembled with Trinity. For comparison, they have also assembled the raw reads. With the current implementation the result is a history spanning multiple pages. To confirm what the final Trinity jobs entail, we have to manually cross-reference
data 1
anddata 7
.Proposed implementation
A similar history to the above, but with the proposed "jobs-view" (blue traces follow a click). With a glance at this history, the logic of the analysis is immediately clear:
Viewing job/dataset information:
Selecting a dataset and naming a job in the tool form: