Stop making _sets by default
Currently, every time you launch a workflow on more than one row of a table, it creates a new entry in the corresponding _set table. There's no option to turn this behavior off. 99% of the time, this is unwanted behavior and it makes the _set table relatively meanignless/useless as it is filled with the clutter of all the previous submissions (is it attempting to duplicate the Job History tab?).
There are times that making _set members is super useful, but not if the table is growing out of control with noise.
Example screenshot of current behavior:
Proposal (minimal change): in the row selection modal above, do not have the bottom part "Selected samples will be saved as a new sample_set named" appear unless explicitly asked to with some sort of checkbox or toggle.
Proposal (even better): these mechanisms for creating sets should be entirely divorced/orthogonal to submitting workflows. Create a UI for making sets out of individual rows. Have it have nothing to do with workflow submission.
Comments
1 comment
Hi Danny,
I believe this behavior exists to easily reference the same set of data in future workflow submissions, but I agree it would be nice to have it be optional.
You can create a set out of individual data table rows already on the Data tab:
This will create a new row in the associated set table (or create the table if it does not already exist).
Please sign in to leave a comment.