Changes between Initial Version and Version 1 of DevMtgMinutes/20090205


Ignore:
Timestamp:
Feb 5, 2009, 4:27:42 PM (17 years ago)
Author:
Scooter Morris
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DevMtgMinutes/20090205

    v1 v1  
     1== February 5, 2009 ==
     2'''Attendees''': Scooter, Greg, Eric, TomF, Elaine
     3
     4=== New Action Items ===
     5 * Conrad will look at how to get annotation information from RCSB that is not in the PDB or MMCIF files.
     6
     7=== Previous Action Items ===
     8 * Scooter will look into providing non-staff access to trac -- will be done Friday
     9 * Everyone will look at open trac issues and assign milestones if possible -- still working through them
     10 * Scooter and Eric will create and account for Wei to access trac -- depends on completing non-staff access to trac
     11 * Conrad will look into disabling stereo in orthographic view
     12 * tef will contact Adobe for more information about embedding 3d graphics in PDF documents -- add as a low priority enhancement request to trac
     13
     14=== Minutes ===
     15
     16 1. Previous Action Items
     17 1. Open bug report updates
     18 1. Discussion of sequence annotation possibilities -- Eric
     19  * More generally, how we associate metadata (annotations) with sequence and structure.  Lots of data sources, but the question is how do we present this data.
     20  * General solution is to allow render by attributes to apply to named selections (groups).
     21  * One option is to use named selections to represent groups.
     22  * Difficult to present a user interface if groups are not hierarchical.
     23  * Important to integrate annotations with both sequence and structure.  Some annotations will be on the sequence and you want to see it on the structure, some annotations will be on the structure directly.
     24  * Have two related projects for 1.4, need a long-term strategy for how to handle.  If we're going to use named selections as the underlying mechanism, we need a better way for users to interact with them.
     25