59cdd5fa35f3630172e775460b28cdbb8556e6f2 brianlee Thu Jun 9 11:20:41 2022 -0700 Noticed gS_otherUserSessionName vs hgS_otherUserSessionName documentation error (added w/87eae20d) and fixed it and made other improvements on FAQlink, no RM diff --git src/hg/htdocs/FAQ/FAQlink.html src/hg/htdocs/FAQ/FAQlink.html index b412092..e38adc4 100755 --- src/hg/htdocs/FAQ/FAQlink.html +++ src/hg/htdocs/FAQ/FAQlink.html @@ -57,48 +57,62 @@ The easiest way to save and share tracks from the URL is by <a href="../cgi-bin/hgLogin" TARGET="_blank">logging in</a> to your Genome Browser account and creating a <a href="../goldenPath/help/hgSessionHelp.html">saved session</a>. Saved sessions are a versatile way to share data that may include native annotations, Custom Tracks, Track Hubs, and Assembly Hubs. In these examples, text in brackets <b>"<"</b> and <b>">"</b> indicate places where the user supplies information. Note that the brackets are not needed for the URL, including the brackets will result in a 'Could not find session' error.</p> <p> You will be able to share Genome Browser sessions with the following link format:</p> <p><code>http://genome.ucsc.edu/s/<userName>/<sessionName></code></p> <p> For instructions on creating a saved session, go to the <a href="../goldenPath/help/hgSessionHelp.html#Create" target ="_blank">session user guide</a>. If you want to specify track settings in a URL directly, please read the section on <a href="#trackViz">setting track visibility via URL</a> for a complete description. </p> - +<h6> Loading sessions on other tools</h6> <p> Or if you prefer the older style, which allows you to link to different tools, you may use the -following format:</p> -<p><code>http://genome.ucsc.edu/cgi-bin/hgTracks?hgS_doOtherUser=submit&hgS_otherUserName=<userName>&gS_otherUserSessionName=<sessionName></code></p> +following parameters:</p> +<ul> + <li id="hgS_otherUserName"><code>hgS_otherUserName=<userName></code></li> + <li id="hgS_otherUserSessionName"><code>hgS_otherUserSessionName=<sessionName></code></li> + <li id="hgS_doOtherUser"><code>hgS_doOtherUser=submit</code></li> +</ul> +<p> +Here is an example:</p> +<p><code>http://genome.ucsc.edu/cgi-bin/hgTracks?hgS_doOtherUser=submit&hgS_otherUserName=<userName>&hgS_otherUserSessionName=<sessionName></code></p> <p> This longer format has the flexibility of replacing "hgTracks" with different tool names to share saved settings on the Table Browser (hgTables), Variant Annotation Integrator (hgVai), or Data Integrator (hgIntegrator). This will preserve your option selections and can be useful to share. The following format will bring the recipient to a user's custom Table Browser selections:</p> <p><code>http://genome.ucsc.edu/cgi-bin/hgTables?hgS_doOtherUser=submit&hgS_otherUserName=<userName>&hgS_otherUserSessionName=<sessionName></code></p> <p>Both session link formats have the advantage of being able to add URL parameters to the end. The shorter link format requires a question mark before any URL parameters, with ampersand characters separating different parameters like so: </p> <p><code><a href=http://genome.ucsc.edu/s/view/clinicalzoom?textSize=18>http://genome.ucsc.edu/s/view/clinicalzoom?textSize=18</a></code></p> <p>Both formats require an ampersand between each additional parameter, seen in the longer format like so:</p> <p><code><a href=http://genome.ucsc.edu/cgi-bin/hgTracks?hgS_doOtherUser=submit&hgS_otherUserName=view&hgS_otherUserSessionName=clinicalzoom&textSize=18>http://genome.ucsc.edu/cgi-bin/hgTracks?hgS_doOtherUser=submit&hgS_otherUserName=view&hgS_otherUserSessionName=clinicalzoom&textSize=18</a></code></p> +<p> +Another option for sessions is to download the file and host it in an external location and load it with +<code id="hgS_doLoadUrl">hgS_doLoadUrl=submit</code> and +<code id="hgS_loadUrlName">hgS_loadUrlName=<URL></code> allowing you to externally maintain your session, +or update it as you wish. Here is an example:</p> +<p><code><a href="https://genome.ucsc.edu/cgi-bin/hgTracks?hgS_doLoadUrl=submit&hgS_loadUrlName=http://genome.ucsc.edu/goldenPath/help/examples/sessions/session.hg19.stopCodons"> +https://genome.ucsc.edu/cgi-bin/hgTracks?hgS_doLoadUrl=submit&hgS_loadUrlName=http://genome.ucsc.edu/goldenPath/help/examples/sessions/session.hg19.stopCodons</a></code></p> <a name="link2"></a> <h2>Linking to the Browser at a specific position, or default position</h2> <h6>How do I make a link to a specific genome, position, or HGVS variant?</h6> <p> You can link to a specific genome assembly and position in the Genome Browser using a URL with the <code>db=</code> and <code>position=</code> parameters.</p> <p><code>http://genome.ucsc.edu/cgi-bin/hgTracks?db=<assembly>&position=<position></code></p> <p> Where:</p> <ul> <li> <code>db</code> - designates a specific genome assembly. For example, <code>db=hg19</code> refers to the Feb. 2009 human genome release. For a list of db parameter values that correspond to UCSC assemblies, see the <a href="FAQreleases.html#release1">list of UCSC