I would check out the history API documentation - if you find the
history via the API the 'id' attribute is the encoded ID you need.
Using bioblend client:
On Thu, Oct 22, 2015 at 5:37 PM, rbrown Brown <rbrown(a)insilico.us.com> wrote:
Good afternoon John,
Your patch works great for opening Galaxy with a specific History, but one
needs to know the encrypted version of the History ID.
How does one obtain that, or convert the clear text version to an encrypted
----- Forwarded Message -----
From: John Chilton <jmchilton(a)gmail.com>
Sent: Mon, 14 Sep 2015 13:44:01 -0000 (UTC)
Subject: Re: [galaxy-dev] Opening Galaxy with a specified History Name
It looks like you can specify a tool or workflow to jump straight to
but not a history.
The following pull request(https://github.com/galaxyproject/galaxy/pull/725)
extends this functionality to include histories. You will need the encoded
history ID as returned by the workflow and
history API to use this – e.g. on my test laptop the following URL
worked to switch histories after applying the patch in the pull
request – http://localhost:8080/root?history_id=1cd8e2f6b131e892
Hope this helps,
On Thu, Sep 10, 2015 at 6:23 PM, <rbrown1422(a)comcast.net> wrote:
> Good afternoon John,
> We are running a self defined workflow in Galaxy and have a unique history
> for each dataset we are working on. This workflow is run repeatedly to
> tackle an entire dataset, requiring the user the use Galaxy multiple times
> with other steps outside of Galaxy.
> The user enters via a web app, and we would like to bring the user into
> their Galaxy account with the correct history loaded for the dataset they
> are trying to process.
> Is there a way to specify the history when starting Galaxy, not just use
> last one from the previous session?
> ----- Original Message -----
> From: John Chilton <jmchilton(a)gmail.com>
> To: rbrown1422(a)comcast.net
> Cc: galaxy-dev(a)lists.galaxyproject.org
> Sent: Wed, 09 Sep 2015 15:32:39 -0000 (UTC)
> Subject: Re: [galaxy-dev] Opening Galaxy with a specified History Name
> Can you please elaborate on what will be driving this? You can
> certainly create a history and run jobs with the API. It sounds like
> what you want though is an external web application or something that
> will have a link to create a new history for the current users's
> session. I'm not sure this is currently supported since this wouldn't
> involve the API but it can probably be hacked together for your
> On Sat, Sep 5, 2015 at 8:17 PM, <rbrown1422(a)comcast.net> wrote:
>> To all,
>> I would like to open a Galaxy session programmatically (schedule Galaxy
>> their user name and password) and have the Galaxy session open with a
>> history name I specify. So if there was work done previously under that
>> history name, those output files will appear in the history window --
>> without the user having to change the history name manually to see them.
>> Is this possible?
>> 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: