Details
-
Type: Improvement
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 2.10.0
-
Fix Version/s: None
-
Component/s: data retrieval services, Datamodel, gui, gui design issue
-
Labels:None
Description
In Jalview 2.10, if one:
1. imports sequence data with arbitrary start/end numbering
2. creates sequence features or adds sequence associated annotation rows (e.g. by dropping a PDB structure onto the sequence which has the same name, or importing an annotation file)
3. Uses the 'View 3D structure...' option, or fetches db-refs manually to retrieve the correct start/end numbering
The annotation and features created in 2 will be relocated to different positions in the sequence, rather than their locations updated so they remain in the same position.
Practially, this means that if someone imports a sequence fragment, begins to annotate it manually, then uses any of Jalview's db-accession validation mechanisms, they risk corrupting their annotation data.
The workaround is to always verify start-end numbering before starting to do any annotation work, but it would be good if we could make it so Jalview users didn't have to care *when* they started to create annotation on sequence data. Particularly when database fetches may take a long time (e.g. for large numbers of sequences).
1. imports sequence data with arbitrary start/end numbering
2. creates sequence features or adds sequence associated annotation rows (e.g. by dropping a PDB structure onto the sequence which has the same name, or importing an annotation file)
3. Uses the 'View 3D structure...' option, or fetches db-refs manually to retrieve the correct start/end numbering
The annotation and features created in 2 will be relocated to different positions in the sequence, rather than their locations updated so they remain in the same position.
Practially, this means that if someone imports a sequence fragment, begins to annotate it manually, then uses any of Jalview's db-accession validation mechanisms, they risk corrupting their annotation data.
The workaround is to always verify start-end numbering before starting to do any annotation work, but it would be good if we could make it so Jalview users didn't have to care *when* they started to create annotation on sequence data. Particularly when database fetches may take a long time (e.g. for large numbers of sequences).
Attachments
Issue Links
- related with
-
JAL-2162 edit start/end of alignment sequence relocates annotation derived from structure
- Open