Details
Description
In the structured data model for SequenceFeatures / FeatureStore, how a SequenceFeature is stored (and retrieved) depends on these fields:
- type, begin, end
which between them determine, well, type, location, whether non-positional, and whether a contact feature.
The simplest way to ensure integrity of the data store if these values get changed is to make them final, i.e. force any change of these values to be done as a delete and re-add of the feature.
Other fields are free to be updated 'in situ'.
- type, begin, end
which between them determine, well, type, location, whether non-positional, and whether a contact feature.
The simplest way to ensure integrity of the data store if these values get changed is to make them final, i.e. force any change of these values to be done as a delete and re-add of the feature.
Other fields are free to be updated 'in situ'.
Attachments
Issue Links
- blocks
-
JAL-2541 Delete/Cut selection doesn't relocate sequence features correctly when start of sequence is removed
-
- Closed
-
-
JAL-2480 Encapsulate performant access to sequence features
-
- Closed
-
- depends on
-
-
- Closed
-
-
JAL-2556 New package for Uniprot data binding classes
-
- Closed
-
- related with
-
-
- Closed
-