On Mon, Dec 14, 2009 at 06:26:41PM -0800, Marek Szuba wrote: > Now that I've got a working prototype for this (which you can find in > my 'ucsc_ensembl' GitHub branch), Chris believes it is time to discuss > the final form - or, in other words, the schema. Here is some > information about the data in question and what needs to be done to > obtain different types of annotations.
Hi Marek, could you post a script or two showing how you might work with this schema in practice? Thanks! Uncommented test scripts are just fine :) > 3. Protein annotation: get the SQLTable used for transcript > annotations, then connect it with MapView to another one attached to > ensGtp, with the protein-ID column as the primary key. For each protein > ID specified by the user use the MapView to obtain the corresponding > transcript ID, then return appropriate transcript information. One > question: shall we hide from the user that protein data (s)he gets is > actually transcript data (i.e come up with some sort of a wrapper) or > just let him/her have it as it is? I don't understand this question... is the problem that the "transcript IDs" would actually be protein IDs? If only for traceability, I would suggest a wrapper. > That's it. Please let me know what you think. Seems good in abstract but I'm kind of code-focused so I'd be interested in how actually working with this data looks. cheers, --titus -- C. Titus Brown, c...@msu.edu -- You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-...@googlegroups.com. To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en.
