For proper logging (see #56), more tables should have a "note" field.
Notes, as plain-text strings, are highly repetitive ("imported from MLWH on xxx"), and use up a lot of DB storage (which also tends to slow down DB systems).
Additionally, notes should be more machine-readable than a plain-text string.
I am currently testing/converting an altered SQL schema in FITS (production) that has a new table note, with source, rationale, and day field. Tables with (meta-)data get an additional "note_id" field (default:null).
I am also altering relevant views to show both the note field, and the additional information from the note table, where available.
I am also converting some notes into the new format, to test the system.
I am also preparing C++ code in a new branch to support this.
For proper logging (see #56), more tables should have a "note" field. Notes, as plain-text strings, are highly repetitive ("imported from MLWH on xxx"), and use up a lot of DB storage (which also tends to slow down DB systems). Additionally, notes should be more machine-readable than a plain-text string.
I am currently testing/converting an altered SQL schema in FITS (production) that has a new table
note
, withsource
,rationale
, andday
field. Tables with (meta-)data get an additional "note_id" field (default:null).I am also altering relevant views to show both the
note
field, and the additional information from thenote
table, where available.I am also converting some notes into the new format, to test the system.
I am also preparing C++ code in a new branch to support this.