We have some LAPIS instances that are backed by a Loculus instance. The ingress potentially generates new versions (revisions) of some accessions. We need to make sure that we filter out non-latest versions properly:
Either by setting LAPIS filters accordingly
Advantage: Easy to implement
Disadvantage: All users of the LAPIS instances need to be aware that this is necessary.
Or by filtering out non-latest versions before they get into SILO
Advantage: client-friendly - no user needs to think about Loculus interna (which we actually want to hide)
Disadvantage: maybe a bit tedious in implementation, as we need to modify the link between Loculus backend and SILO preprocessing.
We have some LAPIS instances that are backed by a Loculus instance. The ingress potentially generates new versions (revisions) of some accessions. We need to make sure that we filter out non-latest versions properly: