Feature #14168

[Running a workflow] Input presets

Added by Moritz Gilsdorf about 3 years ago. Updated 3 months ago.

Assigned To:
Target version:
Start date:
Due date:
% Done:


Estimated time:
Story points:


User Story
As a Scientist
I can use stored presets for workflows from the “Run a Pipeline” page
so that I can switch easily between common resource bundles (e.g. different genome assemblies and depending annotations)

This should be part of the input selection. Basically the idea is that a part of the input fields can populated by selecting a preset from a e.g. dropdown menu. It needs to be clarified how these presets could be stored in the backend.

Example: We have a RNAseq pipeline that requires, apart from the NGS reads as input, a bundle of other input data like an index and annotation data (call this resource bundle). We want to provide different bundles for different assemblies and species so that we don't have to register the same workflow several times for each preset.


#1 Updated by Moritz Gilsdorf about 3 years ago

  • Description updated (diff)

#2 Updated by Chrystian Klingenberg about 3 years ago

  • Target version set to sprint 9

#3 Updated by Chrystian Klingenberg about 3 years ago

  • Target version deleted (sprint 9)

#4 Updated by Tom Morris almost 3 years ago

  • Project changed from Arvados Workbench 2 to Arvados
  • Target version set to To Be Groomed

This came from the Workbench 2 project, but is tightly involved with CWL, so we should discuss what's needed to support it.

#5 Updated by Peter Amstutz almost 3 years ago

This has come up in the CWL community chats. SBG has a very similar use case for their platform and wants a way to describe "suggested" inputs for a workflow (which is slightly different from defaults).

#6 Updated by Peter Amstutz 3 months ago

  • Target version deleted (To Be Groomed)

Also available in: Atom PDF