|
0
|
1 <?xml version="1.0"?>
|
|
|
2 <data_managers>
|
|
|
3 <data_manager tool_file="data_manager/fetch_mlst_data.xml" id="fetch_mlst_data" version="1.0.0"><!-- Defines a single Data Manager Tool that can update one or more Data Tables -->
|
|
|
4 <data_table name="mlst_data"> <!-- Defines a Data Table to be modified. -->
|
|
|
5 <output> <!-- Handle the output of the Data Manager Tool -->
|
|
|
6 <column name="value" />
|
|
|
7 <column name="dbkey" />
|
|
|
8 <column name="name" />
|
|
|
9 <column name="time_stamp" />
|
|
|
10 <column name="file_path" output_ref="out_file" > <!-- The value of this column will be modified based upon data in "out_file". example value "phiX.fa" -->
|
|
|
11 <move type="directory"> <!-- Moving a file from the extra files path of "out_file" -->
|
|
|
12 <target base="${GALAXY_DATA_MANAGER_DATA_PATH}">mlst_data</target>
|
|
|
13 </move>
|
|
|
14 <value_translation>${GALAXY_DATA_MANAGER_DATA_PATH}/mlst_data/${dbkey}/${time_stamp}</value_translation> <!-- Store this value in the final Data Table -->
|
|
|
15 <value_translation type="function">abspath</value_translation>
|
|
|
16 </column>
|
|
|
17 </output>
|
|
|
18 </data_table>
|
|
|
19 <!-- additional data_tables can be configured from a single Data Manager -->
|
|
|
20 </data_manager>
|
|
|
21 </data_managers>
|
