Mercurial > repos > trinity_ctat > ctat_genome_resource_lib_data_manager4
comparison data_manager_conf.xml @ 0:6a478189780c draft default tip
Uploaded
| author | trinity_ctat |
|---|---|
| date | Thu, 25 Oct 2018 16:50:45 -0400 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| -1:000000000000 | 0:6a478189780c |
|---|---|
| 1 <?xml version="1.0"?> | |
| 2 <data_managers> | |
| 3 <data_manager tool_file="data_manager/add_ctat_resource_lib.xml" id="ctat_genome_resource_libs_data_manager"> | |
| 4 <data_table name="ctat_genome_resource_libs"> | |
| 5 <output> | |
| 6 <column name="value" /> | |
| 7 <!-- value is used to uniquely identify this entry in the table. | |
| 8 --> | |
| 9 <column name="name" /> | |
| 10 <!-- name is used as the selector in the pull down lists for items in this table. | |
| 11 --> | |
| 12 <column name="path" /> | |
| 13 <!-- path is the absolute path of the top level directory of the CTAT Genome Resource Library. | |
| 14 --> | |
| 15 <!-- <column name="path" output_ref="out_file"> --> | |
| 16 <!-- It is typical to move the data file, but because our tool gets the destination | |
| 17 location from the user, we do not want to move the data from that location. | |
| 18 The full path of the CTAT Resource library is returned in location. | |
| 19 So no need to change the value either. | |
| 20 The files are so big we do not want to be making copies of them. | |
| 21 They are created where we want them. | |
| 22 --> | |
| 23 <!-- <move type="file" relativize_symlinks="False"> --> | |
| 24 <!--<source>${path}</source> --> | |
| 25 <!--<target base="${GALAXY_DATA_MANAGER_DATA_PATH}">ctat_genome_lib_build_dir</target> --> | |
| 26 <!--</move> --> | |
| 27 <!-- | |
| 28 <value_translation>${GALAXY_DATA_MANAGER_DATA_PATH}/ctat_genome_lib_build_dir | |
| 29 </value_translation> | |
| 30 --> | |
| 31 <!-- The location returned by the tool should already be an absolute path. | |
| 32 <value_translation type="function">abspath</value_translation> | |
| 33 --> | |
| 34 <!--</column> --> | |
| 35 </output> | |
| 36 </data_table> | |
| 37 </data_manager> | |
| 38 </data_managers> |
