Inconsistent versions between application and Ensembl (genome browser)

[eboileau]

Aims/objectives.

What if we use e.g. Ensembl 110 (for sequence context, annotation in general such as features, gene assigment, and complementing RBP annotation) and link reported sites to Ensembl genome browser, which is likely to be a few versions above e.g. at the time of opening this issue it was 112.

A clear and concise description of todo items.

We will eventually have to consider database/application upgrade (and liftover), but we want to do that on a per-species basis only when absolutely required, e.g. when a new assembly is available. We could consider upgrading annotation only, but need to carefuly consider whether this is necessary, and how frequently, see also https://dieterich-lab.github.io/scimodom/database.html#annotation.

[CDieterich]

Dear @eboileau - there is a nice feature of EnsEMBL. They keep old releases on the archive site
with permanent links. see https://www.ensembl.org/Help/ArchiveList

[eboileau]

The archive service seems unstable... for instance https://jul2023.archive.ensembl.org does not work at the moment...

[eboileau]

I leave this open, this needs to be refactored. The version is hard coded separately in BE and FE. We need a single source, and this must match the assembly version set in the DB.