blend4j and bioblend for the most part consumes "encoded ids" not
UUIDs. The gist from yesterday demonstrates how to generate this
encoded id from inside of Galaxy/Cheetah -
https://gist.github.com/jmchilton/27c5bb05e155a611294d.

UUIDs are newer (in Galaxy terms) than encoded ids and only a few
endpoints (mostly related to workflows) currently are capable of
consuming them. Lots of objects in Galaxy's models do not have UUIDS
include both histories and hdas (the thing which output is).

Hope this helps.

-John

On Wed, May 6, 2015 at 3:14 PM, Ben Bimber <bbimber@gmail.com> wrote:
> Hello,
>
> I am working with blend4j and bioblend to interact with galaxy.  In general,
> the API seems to require the UUID of a dataset/history, etc.  I may be
> missing something obvious, but I am not finding great ways to obtain this
> from cheetah substitutions.  For example, I can use ${history.id} or
> ${output.id} to get the integer ID of that dataset/history.  ${output.uuid}
> is not recognized.
>
> I am looking here as a reference:
>
> https://github.com/galaxyproject/galaxy/blob/e73d90c94edc63d181c30bd1942918a960d3fac9/lib/galaxy/tools/wrappers.py
> https://github.com/galaxyproject/galaxy/blob/dev/lib/galaxy/model/__init__.py
>
> and would have expected UUID to get exposed in some manner.  Is there a
> standard way to obtain the UUID?
>
> Thanks,
> Ben
>

> ___________________________________________________________
> 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:
>   https://lists.galaxyproject.org/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/