Description
Some past issues have arisen because of a mismatch between the assembly version and annotation and genetic map intervals that are assumed to belong on a specific assembly version (see #719 and #1252).
In addition to the existing patches (modify intervals on the fly if they over-extend), One solution for new additions is to create checks that assemblies match either by adding and assembly_name attribute to annotations and genetic maps (see #1650), or perhaps by parsing the file name of those resources, which by convention include the assembly name.
Adding one of these should alert anyone contributing to the catalogue to verify the assemblies match (and perhaps formally as part of QC), while also warning users if/when they've loaded mismatching versions.
As discussed in #1650, we have opted to not work on this until some time after the 0.2.1 version release.