| 81 | | * (search other databases such as NR? PSI-BLAST on NR?) |
| 82 | | * connect to our own Web service to multiple sequence alignment program (Muscle, T-Coffee, ... see [http://www.cgl.ucsf.edu/home/meng/sources.html#d list and links]), show result in MAV. I guess input to server would be sequence alignment sent from MAV, probably would have to reformat into unaligned multi-FASTA. ECM |
| | 81 | * (search other databases such as NR? PSI-BLAST on NR?) |
| | 82 | |
| | 83 | * connect to our own Web service to multiple sequence alignment program (Muscle, T-Coffee, ... see [http://www.cgl.ucsf.edu/home/meng/sources.html#d list and links]), show result in MAV. Input would be sequence alignment already open in Chimera, probably would have to reformat into unaligned multi-FASTA for server. ECM |
| | 84 | |
| 84 | | * allow specifying sequence to add by accession (Uniprot perhaps?). Its feature annotations would automatically come along as regions. ECM |
| 85 | | * would we want Fetch by ID for sequences? (would we want a sequence with no structure not aligned with any other sequences?) |
| 86 | | * for existing sequences, allow specifying Uniprot accession for annotation retrieval, parse XML, load feature annotations as sequence regions. (actually I don't know if that would work - what if the existing sequence and that uniprot sequence were even slightly different?) ECM |
| | 86 | |
| | 87 | * allow specifying "sequence to add" by accession (GI number? Uniprot accession?). Its feature annotations would automatically come along as regions. ECM |
| | 88 | * would we want Fetch by ID for sequences? (would we want a sequence with no structure and not aligned with any other sequences?) |
| | 89 | |
| | 90 | * for existing sequences, allow specifying accession for annotation retrieval, load feature annotations as sequence regions (actually I don't know if that would work - what if the existing sequence and that database sequence were even slightly different?) ECM |
| | 91 | |