You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful to be able to store dataset collections in data libraries. Currently, importing a dataset collection from a history to a data library will flatten the collection.
I have many workflows that expect dataset collections as inputs (in addition to samples being analyzed). These collection inputs for the workflow are typically static (i.e., the collection elements do not change for a particular workflow version), so importing the workflow inputs from the data library to a history for running the workflow would be streamlined if the collection inputs could be stored in the data library as a collection. Currently, users have to build the collection from the elements stored separately in the data library for each workflow run.
The text was updated successfully, but these errors were encountered:
I personally (this is not the view of the team!) don’t think we should do this, unless the implementation is trivially easy and clean. I’d rather like libraries to act as a cache system, and use workflow default files for the usecase you're describing. I think that would result in more portable and better described workflows.
I'd also say that you could use the apply rules tool to build up the inputs from a flat collection as part of your workflow today.
It would be very useful to be able to store dataset collections in data libraries. Currently, importing a dataset collection from a history to a data library will flatten the collection.
I have many workflows that expect dataset collections as inputs (in addition to samples being analyzed). These collection inputs for the workflow are typically static (i.e., the collection elements do not change for a particular workflow version), so importing the workflow inputs from the data library to a history for running the workflow would be streamlined if the collection inputs could be stored in the data library as a collection. Currently, users have to build the collection from the elements stored separately in the data library for each workflow run.
The text was updated successfully, but these errors were encountered: