In the brave new world of Legolas schemas for annotations, the annotations table is only required to have recording, id, and span columns. Previous iterations of Beacon's annotation format also had a value field, but that's no longer universally true. The current export code fails on those tables (where the relevant "value" information is recorded in a field with a different name). I think what we should do is
Implement a schema for EDF annotations as generated during import
Implement a schema for the minimum fields required for export, and validate the input annotations during export.
From a very quick perusal of the code, the same schema could be used for both (the import puts the the zero or more strings in .annotations field of the EDF annotation into the value field of one or more Onda.Annotations), so we could define
In the brave new world of Legolas schemas for annotations, the annotations table is only required to have
recording,id, andspancolumns. Previous iterations of Beacon's annotation format also had avaluefield, but that's no longer universally true. The current export code fails on those tables (where the relevant "value" information is recorded in a field with a different name). I think what we should do isFrom a very quick perusal of the code, the same schema could be used for both (the import puts the the zero or more strings in
.annotationsfield of the EDF annotation into thevaluefield of one or moreOnda.Annotations), so we could define