Part of the NDI-matlab did2 migration. Target branch: Vnext.
Scope
Mirror of issue 6 for writes. If a customer modifies a legacy alias (e.g., doc.document_properties.probe_location.ontology_name = 'x') and then writes the doc, the modified legacy value must propagate to the V_delta canonical field before the doc hits the database layer.
- Before handing the struct off to
ndi.database.add/update, walk the alias table from issue 5.
- For each row, compare the legacy value to the V_delta canonical. If they differ, treat legacy as authoritative — the customer modified it — and copy back to V_delta.
- Strip legacy alias fields from the serialized form so only V_delta hits storage.
- Apply the same logic for
depends_on(k).id → depends_on(k).value.
- Idempotent.
Out of scope
Read-side (issue 6).
Dependencies
Issue 6 (read-side present so legacy aliases exist on the struct).
Part of the NDI-matlab did2 migration. Target branch:
Vnext.Scope
Mirror of issue 6 for writes. If a customer modifies a legacy alias (e.g.,
doc.document_properties.probe_location.ontology_name = 'x') and then writes the doc, the modified legacy value must propagate to the V_delta canonical field before the doc hits the database layer.ndi.database.add/update, walk the alias table from issue 5.depends_on(k).id→depends_on(k).value.Out of scope
Read-side (issue 6).
Dependencies
Issue 6 (read-side present so legacy aliases exist on the struct).