Deep Copy

[jburel]

Iain and michael came to office today to report a problem with measurement tool.
Iain described his workflow. The "copy" functionality seems to be misleading, at least the name. Saying that we could not find a better name.

Many people seem to expect a deep copy of the images.
Entries in the DB should be copied (how much still to define), raw data not so the user does not increase the size of disk (volume on disk reported as an issue).
These will have some implications e.g. delete.

[wmoore]

The same issue applies when moving data between groups too: ​https://www.openmicroscopy.org/community/viewtopic.php?f=4&t=3123

[pwalczysko]

This issue has been reiterated many times (lately spli, rleigh, pwalczysko)
As deep changes would be too laborious, I would suggest to avoid the confusion for the users.
These changes do not need to be concerned about permissions, nor do they seem too complicated to me:

A) do not highlight "Copy" in the menu when a Cut action is being performed - in case orphaned entity is being "copied" - grey Copy out, enable Cut

B) when deleting a "copied" entity, put into the warning "do you want to Delete ?" dialog a short sentence explaining that you are deleting ALL the "copies"

[pwalczysko]

Bug is listed in ​https://docs.google.com/folder/d/0B0o63qHVjgTQU2lydkl4UEhlbms/edit?docId=1s58QoESMLP88vC1kgqe3C9cPza-d66Zmqei0_1Lh8zo.

[jburel]

This is a big question. Josh, Gus and J-M discussed a possible solution. More to come later. Removing from the sprint

[jamoore]

This seems to be a possible candidate for 4.4.8, also useful for 5.0 work. Pushing.