Passing user_email to a data source
Hello, I'm trying to add a new data source to my Galaxy instance, using synchronous data depositing. The data source needs to know the email address of the user who tries to import data to the Galaxy server. I would have like to write something like that: <inputs action="https://example.com/my/data/source" check_values="false" method="get"> <display>Browse the XX data source $GALAXY_URL</display> <param name="user_email" type="hidden" value="$__user_email__" /> </inputs> Then Galaxy would have generated this url: https://example.com/my/data/source?GALAXY_URL=http....&user_email=test@example.com But this doesn't work, because the $__user_email__ seems to be available only in <command> tag. I end up with this url which is useless: https://example.com/my/data/source?GALAXY_URL=http....&user_email=$__user_email__ Is there any way to do what I need to do? It would be great if variables were available in <param> tags too. Otherwise, maybe I could write a custom tool type to do this. Is there any guideline for this? I have seen someone talking about that a few months ago, but with no answer: http://lists.bx.psu.edu/pipermail/galaxy-dev/2012-September/011258.html Thanks for your help Regards Anthony Bretaudeau
Hi Anthony I doubt it will solve your problem, but just as a general hint: you can use the email address for filtering. In our case, the user gets a different list of groups he/she can select from, eg: <param name="group" type="select" label="Select your group"> <options from_file="access_to_miseq"> <column name="email" index="0"/> <column name="value" index="1"/> <filter type="static_value" name="external_source_filter" value="$__user_email__" column="0"/> </options> </param> and our file '~/tool-data/access_to_miseq' looks like: 123@fmi.ch gbioinfo 123@fmi.ch gfungen 123@fmi.ch gmeier # # abc@fmi.ch gfungen # # 1a2c@fmi.ch gfungen 1a2c@fmi.ch gmeier .... Regards, Hans-Rudolf On 08/20/2013 05:51 PM, Anthony Bretaudeau wrote:
Hello, I'm trying to add a new data source to my Galaxy instance, using synchronous data depositing. The data source needs to know the email address of the user who tries to import data to the Galaxy server. I would have like to write something like that:
<inputs action="https://example.com/my/data/source" check_values="false" method="get"> <display>Browse the XX data source $GALAXY_URL</display> <param name="user_email" type="hidden" value="$__user_email__" /> </inputs>
Then Galaxy would have generated this url: https://example.com/my/data/source?GALAXY_URL=http....&user_email=test@example.com
But this doesn't work, because the $__user_email__ seems to be available only in <command> tag. I end up with this url which is useless:
https://example.com/my/data/source?GALAXY_URL=http....&user_email=$__user_email__
Is there any way to do what I need to do? It would be great if variables were available in <param> tags too. Otherwise, maybe I could write a custom tool type to do this. Is there any guideline for this?
I have seen someone talking about that a few months ago, but with no answer: http://lists.bx.psu.edu/pipermail/galaxy-dev/2012-September/011258.html
Thanks for your help Regards Anthony Bretaudeau ___________________________________________________________ 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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Hi, I didn't know this was possible, thanks! Unfortunately I can't use this in my case because I can only use param with type="hidden" for a data source... Anthony On 21/08/2013 08:51, Hans-Rudolf Hotz wrote:
Hi Anthony
I doubt it will solve your problem, but just as a general hint: you can use the email address for filtering. In our case, the user gets a different list of groups he/she can select from, eg:
<param name="group" type="select" label="Select your group"> <options from_file="access_to_miseq"> <column name="email" index="0"/> <column name="value" index="1"/> <filter type="static_value" name="external_source_filter" value="$__user_email__" column="0"/> </options> </param>
and our file '~/tool-data/access_to_miseq' looks like:
123@fmi.ch gbioinfo 123@fmi.ch gfungen 123@fmi.ch gmeier # # abc@fmi.ch gfungen # # 1a2c@fmi.ch gfungen 1a2c@fmi.ch gmeier ....
Regards, Hans-Rudolf
On 08/20/2013 05:51 PM, Anthony Bretaudeau wrote:
Hello, I'm trying to add a new data source to my Galaxy instance, using synchronous data depositing. The data source needs to know the email address of the user who tries to import data to the Galaxy server. I would have like to write something like that:
<inputs action="https://example.com/my/data/source" check_values="false" method="get"> <display>Browse the XX data source $GALAXY_URL</display> <param name="user_email" type="hidden" value="$__user_email__" /> </inputs>
Then Galaxy would have generated this url: https://example.com/my/data/source?GALAXY_URL=http....&user_email=test@example.com
But this doesn't work, because the $__user_email__ seems to be available only in <command> tag. I end up with this url which is useless:
https://example.com/my/data/source?GALAXY_URL=http....&user_email=$__user_email__
Is there any way to do what I need to do? It would be great if variables were available in <param> tags too. Otherwise, maybe I could write a custom tool type to do this. Is there any guideline for this?
I have seen someone talking about that a few months ago, but with no answer: http://lists.bx.psu.edu/pipermail/galaxy-dev/2012-September/011258.html
Thanks for your help Regards Anthony Bretaudeau ___________________________________________________________ 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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Hi, I have written a patch for this. The pull request is there : https://bitbucket.org/galaxy/galaxy-central/pull-request/206/give-access-to-... It works fine on my galaxy instance. Cheers Anthony On 21/08/2013 08:51, Hans-Rudolf Hotz wrote:
Hi Anthony
I doubt it will solve your problem, but just as a general hint: you can use the email address for filtering. In our case, the user gets a different list of groups he/she can select from, eg:
<param name="group" type="select" label="Select your group"> <options from_file="access_to_miseq"> <column name="email" index="0"/> <column name="value" index="1"/> <filter type="static_value" name="external_source_filter" value="$__user_email__" column="0"/> </options> </param>
and our file '~/tool-data/access_to_miseq' looks like:
123@fmi.ch gbioinfo 123@fmi.ch gfungen 123@fmi.ch gmeier # # abc@fmi.ch gfungen # # 1a2c@fmi.ch gfungen 1a2c@fmi.ch gmeier ....
Regards, Hans-Rudolf
On 08/20/2013 05:51 PM, Anthony Bretaudeau wrote:
Hello, I'm trying to add a new data source to my Galaxy instance, using synchronous data depositing. The data source needs to know the email address of the user who tries to import data to the Galaxy server. I would have like to write something like that:
<inputs action="https://example.com/my/data/source" check_values="false" method="get"> <display>Browse the XX data source $GALAXY_URL</display> <param name="user_email" type="hidden" value="$__user_email__" /> </inputs>
Then Galaxy would have generated this url: https://example.com/my/data/source?GALAXY_URL=http....&user_email=test@example.com
But this doesn't work, because the $__user_email__ seems to be available only in <command> tag. I end up with this url which is useless:
https://example.com/my/data/source?GALAXY_URL=http....&user_email=$__user_email__
Is there any way to do what I need to do? It would be great if variables were available in <param> tags too. Otherwise, maybe I could write a custom tool type to do this. Is there any guideline for this?
I have seen someone talking about that a few months ago, but with no answer: http://lists.bx.psu.edu/pipermail/galaxy-dev/2012-September/011258.html
Thanks for your help Regards Anthony Bretaudeau ___________________________________________________________ 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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
participants (2)
-
Anthony Bretaudeau
-
Hans-Rudolf Hotz