Re: [galaxy-dev] Retain the dbkey specified for an input dataset through a Galaxy workflow?

I’ve submitted an issue about this here: https://github.com/galaxyproject/galaxy/issues/1598 > On Jan 26, 2016, at 8:15 AM, Greg Von Kuster wrote: > > I’ve tracked down how the dbkey is getting lost on tool output datasets that > are part of a collection, but now I’m

Re: [galaxy-dev] Retain the dbkey specified for an input dataset through a Galaxy workflow?

I’ve tracked down how the dbkey is getting lost on tool output datasets that are part of a collection, but now I’m wondering if the tool’s tag is lacking information about the dbkey and this is why it is getting lost. At least the code implies this. John, can you help here? The

Re: [galaxy-dev] Retain the dbkey specified for an input dataset through a Galaxy workflow?

I’ve disovered that this issue is related to tools rather than workflows, and specifically with tools that produce dataset collections on output. In the "job.finish()" method, metadata that includes the input dataset’s dbkey setting is generated correctly for output datasets that are not part