Open jennaj opened 7 months ago
We are now considering these changes: 1) send the GCA_xxxx ID as db_key to Galaxy 2) accept the GCA_xxxx ID in all incoming links. 3) send a list of GCA_xxx IDs (Jen already has the URL, see above) that we accept to Galaxy and ask that Galaxy pulls this file every day or so.
Does this sound reasonable?
Hi @maximilianh. not
or now
?
Oh boy, I read over it, but didn't see the typo, sorry. Thanks @bgruening.
We fixed (2) on genome-test yesterday, but still need to do (1)
Some cool progress, if we have this in place it would be soooo good for our users! :+1:
Yes, and then the future steps will be, one day: 1) make liftOver alignments or maybe even add entire assemblies in Galaxy (as discussed over beer with Anton, I think in Montpellier) 2) somehow let UCSC grab these alignments or assembly files
On Tue, Apr 30, 2024 at 11:25 AM Björn Grüning @.***> wrote:
Some cool progress, if we have this in place it would be soooo good for our users! 👍
— Reply to this email directly, view it on GitHub https://github.com/galaxyproject/idc/issues/47#issuecomment-2084814704, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACL4TIYVEAMKTTMJZBJSGLY75PSHAVCNFSM6AAAAABG3PFAPCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUHAYTINZQGQ . You are receiving this because you were mentioned.Message ID: @.***>
Discussion and use case https://help.galaxyproject.org/t/no-link-for-ucsc-to-visualise-datasets/12260/
From UCSC. This would either be in addition to the ucsc.builds.txt You will also need all genbank-ids that we have here on our side… as a text file: https://hgdownload.soe.ucsc.edu/hubs/UCSC_GI.assemblyHubList.txt
What might work
Known wrinkles so far