Data transfer between two galaxy instances
Hi, We are running two instances of galaxy on our site--one internal, the other external. Some of our internal users have data on the external instance. What might be the easiest way to transfer the data of our internal users from the external to the internal instance? OR Is there a way to transfer data between galaxy instances? I thought that I'd give this mailing list a shot before telling our internal users that they would have to re-load the data on the internal instance. Thanks, Len Taing
Hi Have you tried the 'Export to File' followed by 'Import from File' for individual histories? This worked for us very well, at least for small histories with small data files associated with them a few months ago. Regards, Hans On 09/23/2011 09:26 PM, lentaing@jimmy.harvard.edu wrote:
Hi,
We are running two instances of galaxy on our site--one internal, the other external. Some of our internal users have data on the external instance. What might be the easiest way to transfer the data of our internal users from the external to the internal instance? OR Is there a way to transfer data between galaxy instances? I thought that I'd give this mailing list a shot before telling our internal users that they would have to re-load the data on the internal instance.
Thanks, Len Taing
___________________________________________________________ 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:
Hi Hans (and all), Thank you for the recommendation. I wasn't even aware of this feature--it is exactly what our site needs. But I have yet been able to successfully transfer a history this way. I've tried various permutations of importing/exporting to/from our site and galaxy (http://main.g2.bx.psu.edu/), but everytime I click submit on the "Import from File" page, nothing seems to happen. My history is a small test-set containing two trivial files so it should transfer over immediately. Sometimes when I click on the Export to file button, my browser downloads a tar-ball. But I can't submit this tarball on the "import from file" page because it expects a URL. I was wondering if there are other devs out there who might be able to replicate my "bug". It would help me to determine if it is something specific to our deployment, or whether this might be a galaxy bug. If you've been able to get Export to/Import from file to work for your site *recently* I'd love to talk to you! Thanks, Len For those who are interested, the link generated for my http://cistrome.org/ap/history/export_archive?id=e529b88352bf9863
Hi
Have you tried the 'Export to File' followed by 'Import from File' for individual histories? This worked for us very well, at least for small histories with small data files associated with them a few months ago.
Regards, Hans
On 09/23/2011 09:26 PM, lentaing@jimmy.harvard.edu wrote:
Hi,
We are running two instances of galaxy on our site--one internal, the other external. Some of our internal users have data on the external instance. What might be the easiest way to transfer the data of our internal users from the external to the internal instance? OR Is there a way to transfer data between galaxy instances? I thought that I'd give this mailing list a shot before telling our internal users that they would have to re-load the data on the internal instance.
Thanks, Len Taing
___________________________________________________________ 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:
Len, This a beta feature with multiple usability issues. That said, it should work; here's how: Galaxy provides a URL when you export a history; take note of this URL as this is the one that you'll when importing the link. If Galaxy doesn't provide a link, update the history somehow (e.g. change its name slightly) and Galaxy will provide the URL again. Another catch: you'll need to make the history 'accessible via link' for the URL to work. You can do this via Options --> Share or Publish menu. Good luck, J. On Sep 27, 2011, at 6:07 PM, <lentaing@jimmy.harvard.edu> <lentaing@jimmy.harvard.edu> wrote:
Hi Hans (and all),
Thank you for the recommendation. I wasn't even aware of this feature--it is exactly what our site needs.
But I have yet been able to successfully transfer a history this way. I've tried various permutations of importing/exporting to/from our site and galaxy (http://main.g2.bx.psu.edu/), but everytime I click submit on the "Import from File" page, nothing seems to happen. My history is a small test-set containing two trivial files so it should transfer over immediately. Sometimes when I click on the Export to file button, my browser downloads a tar-ball. But I can't submit this tarball on the "import from file" page because it expects a URL.
I was wondering if there are other devs out there who might be able to replicate my "bug". It would help me to determine if it is something specific to our deployment, or whether this might be a galaxy bug. If you've been able to get Export to/Import from file to work for your site *recently* I'd love to talk to you!
Thanks,
Len
For those who are interested, the link generated for my http://cistrome.org/ap/history/export_archive?id=e529b88352bf9863
Hi
Have you tried the 'Export to File' followed by 'Import from File' for individual histories? This worked for us very well, at least for small histories with small data files associated with them a few months ago.
Regards, Hans
On 09/23/2011 09:26 PM, lentaing@jimmy.harvard.edu wrote:
Hi,
We are running two instances of galaxy on our site--one internal, the other external. Some of our internal users have data on the external instance. What might be the easiest way to transfer the data of our internal users from the external to the internal instance? OR Is there a way to transfer data between galaxy instances? I thought that I'd give this mailing list a shot before telling our internal users that they would have to re-load the data on the internal instance.
Thanks, Len Taing
___________________________________________________________ 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:
participants (3)
-
Hans-Rudolf Hotz
-
Jeremy Goecks
-
lentaing@jimmy.harvard.edu