Files
galaxy/test/functional/tools/identifier_single.xml
T
John Chilton 2f15eb0d78 Expose improved sample tracking to tools for implicit map/reduce ops.
Tools may now use $input.element_identifier during tool evalution for input 'data' parameters with the following semantics:

 - If the input was specified as a single dataset by the user - this just fallbacks to providing the $input.name.
 - If the input was mapped over a collection (to produce many jobs) or if the input is a 'multiple="true"' input that was provided a collection - the $input.element_identifier will be the element identifier for the corresponding collection item (generally much more useful the dataset name - since if preserved throughout workflows).

'data_collection' parameters already can access this kind of information - but it is something of a best practice to use simple 'data' parameters since they are compatible with more traditional un-collected datasets.

This commit really needs more comments - but Philip Mabon has been patiently waiting for this functionality for a long time.
2015-02-02 16:29:42 -05:00

14 lines
330 B
XML

<tool id="identifier_single" name="identifier_single">
<command>
echo '$input1.element_identifier' > 'output1'
</command>
<inputs>
<param type="data" name="input1" label="Input 1" />
</inputs>
<outputs>
<data name="output1" type="tabular" from_work_dir="output1" />
</outputs>
<tests>
</tests>
</tool>