Hiram,
Thank you very much for the answer. We decided to stay away from pushing custom tracks programmatically to existing user sessions. I rather need to know the table which holds the custom session information to be able to enumerate all saved custom sessions (the once saved via "Session" menu, not to confuse with web session) and the list of tracks saved within each session. That way I'll be able to reconcile the tracks kept locally in our system vs. tracks uploaded by researchers to the GB directly. Obviously, I'm referring to our local GB mirror. My second question revolves around session maintenance. The user authentication fails on logging in to the session. Here is the sequence of events: 1. User accesses the Session Login in our local mirror then selects "Click here to sign in" link 2. Then we get genomewiki's login page: http://genomewiki.ucsc.edu/index.php.... 3. User logs in and genomewiki shoots back to return url provided in query string parameters. 4. The session login screen is still in logged off state. We simulated the same process with genuine Genome Browser and everything works like a charm. Can you please point out what could be the caveat? As I mentioned, our local mirror is identified by publically accessible IP address, although we are in process of setting up DNS name for it. Could IP based URL be a problem (I'm wondering how it could be...)? Your help in pointing us to the right direction will be highly appreciated. Thanks a lot for your prompt replies! Regards, Rouben. -----Original Message----- From: Hiram Clawson [mailto:[email protected]] Sent: Wednesday, March 18, 2009 4:15 PM To: Gargaloyan, Rouben Cc: [email protected]; Martin Curland Subject: Re: [Genome] Add tracks programmatically Good Afternoon Rouben: Please note the following discussion about adding tracks to the genome browser: src/product/README.trackDb If you can add one manually, you could maybe make an automatic process. Your fundamental problem is that users often do not submit correct data for a track and you would end up with a lot of meaningless tracks unless you have a curator to take them out. --Hiram Gargaloyan, Rouben wrote: > Hello, > > I'm building a web site to interface with Genome Browser. Currently I'm using > your formatted URL approach to make the custom tracks available within a > group. > > It works great but we want to be able to programmatically upload a permanent > annotation track to our local mirror. > > I learned from your documentation that custom tracks never become part of > MySQL database and use specific controllers which read track data directly > from File System. I presume, there is a database table which holds a > reference to a local disk path which I could set programmatically upon > copying my custom track to specific location (please define) within the > genome browser. > > To summarize my question, I need your help in letting me: programmatically > upload a track to be globally available to all Genome Browser mirror users. > > Your hints will be very much appreciated. > > Thank you very much for your work! > > > Rouben Gargaloyan. _______________________________________________ Genome maillist - [email protected] http://www.soe.ucsc.edu/mailman/listinfo/genome
