Store a copy of our mapping database
Migrated from GitLab #10
Over the years we have picked up an interesting set of transcript mappings, including mappings for transcripts no longer available from major database sources. When setting up a new server (or restoring a crashed one...), we always take care to not start from scratch, but instead use this existing mapping database.
Perhaps we should (and/or):
- Make our mapping database available as a download
- Automate creating this download
- Automate importing this download
Should this be a raw SQL dump? Then it's not database agnostic. Should we invent our own format? Just simple CSV?