(Once more with the list cc'ed - sorry for the duplicate message.)
The IDs are encoded before they are shared out via the API so that raw
integers aren't exposed. The ID the API returns is generally the value
in the id column for that table.
Eric Rasche kindly contributed a script to the development version of
Galaxy that converts IDs
python scripts/secret_decoder_ring.py decode <id_from_bioblend>
You can probably add the script to older versions of Galaxy and it
I hope this helps and thanks for hacking on Galaxy!
On Wed, May 3, 2017 at 11:05 PM, Aarthi Mohan <epha...@nus.edu.sg> wrote:
> Hello all,
> I have a local instance of galaxy version 15.03.1 (this is needed by IRIDA
> I have retrieved datasets associated with a history using Bioblend.
> I want to confirm, if the history id used in get_histories(hid) or
> show_history(hid) is stored in the database? I have tried searching the
> entire database by mysqldump, and couldn’t find such values in it.
> Where else is this id stored and will this be deleted periodically?
> Appreciate your help!
> Important: This email is confidential and may be privileged. If you are not
> the intended recipient, please delete it and notify us immediately; you
> should not copy or use it for any purpose, nor disclose its contents to any
> other person. Thank you.
> 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: