Re: [galaxy-dev] Why "upload" to Local Instance rather than "import"?

2013-02-07 Thread Jennifer Jackson
Hi Greg, I believe that you do not need to actually copy the data to your workstation (although you could ...) - instead, symbolically link it from the external drive to your workstation so that it appears local. Then upload from that path. The data library upload "by path" option will follow

Re: [galaxy-dev] Why "upload" to Local Instance rather than "import"?

2013-02-04 Thread Dannon Baker
The absolute fastest method would be to enable filepath upload for data libraries (in universe_wsgi.ini -- allow_library_path_paste = True). Once that's set, you can paste the absolute file path into the upload box, and check the box for not copying the data. This will leave the data where it

[galaxy-dev] Why "upload" to Local Instance rather than "import"?

2013-02-04 Thread Thyssen, Gregory - ARS
I have a local instance of Galaxy running on my workstation. I have external hard drives full of fastq sequencing files. I want to make them available to myself as data libraries. I am the Admin and sole user at this point. The "upload" data libraries seems to pass the data through the (slow) net