cfd961e29652fe4d249f219126d8c41ba8d83d1c brianlee Mon Jun 13 06:28:35 2022 -0700 Added a section in Session Gallery about Public Sessions and how labs can make their own Lab Session Gallery refs #19784 diff --git src/hg/htdocs/goldenPath/help/sessions.html src/hg/htdocs/goldenPath/help/sessions.html index ce6691f..3d7e28c 100755 --- src/hg/htdocs/goldenPath/help/sessions.html +++ src/hg/htdocs/goldenPath/help/sessions.html @@ -355,30 +355,51 @@ that can include custom tracks allowing snapshots of browser activities. Multiple sessions may be saved for future reference, for comparing different data sets, or for sharing with your colleagues. Follow these links to learn how to <a href="hgSessionHelp.html#Create" target="_blank">create</a> and <a href="hgSessionHelp.html#Share" target="_blank">share</a> sessions.</p> <a name="What2"></a> <h3>What is the session gallery?</h3> <p> The Session Gallery is a collection of track views that help highlight viewing different topics in the browser. The sessions in the Session Gallery were created in the browser and then saved to a local file, which was then uploaded to an online location. This allows creating a single link, such as http://genome.ucsc.edu/cgi-bin/hgTracks?hgS_doLoadUrl=submit&hgS_loadUrlName=U, where <strong>U</strong> is the URL of the session file, e.g. http://www.mysite.edu/~me/mySession.txt, enabling users to maintain external control of the content file for easy update.</p> +<h6 id="lab">Public Sessions - make a Session Gallery for your laboratory!</h6> +<p> +After the creation of this Session Gallery page, UCSC created short links to sessions +and released our <a target="_blank" href="/cgi-bin/hgPublicSessions">Public Sessions</a> page. +Public Sessions allows users to publish their sessions and annotate them with a description. +By using the <code>search=searchTerm</code> feature, it is now possible for groups to create +their own laboratory-focused Session Gallery, by selecting sessions to add to the Public Sessions +collection and describing their data with common unique terms.</p> +<p> +For example, a link to the Public Sessions page such as +<a href="http://genome.ucsc.edu/cgi-bin/hgPublicSessions?search=protein" +target="_blank">http://genome.ucsc.edu/cgi-bin/hgPublicSessions?search=protein</a> +will search all Public Sessions with "protein" mentioned in their description. +If "protein" were replaced with "YourLabName" you could then have a link +to display a gallery of sessions related to your laboratory data. Another example is +<a href="http://genome.ucsc.edu/cgi-bin/hgPublicSessions?search=sessionView" +target="_blank">http://genome.ucsc.edu/cgi-bin/hgPublicSessions?search=sessionView</a>, which +uses the unique term "sessionView" to collect related sessions. Read more +in this <a href="https://genome.ucsc.edu/blog/sharing-data-with-sessions-and-urls/#sessions" +target="_blank">blog post</a>.</p> + <a name="links"></a> <h3>Don't copy that link -- make a Session!</h3> <p> Please see the <a href="http://genome.ucsc.edu/blog/how-to-share-your-ucsc-screenthoughts/" target="_blank">How to share your UCSC screenthoughts</a> and <a href="http://genome.ucsc.edu/blog/sharing-data-with-sessions-and-urls/" target="_blank">Sharing Data with Sessions and URLs</a> blog posts for a discussion about sessions.</p> <p> Most new users make the mistake of sharing a URL of the current view to others for collaboration. This can lead to many problems as each URL is given a unique identifier called a <strong>"hgsid"</strong> that allows users to continue actively manipulating their data across different platforms (FireFox,Chrome,IE). The person one shares the link with will be interpreted as the same user and will have the power to continue manipulating the original shared content.</p>