Hi @jasmus
You don’t need to specify the “datatype” or “database” when importing data. Most of the time is actually better to leave these at default (for both) when using the Upload functions.
Why?
- If Galaxy guesses the wrong datatype, that could indicate a format problem.
- The exact genome build/version usually does not apply to starting data (reads – these are associated with an organism, but not a genome build/version aka database). Once mapped or other downstream tools are used, then the result would be associated with a database (coordinates differ by the original database assembly).
- Most tools do not require that database is assigned to use a custom genome. If one does, or you just want to label your data with specificity, then load the custom genome (in fasta format) and promote it to a custom build in Galaxy. This will create a new “database” specific to your account, and you can assign it to any dataset. I added tags to this post that point to other Q&A plus FAQs that cover the “how-to”.
But first, you need to get the data into Galaxy! Few questions to troubleshoot FTP. Paste back what values you are using, we might be able to spot the problem.
- What is the URL of the Galaxy server you are working on?
- What are you entering in Filezilla for the “Host” field?
- Are you using your account’s email address and password (same as used on that exact same server) for the “username” and “password” fields? Don’t post the values back here – just confirm that is what you are using. Some people try to use their “public name” in Galaxy for the “username” in Filezilla – that won’t work – you need to use your full email address (this is a case-sensitive value – Me@school.edu is NOT the same as me@school.edu).
The size of the dataset(s) probably do not matter until you can connect at all. For reference, the maximum size is 50 GB for most data and ~35 GB for others (BAM in particular, possibly others).
If Filezilla itself is connected to the server, then times out during the data transfer, you can “resume” the transfer – log in with Filezilla to the target server, accept any security certificates, and find the resume function to start again. Note that this won’t work if you quit out of Filezilla – the app needs to stay open. If the data is large and your connection is slow, you might need to do this a few times. In those cases, sometimes this works better if you transfer only one file at a time – but much depends on your internet upload speed.
There is no waiting period or throttling for data transfer rates at the usegalaxy.* servers that I know of. Other public Galaxy sites might have that in place though. Or, your internet provider might throttle.
Let’s start from there to troubleshoot this more 