Annotation Layer Ordering is Inconsistent

[fm3]

The ordering of (volume) annotation layers is done in different ways in different scenarios:

• The frontend displays them in the order they appear in the annotationProto
• When adding a new layer, it is appended to the list in the annotationProto
• However, when fetching the annotation layers from the postgres database, this ordering is not available. There, the layers are ordered lexicographically by tracingId
• The ordering from the database is written to NML. On NML re-upload new IDs are handed out to the uploaded layers, but the ordering from the NML is used for proto.

Should be unified, so that adding layers and download + reupload should yield the same ordering. I’m not sure what’s the best way to solve this, and where a newly added layer should appear.

Note that the layer ordering also affects the initially visible layer (the first in the frontend’s list, apparently)

[philippotto]

I’m not sure what’s the best way to solve this, and where a newly added layer should appear.

I'd vote for lexicographic ordering (by tracing id), because it's very simple and only depends on the current tracing set. this gets us some determinism.

if we find this weird in the layers sidebar, we could still sort them there by name (would also affect the initially visible segmentation layer).