e67a7fb01f99795dce4381516669678731f71a5e brianlee Sat Jan 11 11:27:04 2020 -0800 Adding NIH link on Hosting refs #24744 diff --git src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html index 4462edf..a14edb2 100755 --- src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html +++ src/hg/htdocs/goldenPath/help/hgTrackHubHelp.html @@ -846,31 +846,39 @@ if you knew that a setting called "ensemblAssemblyName" was supported for use in track hubs by Ensembl, you could create a single line file that included the setting "ensemblAssemblyName". Then, when you want to check a hub that includes these extra trackDb settings, you would then specify this extra settings file on the command line:</p> <pre><code>$ hubCheck -checkSettings -extra=http://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubCheckUnsupportedSettings/myExtraSettings.txt http://genome.ucsc.edu/goldenPath/help/examples/hubExamples/hubCheckUnsupportedSettings/hub.txt </code></pre> <p> (Note: The settings listed here in the "extra" file are just examples and do not represent real trackDb variables for hubs at Ensembl.) <!-- ========== Where to host your data ============================== --> <a name="Hosting"></a> <h2>Where to host your data?</h2> <p> As stated in <a href="#Intro">What Are Track Hubs?</a>, track hubs files must be located -in web-accessible locations that support byte-range requests. If your institution does not +in web-accessible locations that support byte-range requests. Often universities provide a +location for researchers to place shareable data on the web and contacting your institution's +system administrators will help discover a location to store your data. For example, if you +work at the NIH, there is an internal data sharing <a href="https://hpc.nih.gov/nih/datashare.html" +target="_blank">NIH network</a> site. Sometimes institution firewall rules can change, and +you may need to inform your system administrators to add browser IP addresses as exceptions, listed +<a href="http://genomewiki.ucsc.edu/index.php/Public_Hub_Guidelines#Connection_issues.3F" +target="_blank">here</a>.</p> +<p>If your institution does not provide web hosting space for you, we know of at least the following sites where you can host your data and configuration files for free:</p> <ul> <li><a href="https://de.cyverse.org/de/" target="_blank">CyVerse Discovery Environment</a></li> <!--<li><a href="https://usegalaxy.org/" target="_blank">Galaxy</a></li>--> <li><a href="https://github.com/" target="_blank">Github</a></li> <li><a href="https://figshare.com/" target="_blank">Figshare</a></li> </ul> <p> Each of the providers above has a slightly different approach to hosting data for compatibility with the UCSC Genome Browser, and may have different advantages and disadvantages, such as size limitations, usage statistics, and version control integration. Additionally, as previously mentioned, any provider that supports byte-range access will work for hub hosting, and you are not limited to the above sites. Below is a summarized guide for each of the providers mentioned above.</p>