Re: [galaxy-dev] Is there a way to pass key =value pairs to the output files in a programmatic way? (Tags? Metadata?)

2011-12-31 Thread Thon deBoer
I digged some more and I guess I could use the rename dataset option in a workflow, but I can't find how I can rename a dataset using the original input name. I tried to use the same notation as those used in the tools (such as ${input.name}) but that just treats the input.name as a user

Re: [galaxy-dev] Is there a way to pass key =value pairs to the output files in a programmatic way? (Tags? Metadata?)

2011-12-31 Thread Peter Cock
On Sat, Dec 31, 2011 at 11:43 PM, Thon deBoer thondeb...@me.com wrote: I digged some more and I guess I could use the rename dataset option in a workflow, but I can't find how I can rename a dataset using the original input name. I tried to use the same notation as those used in the tools

Re: [galaxy-dev] Is there a way to pass key =value pairs to the output files in a programmatic way? (Tags? Metadata?)

2011-12-31 Thread Thon Deboer
Thanks, but ${foo.name} did not work in the workflow to rename an output file. It takes ${foo.name} to be a user provided parameter. ${foo.name} will definitely work in tool definitions, but that means I have to change ALL the default tool names for all the tool in galaxy...Surely there must

Re: [galaxy-dev] Is there a way to pass key =value pairs to the output files in a programmatic way? (Tags? Metadata?)

2011-12-31 Thread Peter Cock
On Sun, Jan 1, 2012 at 12:29 AM, Thon Deboer thondeb...@me.com wrote: Thanks, but ${foo.name} did not work in the workflow to rename an output file. It takes ${foo.name} to be a user provided parameter. ${foo.name} will definitely work in tool definitions, but that means I have to change ALL