Metadata for triggers and candidate events
The charge for O4 data product management states:
Metadata: We define metadata as a set of lightweight data products or links to data products associated with a given trigger. For example, lightweight data products such as the FAR and SNR or paths links to parameter estimation posteriors.
I think this can be accomplished with a new table that's linked with a 1:1 foreign key to a g-event. Also from the charge, a proposed format the metadata is below. Inserted as a screenshot since copy/paste from pdf totally gnarled up the formatting.
I think a first cut would involve taking advantage of postgres' json datatype.
Querying for metadata would have to be implemented too.