I have installed the rsync data manger into galaxy and am attempting to locate the human genome assemblies through the dbkey search but no results are populating the field. Previously I was able to use this to find the genomes I needed but now it appears to no longer function. Is there a better method to adding genomes for use in a local galaxy other than this.
We will follow up for the rsync fetching option problems (this has come up before, but is not ticketed). If you have time, could you add a comment about which genome - specifically by dbkey - is problematic?
Meanwhile, alternatives include:
Obtaining the data directly from rsync locally, loading it into a history, then using that as input. (Just get the <dbkey>/seq/<dbkey>.fa file). Once the new genome has been added, create all indexes new on your instance. It is only worth doing this for genomes that you find at http://usegalaxy.org but are not available at the original public source, or have been modified in some way to not be the same as the public source. There are very few of this type.
Load any fasta file into a history the admin account can access and run the data manager on the file that way. This is similar to item 1 above, but the source would not be the rsync server, but some other public data resource, or your own groups genome/transcriptome builds.
Load the data from the public source directly (when that source is supported by the fetching tool).
Not directly related, but has much information about reference genomes in general and how to avoid issues with them - for you and others reading later - (I am guessing that you chose to use rysnc originally to avoid a mismatch problem): https://wiki.galaxyproject.org/Support#Reference_genomes
Hope one of these works out for you, but let us know if not.
Jen, Galaxy team