Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

User Story #3532 (closed)

Opened 10 years ago

Closed 8 years ago

Implement chgrp

Reported by: jamoore Owned by: jamoore
Priority: blocker Milestone: OMERO-4.4
Component: Security Keywords: paris2011
Cc: jburel Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: 0.0d Estimated Remaining Time: n.a.

Description (last modified by jmoore)

Needed for working with the group permissions system (#1434)

Plan

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.

See:

  • #2997 - other's users annotations are not deleted.

Change History (9)

comment:1 Changed 10 years ago by cxallan

  • Milestone changed from OMERO-Beta4.3 to Unscheduled

comment:2 Changed 9 years ago by jmoore

  • Keywords paris2011 added
  • Milestone changed from Unscheduled to OMERO-Beta4.3.2

Adding to 4.3.2 per Paris 2011 Users' meeting.

comment:3 Changed 9 years ago by jmoore

  • Owner set to jmoore

comment:4 Changed 9 years ago by jmoore

  • Cc jburel added
  • Description modified (diff)

comment:5 Changed 9 years ago by agilo

  • Status changed from new to accepted

Updated status, related task in progress

comment:6 Changed 9 years ago by jburel

  • Milestone changed from OMERO-Beta4.3.2 to OME-5.0

comment:7 Changed 9 years ago by jmoore

  • Resolution set to fixed
  • Status changed from accepted to closed

All open tickets moved to #8099 (api v2) and #8100 (adv. impl) except for #6620 which needs to be reviewed. Closing this story since the branch has been merged in and everyone is actively using it.

comment:8 Changed 8 years ago by agilo

  • Status changed from closed to accepted

Updated status, related task in progress

comment:9 Changed 8 years ago by jburel

  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.104515 sec.)

We're Hiring!