Florian M

note to self: note to self, open questions: - remove downsample feature? → yes - duplicate history? - duplicate update actions (needed for merging editable mappings) - duplicate v0 in...

> or at least a parameter / property of the updateMappingName like makeMappingEditable or isMappingEditable? Yes, such an extra property is required! It’s called isEditable. For this particular context, both...

@MichaelBuessemeyer the backend should be ready for review. I’ll continue by building the FossilDB migration, this will occupy me for some time. I’d suggest to first finish the frontend here...

You’re right, I’ll add that! I didn’t even remember that the time tracking api includes the stats :sweat_smile:

@normanrz the migration should be ready for a first review round. Could you please have a look at the code in `tools/migration-unified-annotation-versioning`?

Thanks a lot for the thorough review @MichaelBuessemeyer ! You definitely found some bugs that would have caused headaches later! I tried to answer your questions and address the feedback....

Thanks for your testing! > Is it correct, that t in case an annotation is merged with another and both modified the same bucket, that one bucket takes precedence and...

quoting michael from [above](https://github.com/scalableminds/webknossos/pull/7917#pullrequestreview-2533889481): > preview the version where the agglomerate mapping was activated -> The frontend crashed due to the unexpected server 400 error. I think this is a...

ping :) I hope I fixed those problems in [51839f0](https://github.com/scalableminds/webknossos/pull/7917/commits/51839f041753392e0e8fcf2082c53beddbd94825)

The user-friendliest option would be to disable the button in case of zero finished matching annotations, and add a tooltip. However, adding this count to the task type list would...