Is your suggestion related to a problem to be solved?
We need an upgrade method, eventually callable via the CLI, to perform an annotation upgrade, or a full upgrade (assembly and annotation), e.g. current version of Sci-ModoM relies on Ensembl 110, while Ensembl is at 113 (October 2024). This is not something we want to perform regularly, but will be needed sooner or later.
This is currently only relevant for Ensembl:
depending on #149 this may have to be generalized
we need to consider #146.
A concise description of your feature request.
See Database upgrade for some ideas. An upgrade method could take an Ensembl version/release number, check the Ensembl.RELEASE for consistency, and perform some validation before running the upgrade. We should integrate that with a backup/failsafe solution in case the upgrade fails (data files and database).
Is your suggestion related to a problem to be solved?
We need an upgrade method, eventually callable via the CLI, to perform an annotation upgrade, or a full upgrade (assembly and annotation), e.g. current version of Sci-ModoM relies on Ensembl 110, while Ensembl is at 113 (October 2024). This is not something we want to perform regularly, but will be needed sooner or later.
This is currently only relevant for Ensembl:
A concise description of your feature request.
See Database upgrade for some ideas. An upgrade method could take an Ensembl version/release number, check the
Ensembl.RELEASEfor consistency, and perform some validation before running the upgrade. We should integrate that with a backup/failsafe solution in case the upgrade fails (data files and database).