For moving workflows from one instance to another you'll want to click on
"Download or Export" in the workflow context menu and use the "URL for
Importing to Another Galaxy". It looks something like this: (note the
for_direct_import, that's how you'll know you have the right link type).
And, the duplicate headers issue should be resolved on our main server now,
please let us know if you find this isn't the case.
On Mar 14, 2012, at 12:13 PM, Muehlschlegel, Jochen D.,M.D. wrote:
> I would like to download/export my workflows from the Galaxy main to a local
> install at my institution. When I use the URL method, I get the following
> error message:
> Data at
> ' does not appear to be a Galaxy workflow
> Message: No JSON object could be decoded: line 1 column 0 (char 0)
> When I want to download a workflow to my local machine, I get a server error
> (Duplicate headers received from server).
> The local install does not recognize publicly published workflows, so that
> step won't work either.
> Thanks for your help,
> The information in this e-mail is intended only for the person to whom it is
> addressed. If you believe this e-mail was sent to you in error and the e-mail
> contains patient information, please contact the Partners Compliance HelpLine
> http://www.partners.org/complianceline . If the e-mail was sent to you in
> but does not contain patient information, please contact the sender and
> dispose of the e-mail.
> 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: