ESAP database changes
(https://support.astron.nl/jira/browse/SDC-390)
The ESAP datamodel is still in its orignal form when not everything about the functionality was clear. I would like to make the following changes for various reasons:
datamodel (database structure):
- add a 'visibility' field to datasets. To be able to control where in the GUI they should show up. (this is needed when we split up the IVOA service in multiple services, where one of them should only be visible in 'multi-query' and not in the main archive screen.
- remove the 'catalog.protocol' field. (not used).
- remove the 'catalog.equinox' field. (not used).
configuration (database content): This has caused confusion when people accidentally started to change 'vo.py' becuase they thought that was the ivoa service connector.
- rename vo.py => astron_vo.py
- rename vo_reg.py => ivoa.py
- rename alta.py => apertif.py
This does not only affect the database, but also means renaming the service connectors in the backend.
Migrate and dump: When these changes are made, the database should be migrated and new yaml files should be dumped. See: https://git.astron.nl/astron-sdc/esap-api-gateway/-/wikis/ESAP-databases
Document: Update the datamodel diagram and a copy here: https://git.astron.nl/astron-sdc/esap-api-gateway/-/wikis/ESAP-databases
Communicate: Announce that this will happen, and has happened, because the next version of ESAP-API will not be compatible with the already installed databases. So everybody who has a local copy of ESAP running has to recreate their esap_config.sqlite3 database from the yaml file.