Changes between Version 85 and Version 86 of Release1.4

Timestamp:

Apr 15, 2009, 11:30:25 AM (17 years ago)

Author:

pett

Comment:

--

Release1.4

@@ -23 +23 @@
   * (search other databases such as NR? PSI-BLAST on NR?) Ticket #7170
  1. Support PDB v3.2 Ticket #7056
+ 1. Annotations submenu in Select menu #7190
 
 == Features Desired for 1.4 ==
@@ -50 +51 @@
 
 === Core 4 (Tools for Integrated Sequence/Structure Analysis) ===
- 1. allow specifying "sequence to add" by accession code (Uniprot?). Its feature annotations would automatically come along as regions.  Ticket #7186
-  * would we want Fetch by ID for sequences? (would we want a sequence with no structure and not aligned with any other sequences?)
-  * perhaps allow specifying Uniprot accession or BLAST on Uniprot for existing sequences, retrieve and load feature annotations as sequence regions (would require global alignment to Uniprot sequence for correct mapping of features when the existing sequence is not identical)
-  * on my secondary MAV to-do list. EFP
+ 1. ~~allow specifying "sequence to add" by accession code (Uniprot?). Its feature annotations would automatically come along as regions.~~  Ticket #7186 ; mutated into "Annotations submenu" above as 1.4 release priority (still wanted as a feature, just not milestoned for 1.4)
+  * ~~would we want Fetch by ID for sequences? (would we want a sequence with no structure and not aligned with any other sequences?)~~
+  * ~~perhaps allow specifying Uniprot accession or BLAST on Uniprot for existing sequences, retrieve and load feature annotations as sequence regions (would require global alignment to Uniprot sequence for correct mapping of features when the existing sequence is not identical)~~
+  * ~~on my secondary MAV to-do list. EFP~~
  1. When aligning in a structure sequence, consider secondary structure markups of non-structure sequences Ticket #7187
  1. If gaps are created while adding a sequence, make corresponding gaps in any markups Ticket #7188