Consolidate Reconstructions into Single Table #69
Description
Currently reconstructions are being held in 2 tables, and have unique IDs, one for wire recons and one for mask recons.
After viewing this design, it's been decided it is more intuitive for the user to have both of these in the same table for views.
This brings on several implications:
- Having unique IDs for both types of reconstructions
- Logic to handle errors when incorrect reconstructions are attempted on incompatible scan types
- Handling how indexing reads branch depending on type of reconstruction
It would best to also combine the tables in the backend, not just the views because of the first requirement.
To do so the standard design would be to have a singular reconstruction table with shared fields, then sub-tables with unique fields for each type of reconstruction.
This is a large refactor that will impact many parts of the program.