galaxyproject / galaxy

Data intensive science for everyone.
https://galaxyproject.org
Other
1.38k stars 996 forks source link

[Feature request] Add tags to histories and/or invocations when invoking workflow #17562

Open simonbray opened 7 months ago

simonbray commented 7 months ago

Not sure how used this feature is, so perhaps this is niche, but I'm currently launching workflows with multiple datasets selected under an input in order to create multiple workflow invocations at once, which is very handy.

To keep things tidy, I'm using the Send results to new history option to run each invocation in a separate history. It would be nice to be able to add a tag to all the created histories or invocations, to be able to easily track which belong together.

(Comparable to #8710 / #13885 I guess, but for workflows rather than tools.)

mvdbeek commented 7 months ago

This is a duplicate of https://github.com/galaxyproject/galaxy/issues/17103, which I think we shouldn't do

simonbray commented 7 months ago

It is not the same as #17103, which suggests tagging output datasets of a single invocation. I would like to be able to tag the multiple histories and invocations created by a single "launch" (not invocation, but not sure what word is appropriate) of a workflow in the UI, so they are linked together. If they can be linked in another way that doesn't involve tags that would be great as well.

simonbray commented 7 months ago

It is not the same as #17103, which suggests tagging output datasets of a single invocation. I would like to be able to tag the multiple histories and invocations created by a single "launch" (not invocation, but not sure what word is appropriate) of a workflow in the UI, so they are linked together. If they can be linked in another way that doesn't involve tags that would be great as well.

Can this be reopened please?

mvdbeek commented 7 months ago

https://github.com/galaxyproject/galaxy/issues/17103#issuecomment-1832455145 applies though, can we close this ?

simonbray commented 7 months ago

I agree with John's comment, and being able to filter histories by invocation id will be useful (thanks for implementing it!) but I don't think it's related to what I am describing here.