It is possible to do things like this using dynamic_options and a code file,
which are somewhat deprecated, but still usable. An example that you might want
to look at could be the GenomeSpace Export tool
(tools/genomespace/genomespace_exporter.*), which queries the GenomeSpace API
to get a list of available folders for export for a specific user. It generates
a drill_down type select parameter, but the same can be done for a standard
Another option would be to have a standalone process that generates a
data_table.loc file and, via e.g. cron, updates this loc file and reloads the
data table at some set interval.
Thanks for using Galaxy,
On Oct 9, 2014, at 4:56 PM, Melissa Cline <cl...@soe.ucsc.edu> wrote:
> Hi Folks,
> I suspect I know the answer to this question already, but I have to ask just
> for the sake of completeness...
> I'm working on a tool for which I'd like to query an external server for the
> set of expected inputs, and then make that set available as input options.
> The tool in question will import a Galaxy dataset into an external cancer
> genomics database. The user will need to specify what cancer cohort the new
> data belongs under. In the perfect world, I would query this cancer genomics
> database for the existing cancer cohorts, and use that set of cohorts to
> populate the set of options for a select-type input parameter.
> Is anything like this possible? If so, where could I look at some examples?
> If not, is there anything you can think of to produce similar behavior?
> Please keep all replies on the list by using "reply all"
> in your mail client. To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
> To search Galaxy mailing lists use the unified search at:
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
To search Galaxy mailing lists use the unified search at: