Prutha Kulkarni - I would like to move this into the backlog as it is a lower priority than some IGB codebase tasks.

How much have you done on it? Should I hold off on moving it to the backlog to give you a chance to finish? Either way is fine. Just let me know.

I would just need a few more minutes and I would then move the ticket to the First Level Review.
I would do it by today EOD.
Would that be okay?
cc: [~aloraine]

Basically the genome dashboard is making use of node-fetch library in order to fetch mergerd quickload data which is present at the location:
https://bitbucket.org/lorainelab/integrated-genome-browser/raw/master/core/igb-preferences/src/main/resources/igbDefaultPrefs.json

• The fetch method when requested data won't show any weird behavior as usually it returns a javascript promise and in case of failure it just rejects the promise with a normal response i.e. The Promise returned from fetch() won’t reject on HTTP error status even if the response is an HTTP 404 or 500. Instead, it will resolve normally (with ok status set to false), and it will only reject on network failure or if anything prevented the request from completing.

You could refer the link mentioned below to know more about the operation.
https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch

To add to what Prutha Kulkarni has found, the mergeAllQuickLoadSites function she describes gets genome version names and scientific names for species. As I understand it, genome dashboard doesn't actually contact quickload sites in order to obtain genomic data, but instead hits an IGB endpoint specifying a genome version, at which point IGB reaches out to the relevant quickload site.

The request URI looks something like:
'http://localhost:7085/IGBControl?version=<genomeVersion>'