Nowlan Freese added a comment - 15/Oct/19 2:58 PM - edited Created multiple quickloads to test if the index attribute in annots.xml is functioning correctly in quickloads. Tested IGB 8.5.4, 9.0.0, 9.0.2, and 9.1.0 (see attached images) as of October 15, 2019. The index attribute only works if the full URI is specified to the data. For example, having a local or remote quickload that specifies the full path to remotely hosted data works correctly (all files load). If the index attribute is specified and the data use relative URIs, data do not load correctly. For example, a local quickload with local data using relative URIs can only load a bam file with a bai in the same folder with the same name. Interestingly, if the quickload is in Amazon with the data also stored in amazon with relative URIs, none of the data is able to load, including the bam/bai in the same folder and with the same name. If the index attribute is omitted, a quickload in amazon using relative URIs can load the bam/bai in the same folder and with the same name, which is how our current IGB quickloads are designed. To test: Unzip the attached quickloads.zip and add the two local quickloads and the following remote quickloads in the configure data panel: https://quickload-testing.s3.amazonaws.com/QL_Amazon_Target_CyVerse https://quickload-testing.s3.amazonaws.com/QL_Amazon_Target_Amazon https://quickload-testing.s3.amazonaws.com/QL_Amazon_Target_Amazon_noIndex Next, go to the Arabidopsis genome, chromosome 1, zoom all the way in, and go to the beginning position of the chromosome. Select the files from the quickloads and load data.

Nowlan Freese added a comment - 15/Oct/19 3:02 PM May be worth taking a look at the IGBF-445 code changes to understand why relative URIs are not working with the index attribute.