That was automatically assigned by the Table Browser. So whatever you decide to send over as the “dbkey”, is what Galaxy would also populate. We don’t have a mechanism for mapping/changing external IDs. The return direction is always the same value. But users can create custom database/dbkeys. They just need a way to learn what those are, which is usually by fetching data from the TB or checking the Downloads area… which loop back around
It looks like the initial changes are on the UCSC test server so far. My guess is that they are still working on remainder. The idea seems to be to have the UCSC server both host and receive a consistent database key to link everything together. We know what that will be but it isn’t implemented yet so you cannot use it quite yet. But, this will happen which is pretty great for a bunch of reasons. We’re really glad that you asked the question.
