User Story #3532 (closed)
|Reported by:||jamoore||Owned by:||jamoore|
|Total Remaining Time:||0.0d||Estimated Remaining Time:||n.a.|
Description (last modified by jmoore)
Needed for working with the group permissions system (#1434)
The chgrp functionality will work similar to the delete functionality (#2615 - phase 1 / #2911 - phase 2) in that graph specfications like "/Image" or "/Annotation" along with an option map will be used to specify the starting point of the modification as well as what should happen when certain boundary conditions are reach. For example, what happens to an annotation which is attached to a chgrp'ed object if that annotation is also attached to another object that would be chgrp'ed.
Invocation is also expected to be asynchronous as with delete since calling chgrp on a larger hierarchy could take many minutes. The delete API may be refactored so that the same callback classes can be used in both cases.
- #2997 - other's users annotations are not deleted.
Change History (9)
comment:2 Changed 10 years ago by jmoore
- Keywords paris2011 added
- Milestone changed from Unscheduled to OMERO-Beta4.3.2
comment:7 Changed 9 years ago by jmoore
- Resolution set to fixed
- Status changed from accepted to closed