inconsistency in data library display
![](https://secure.gravatar.com/avatar/6bc7da2514bfc4eb385cabe18a4cbce3.jpg?s=120&d=mm&r=g)
I'm uploading a bunch of fastq.gz files to a data library. I'm currently doing this one file at a time to test some API functionality. I noticed that right after the web page refreshes itself, the file name is displayed with a '.gz' at the end. If I navigate to the data library by clicking on 'Manage Data Libraries", etc, the file is displayed without the '.gz'. Not a big deal, but it was throwing me off for a while trying to figure out how to use the underlying API.
![](https://secure.gravatar.com/avatar/6bc7da2514bfc4eb385cabe18a4cbce3.jpg?s=120&d=mm&r=g)
Follow up to this - While playing with the API, the name is actually stored with '.gz'. Somewhere along the way, galaxy updates the name in the database to not have a '.gz' extension. On Tue, Dec 23, 2014 at 4:37 PM, Ryan G <ngsbioinformatics@gmail.com> wrote:
I'm uploading a bunch of fastq.gz files to a data library. I'm currently doing this one file at a time to test some API functionality. I noticed that right after the web page refreshes itself, the file name is displayed with a '.gz' at the end. If I navigate to the data library by clicking on 'Manage Data Libraries", etc, the file is displayed without the '.gz'.
Not a big deal, but it was throwing me off for a while trying to figure out how to use the underlying API.
participants (1)
-
Ryan G