Fix importing a dataset from disk

[philippotto]

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• remove the datasource-properties.json for an existing dataset and reload the list in the dashboard
• try to import the dataset by using the inferred values from wk

Issues:

• fixes a regression introduced with Improve Zarr Import UI (and general editing of datasets) #6485

---

(Please delete unneeded items, merge only when none are left open)

• Updated (unreleased) changelog
• Updated (unreleased) migration guide if applicable
• Updated documentation if applicable
• Adapted wk-connect if datastore API changes
• Adapted wk-libs python client if relevant API parts change
• Needs datastore update after deployment
• Ready for review

[fm3]

I think you branched off of folders – could you cherry pick the relevant commit here? 😇

[philippotto]

I think you branched off of folders – could you cherry pick the relevant commit here? innocent

Argh, good catch. I didn't branch wrong, though. Instead, I pulled the folders branch into this branch 🤦

[daniel-wer]

Works as expected using the testing instructions 👍

Maybe unrelated, but I noticed that there is no field to enter the largestSegmentId for the dataset I tested this with (ROI2017_wkw), although it has a segmentation layer. Is this expected or a regression (from another PR)?

[philippotto]

Maybe unrelated, but I noticed that there is no field to enter the largestSegmentId for the dataset I tested this with (ROI2017_wkw), although it has a segmentation layer. Is this expected or a regression (from another PR)?

Good catch! I think, it's a regression from the same PR. I fixed it now :)

[daniel-wer]

LGTM 👍