39f03efc4e38cefcf29a8456f52037a92363a89a lrnassar Wed Nov 9 16:21:35 2022 -0800 Typo fix from CR. Refs #30246 diff --git src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html index fdfbbc0..9d3dfbf 100755 --- src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html +++ src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html @@ -1108,31 +1108,31 @@ one must first create an account, upload the bigDataUrl files, create shareable links, and then edit your hub.txt, genomes.txt, and trackDb.txt appropriately. One advantage to using Figshare is their emphasis on usage statistics, so institutional accounts can see how often their hubs and tracks are being accessed by others.

Note that Figshare does not use filenames as part of the URLs, therefore bigDataUrl files that require a separate index file, like VCFs and BAM files, must have their index file location specified with a bigDataIndex. This keyword is relevant for Custom Tracks and Track Hubs. You can read more about bigDataIndex in the TrackDb Database Definition page.

If you are having issues hosting at figshare, try to use the file's download URL. This -URL will have "ndownloader" in its path. Also for custom you will need to +URL will have "ndownloader" in its path. Also, for custom tracks you will need to declare a track line with track type and bigDataUrl. Below is a simple example of a bigBed custom track on hg38:

 track type=bigBed name="figshare example" bigDataUrl=https://figshare.com/ndownloader/files/38068053
 

For more information on using Figshare, please see their Support Portal.

Troubleshooting your own HTTPS server configuration

When your own institution's system administrators are hosting your data they may benefit from this section about ensuring a secure HTTPS configuration. The most popular web servers