John, the prefixes like "22|" are added to the inputs associated with each
step, so that they can be separated back out. In this case, the chunk of HTML
you have pasted likely corresponds to the 22nd step of the workflow.
53 on the other hand should be a dataset id from the current history (unencoded
in this case).
On Aug 9, 2011, at 8:24 PM, Duddy, John wrote:
> I’d like to integrate with Galaxy and launch workflows, and I am hoping to
> reuse Galaxy’s support for prompting the user for items that are tagged as
> being set at runtime. It looks to me that I could load the workflows/run page
> in a frame on my app (on the same server) and reuse it.
> The problem I’m having is that I don’t understand how the parameters for the
> input files are encoded. For example, here is one for adding a column to a
> <select name="22|input" last_selected_value="53">
> <option value="53" selected>1: Add column on data 6</option>
> <input type="hidden" name="22|__force_update__input" value="true" />
> <div style="clear: both"></div>
> What are 22 and 53? They don’t seem to correspond to dataset IDs.
> Is there a way that I can encode data library IDs such that I can submit this
> form and have Galaxy run the workflow with the right files in a new history?
> John Duddy
> Sr. Staff Software Engineer
> Illumina, Inc.
> 9885 Towne Centre Drive
> San Diego, CA 92121
> Tel: 858-736-3584
> E-mail: jdu...@illumina.com
> 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:
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: