Hmm... I am not exactly sure the best way to display this data but I
wanted to mention that it is all available via the API (thanks to Kyle
Ellrott). I believe full provenance information (parameters, stdout,
stderr, tool_id, etc...) is available even for permanently deleted
I just added a method of accessing it from bioblend:
And it has been available in blend4j for sometime:
Sorry, I realize this doesn't answer your question, but it is
something worth considering if you are thinking about an external
On Tue, May 20, 2014 at 8:12 AM, Guillaume Penderia
> I am currently working on some user-service functionalities on a local
> version of galaxy (cistrome actually) and I am looking for a way to save
> some job details outside of Galaxy.
> This would allow the users to consult those even after the datasets are
> deleted from Galaxy (in order to free some memory on disks).
> It would be great to get the same presentation as in the job details (with a
> column "input parameter", "value", etc), and I have found out that it has
> something to do with a "show params" function in the Galaxy code, but I
> can't figure out how to use it.
> I would like it to be called in the command line when we use a tool (I'll
> just have to put it in the xml file), is that even possible ?
> Oh and by the way, losing the stderr and stdout links is not a problem as
> long as it doesn't screw the whole file.
> Thank you for your help
> 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: