Separate Dataset Storage from Display

[fm3]

Dataset registry should not happen primarily on disk. Imported remote datasets should not be represented on disk, but only in the db. Layers can be should be shared between datasets. compare https://www.notion.so/scalableminds/Design-Doc-Dataset-Management-b9c5dbabb7bf4bbba528ef3f68fe97b0

• [ ] Backend
  • [ ] Standard dataset routes by id
  • [ ] Disambiguation route for datasets by name and orga (use oldest if multiple)
  • [ ] SQL schema for layers with key
  • [ ] store paths to mesh files etc in postgres
  • [ ] credentials instances
  • [ ] migration to unify existing multiply used layers
  • [ ] names need not be unique anymore
• [ ] Frontend
  • [ ] edit view should use updated routes
  • [ ] options to create new datasts from the layers of existing ones
• [ ] Libs/worker
  • [ ] Add virtual dataset read support in libs (paths per layer from webKnossos)
  • [ ] Add virtual dataset create support in libs
  • [ ] Adapt jobs that create copies of datasets to create virtual datasets