Assembly Data Hubs extend the functionality of Track Data Hubs to assemblies that are not hosted natively on the Browser. Assembly Data Hubs were developed to address the increasing need for researchers to annotate sequence for which UCSC does not provide an annotation database. They allow researchers to include the underlying reference sequence, as well as data tracks that annotate that sequence. Sequence is stored in the UCSC twoBit format, and the annotation tracks are stored in the same manner as Track Data Hubs. For more information on how to setup your own Assembly Data Hub, please refer to the Assembly Hub wiki and see the Quick Start Guide to Assembly Hubs.
-Public hubs
The Genome Browser provides links to a collection of public track hubs that have been registered
-with UCSC. To view a list of the public track hubs available for the currently selected assembly,
-click the "track hubs" button on the Genome Browser gateway or annotation tracks page. The
-Public Hubs tab on the Track Hubs page lists the hubs that are available for display in the browser.
-To add a hub to your display, click the "Connect" button next to the hub. You can also
-click "Description" and "Hub Name" to see more details about some Public Hubs.
-After connecting to the hub, click the "Genome Browser" link from the top blue bar. The
-default assembly for the selected hub will be displayed with hub tracks in a separate track group
-below the browser image. The tracks can be configured and
-manipulated in the same fashion as native browser tracks. As with any very large track in the
-Genome Browser, exercise caution when viewing a broad genomic region that requires the Genome
-Browser to display a large number of track features: the browser display may time out.
-Unlisted hubs (located in the My
-Hubs tab)
-In addition to the publicly available hubs listed on the Public Hubs tab, it is possible to load
-your own unlisted track hub or one created by a colleague as long as you know its URL. To add an
-unlisted hub, open the Track Hubs page and click the My Hubs tab. This tab lists the unlisted track hubs that you have loaded into
-your browser. To import a new hub, type its URL into the text box, then click the Add Hub button.
-If the track hub is imported successfully, it will be added to the list. It is also possible to add
-a track hub by directly adding the hub's URL to the browser URL. If you add
+with UCSC. To view a list of the public track hubs available, click into the blue navigation bar
+"My Data" and then "Track Hubs" to reach the
+Public Track Hubs page.
+You can click links in the "Description" column to see details about a particular Hub.
+To view a hub's data, click on an assembly name on the row of your
+hub or the "Connect" button. If you clicked the "Connect" button,
+choose your assembly or click the "Genome Browser" link from the top blue bar to be brought to the
+default assembly. The selected hub tracks will be listed in a separate track group
+below the browser image and can be configured just like
+native browser tracks. Exercise caution when viewing a wide region that requires the Genome
+Browser to display a large number of track features: the browser display may time out.
+
In addition to the Public Hubs listed, it is possible to load +your own track hub or one created by a colleague. To add an +unlisted hub, open the Track Hubs page and click the +My Hubs tab. +To import a new hub, type or paste its URL into the text box, then click the Add Hub button. +If successful, your track hub will appear on that page.
++It is also possible to add or share a track hub by directly by URL. If you add hubUrl=[URL] to your hgTracks URL line, it will add the hub directly into the -browser (e.g., -http://genome.ucsc.edu/cgi-bin/hgTracks?db=hg19&hubUrl=http://vizhub.wustl.edu/VizHub/RoadmapRelease3.txt). -If the hub you've selected is an assembly hub, the supported assemblies will be selectable from the -gateway page by selecting the name of the track hub in the group pulldown.
--If the browser is unable to load the track hub, it will display an error message. Some common causes -for an import to fail include typos in the URL, attempting to add a track hub from a different -assembly, a hub server that is offline, or errors in the track hub files. Once you have successfully -loaded a hub, you can view it in the browser by clicking the "Connect" button. Please note -that unlisted hubs are in no way secure. The URL helps to obfuscate the location of the data; it is -a simple barrier to casual users. Please also know that hubs can be loaded from a local directory -when using GBiB.
--To remove a track hub from your Genome Browser display, click the "Disconnect" button on -the Track Data Hubs page.
--Occasionally, remote track hubs may be missing, off-line, or otherwise unavailable. If a user is -already browsing data from the remote hub when it disconnects, a yellow error message will be -displayed instead of the expected data.
+browser: +-The track sets in hubs are genome assembly specific. The Track Hubs page lists each hub and the -assemblies it supports. To switch to a different assembly, click the Genomes link in the top menu -bar, then select the new assembly from the Gateway page. If the hub supports assemblies that are not -natively supported by UCSC or the mirror you're visiting, the assembly can be selected by choosing -the track hub name under the group menu.
+If you are adding an assembly hub with multiple genomes, you can link directly to hgGateway, +the assembly selection page and a particular genome: +Tracks accessed through a hub can be used in Genome Browser sessions and custom tracks in the same manner as other tracks. The data underlying data hub tracks can be viewed, -manipulated, and downloaded using the UCSC Table Browser.
- +manipulated, and downloaded using the UCSC Table Browser. +To remove a track hub from your Genome Browser display, click the "Disconnect" button on +the Track Hubs page. ++For confidential or private data,please note +that unlisted hubs are not secure. The URL helps to hide the location of the data; it is +a simple barrier of obscurity. Please also know that hubs can be loaded from local directories +when using GBiB.
This section provides a step-by-step description of the process used to set up a track hub on your own server.
To create your own hub you will need:
Note that you will have to use the udcDir if /tmp/udcCache is not writable on your machine.
The hubCheck program is available from the UCSC downloads server at http://hgdownload.soe.ucsc.edu/admin/exe/.
+ ++If the browser is unable to load a track hub, it will display an error message. Some common causes +for an import to fail include typos in the URL, a hub server that is offline, +or errors in the track hub configuration files. Occasionally, remote track +hubs may be missing, off-line, or otherwise unavailable. If a user is +already browsing data from the remote hub when it disconnects, a yellow error message will be +displayed instead of the expected data.
+The Genome Browser supports searching for items within bigBed tracks in track data hubs. To support this behavior you have to add an index to the bigBed file when you initially create the the bigBed file from the bed file input. Indices are usually created on the name field of the bed, but can be created on any field of the bed. Free-text searches can also be enabled by creating a TRIX index file that maps id's in the track to free-text metadata. Further intructions can be found in the Searchable Hub Quick Start Guide.
See the searchIndex and searchTrix fields in the Hub Track Database Definition document for information on how to set up your bigBed to enable searching. The searchIndex setting requires