Implementation is done, when testing found out that the API is returning a different value now for the hubUrlPrefix, which we were planning to use to build the hub.txt url. After discussing with Nowlan Freese, we decided to hardcode the prefix url, which would be the genark hub domain for now, and follow up with the UCSC team for more info.
Nowlan Freese here is the context:
The value for the variable hubUrlPrefix in this API (https://api.genome.ucsc.edu/list/genarkGenomes) has been changed from an actual hub domain (https://hgdownload.soe.ucsc.edu/hubs) to some relative path (/gbdb/genark) we were planning to use the original value to build the hub Url for each genome (by adding the hubUrlPrefix to the hubUrl variable present inside the genome object) and use the hub.txt to load the hubs into IGB.
Example hub.txt url built from the API response:
Before the changes: https://hgdownload.soe.ucsc.edu/hubs/GCA/000/001/905/GCA_000001905.1/hub.txt
After the changes: /gbdb/genark/GCA/000/001/905/GCA_000001905.1/hub.txt (this isn’t the actual hub.txt location, which is giving us an issue to load the hub)
May we know why the change occurred? Is it safe to assume https://hgdownload.soe.ucsc.edu/hubs this would be the domain for the genark genomes in the future as well, so that we can hardcode it on our end? Or else is there any other API that can give us the actual domain for the genark hub?
Will change the code to use the hardcoded domain and do the testing again.
Implementation is done, when testing found out that the API is returning a different value now for the hubUrlPrefix, which we were planning to use to build the hub.txt url. After discussing with Nowlan Freese, we decided to hardcode the prefix url, which would be the genark hub domain for now, and follow up with the UCSC team for more info.
Nowlan Freese here is the context:
Will change the code to use the hardcoded domain and do the testing again.