Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
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 #394 (closed)

Opened 18 years ago

Closed 14 years ago

Provide high-level permissions interface

Reported by: jamoore Owned by: jamoore
Priority: minor Milestone: OMERO-Beta4.2
Component: API Keywords: n.a.
Cc: Story Points: n.a.
Sprint: n.a. Importance: n.a.
Total Remaining Time: n.a. Estimated Remaining Time: n.a.

Description

After a discussion on #374, it was seen as generally useful and A Good Thing to design and implement a higher-level permissions api (for lack of a better name, IPermissions) which makes semi-recursive changes. "Semi-recursive" here means that a conditional graph-walk is performed, in which not all items are modified. For example:

  Image i = new Image( 1L, false );
  IPermissions permsService = serviceFactory.getPermissionsService();
  permsService.modifyImageGraph( i, Permissions.READ_ONLY );

Which would update:

  • Image
  • Pixels
  • Channels
  • Stats

but perhaps not:

  • ImageAnnotations
  • ...

The conditionals for the graph-walk should most likely be configurable. So called "Profiles" represent another ticket that should also be filed (under the to-be-created "MushroomCloud?" milestone).

Change History (1)

comment:1 Changed 14 years ago by jmoore

  • Milestone changed from GatherReqs to OMERO-Beta4.2
  • Resolution set to fixed
  • Status changed from new to closed

This seems to be eclipsed by the group permissions work in #1434.

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.71490 sec.)

We're Hiring!