We need to settle on metadata for the calibrations we have ingested for the EVLA.
| Column Name | Column Type | Comments |
|---|---|---|
| calibration_id | integer | Automatically generated unique Id |
| casa_version | varchar | Which version of CASA was used. This potentially has several effects, including restores. |
| parallelized_casa | boolean | Was CASA used in MPI mode? That has implications for how the calibration information is stored. |
| date_ingested | datetime | When the calibration ingestion was performed. |
| qa_comments | varchar | Comments provided by the DA upon Ingestion. Optionally, this could be replaced with a workflow_id if the comments are stored there. |
I've removed the reference to a particular EB (That's far too EVLA specific for what we need). Instead, I suspect we'll need linking tables into our processing structure (see: here).