Details
-
Type:
Task
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Component/s: data retrieval services, Datamodel
-
Labels:
-
Epic Link:
Description
Up to Jalview 2.9.x, we have encoded the properties and relationships between a specific set of datasources for the purposes of showing cross references (EMBL/Ensembl vs Uniprot), and recognising when to create distinct alignment views for each accession retrieved (Pfam, Rfam).
Some of this was done via the groupings and canonical string identifiers in jalview.datamodel.DBRefSource, and there were (in previous versions), semantic groupings to support recognition of domain or coding database references from an arbitrary set of DBRefEntry objects.
We now need a clearly defined api to ensure that the source field in DBRefEntry objects are interpreted correctly as a particular canonical database identifier, allowing unambiguous identification of the properties those references provide.
Some of this was done via the groupings and canonical string identifiers in jalview.datamodel.DBRefSource, and there were (in previous versions), semantic groupings to support recognition of domain or coding database references from an arbitrary set of DBRefEntry objects.
We now need a clearly defined api to ensure that the source field in DBRefEntry objects are interpreted correctly as a particular canonical database identifier, allowing unambiguous identification of the properties those references provide.