On Wed, Jul 23, 2014 at 10:47 AM, Ulf Schaefer <ulf.schae...@phe.gov.uk> wrote: > Dear all > > I have several smallish BLAST databases that I would like to provide in > a data library. I create them in a history with the makeblastdb tool and > them try to add them to the library. I see that for each blast db there > is an empty file created (like /path/dataset_12345.dat) and a folder > with the same name (/path/dataset_12345_files/) that contains the actual > db files (blastdb.n*). > > In my library the blastdb shows up empty and I cannot import it back to > another history. I does not seem to be aware of the _files folder, > despite it being the right data type (blastdbn). > > Any ideas what I am doing wrong? > > Thanks a lot for your help > Ulf
Hi Ulf, I've never tried that. It could be a bug in Galaxy importing composite datatypes into a library, or something in the BLAST database definition which needs fixing. Does importing an HTML report (with child files like images) into a library work for you? (This is another composite datatype so a useful comparison). Rather than using Data Libraries, we just list all the locally installed shared BLAST databases via the BLAST *.loc files instead. Note using the *.loc files makes the databases available to all the Galaxy users, while with a Data Library you can control access to specific groups/roles. Regards, Peter ___________________________________________________________ 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: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
