During outbreaks of emerging diseases such as COVID-19, efficiently collecting, sharing, and integrating data is critical to scientific research. outbreak.info is a resource to aggregate all this information into a single location.
This will then add XBB.1.5* [Omicron (XBB.1.5.X)], when it should have added XBB.1.5.
Desired behavior
In Box 3, selecting "XBB.1.5" would add XBB.1.5
In Box 2, selecting "XBB.1.5 [Omicron (XBB.1.5.X)]" would add `XBB.1.5 [Omicron (XBB.1.5.X)]`
Why is this happening?
XBB.1.5 represents the Pango lineage XBB.1.5, whereas XBB.1.5* represents XBB.1.5 and all its descendants (lineages which have evolved from XBB.1.5). Right now, there's not a way to query this information on the API (yet), so we do a front-end lookup to lookup the sublineages associated with a small set of curated lineages. The front-end searches in CURATED_LINEAGES if there's a match, and then translates the name and query to be a OR query of all the sublineages.
This works, but should not be applied when the user asks explicitly for just that lineage.
For testing
I would use BQ.1 (1 lineage) vs. BQ.1* (should be ~ 80 lineages)
Steps to recreate
XBB.1.5
.Desired behavior
XBB.1.5
Why is this happening?
XBB.1.5 represents the Pango lineage XBB.1.5, whereas XBB.1.5* represents XBB.1.5 and all its descendants (lineages which have evolved from XBB.1.5). Right now, there's not a way to query this information on the API (yet), so we do a front-end lookup to lookup the sublineages associated with a small set of curated lineages. The front-end searches in
CURATED_LINEAGES
if there's a match, and then translates the name and query to be aOR
query of all the sublineages.This works, but should not be applied when the user asks explicitly for just that lineage.
For testing
I would use BQ.1 (1 lineage) vs. BQ.1* (should be ~ 80 lineages)