BAM data slices from DAS/2 not merging - ID: 3402835

Looks like BAM data slices loaded from a DAS/2 source are not being merged. Thus when one moves to a different location and hits Refresh Data a new track is created. This is a recent issue and wasn't a problem 6 months ago.

I also noticed that the name given to the data track isn't the DAS/2 delivered name but a local temp file? This is also a new bug.

To reproduce this navigate to chrY on Human_Feb_2009, enable the UofUBioinformatics Core DAS/2 server and goto -> BamTest -> ChrY -> select the "All Paired 101bp Fixed" track. then zoom in on a gene hit Refresh Data, move over a few mb, hit Refresh again.

Note this is particular to BAM data and doesn't appear to be a problem with other binary data such as xxx.useq.