I'd like to do the same thing that Tanguy described. I'm trying to figure out the syntax to this within the workflow editor, but can't quite get it right. In your example Dannon, would you just set ${dataset_name} as the "Name" for your "Input dataset" to capture the input dataset name as a variable? When I do that and then try to run the workflow I get the following error:
Tanguy,
My apologies for the delay in response. For now, the best way to do something like this would be to add rename dataset actions to each step where you want to modify the dataset name. You can do this within the workflow editor, in the right panel under "Edit Step Actions".
A new feature we've been working on will allow you to use variables within the rename action, among other places. Depending on how often you reuse workflows, it could save you a lot of time renaming things. An example would look something like this, for a rename dataset action: "Filtering ${dataset_name} on col2 > ${threshold}", where ${dataset_name} and ${threshold} are variables that are set when you run a workflow. These variables get replaced anywhere they are seen in the workflow tool parameters and step actions. This feature is not available yet, but we do expect it to be ready soon.
Thanks for using Galaxy,
Dannon
On Oct 28, 2010, at 4:40 AM, Tanguy Le Carrour wrote:
> Dear Galaxy Team,
>
> I started using Galaxy few months ago. I'm now setting up my first "real" workflows.
> I would like to keep the name of my input file through the various steps as dataset's label, maybe also modify it a bit, and finally give a "proper" name to the result file downloaded.
>
> A simple example:
> 1) date-sample_name.gff3 --[step1]-> date-sample_name-step1.tsv
> 2) date-sample_name-step1.tsv --[step2]-> date-sample_name-step1-step2.txt
> 3 download date-sample_name-step1-step2.txt
>
> I've seen that I can use the 'label' attribute in the tool config "data" tag to do so. But I don't know how to access the ${input.label} (?) and how to modify it.
>
> I doesn't stop me using my workflows, but it would definitely help my users not to get lost when they use them.
>
> Best regards,
> Tanguy Le Carrour
>
> --
> Tanguy LE CARROUR
>
> Functional Genomics Center Zurich
> ETH Zurich / University of Zurich
> Winterthurerstrasse 190
> 8057 Zurich
> Switzerland
>
>
>
> _______________________________________________
> galaxy-dev mailing list
> galaxy-dev@lists.bx.psu.edu
> http://lists.bx.psu.edu/listinfo/galaxy-dev
_______________________________________________
galaxy-dev mailing list
galaxy-dev@lists.bx.psu.edu
http://lists.bx.psu.edu/listinfo/galaxy-dev