Detailed Description

• RemoteAttachments.delete_attachment
  • Backend needs to respect missing attachments in updatePartial call
    • ensure frontend or older libs versions don’t already skip the attachments?
    • ensure libs don’t drop attachments on updates when opened via zarr streaming?
    • possibility to rename attachments?
• RemoteDataset.add_layer_as_ref (linked layer)
  • Needs new protocol similar to compose (ensure permission checks)
  • Note: if user permissions for target dataset is revoked, they can still access it in this way! How to restrict?
• RemoteLayer.add_mag_as_ref (linked mag)
  • Same as above
• RemoteAttachments.add_attachments_as_ref
  • Same as above
• RemoteLayer.add_mag_as_copy with transfer_mode=HTTP
  • Needs new upload protocol. Use resumable here too?
• RemoteAttachments.add_attachment_as_copy with transfer_mode=HTTP
  • Needs new upload protocol (analog to mag)
• Actual editing of the existing data?
  • libs-only (only for RemoteAccessMode.DIRECT_PATH)

Context

Remote datasets should have the same flexibility as datasets stored in the binaryData folder with disk access.