Task #1992 (closed)
Move to READ-ONLY / READ-LINK rather than READ-WRITE
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | n.a. | Milestone: | OMERO-Beta4.2 |
Component: | n.a. | Version: | n.a. |
Keywords: | n.a. | Cc: | jburel, wmoore |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | 2010-03-19 (5) |
Description
See #1929 and insight#1212
Definitions
- READ-ONLY: no modifications, deletions, or linking to other users data
- READ-LINK: no modifying or deleting other users data, but linking is allowed
- READ-WRITE: link to and edit other users data (similar to group-ownership, but without permissions for adding/removing users, etc.)
Discussion
User feedback from #1929 points toward READ-WRITE being too open a permission setting. Currently (Sprint 4) the server implements rwr--- as READ-LINK and rwrw-- as READ-WRITE. Clients are implementing rwr--- as READ-ONLY and rwrw--- as READ-WRITE. If the server moves to READ-ONLY and READ-LINK, then clients CAN but won't have to enforce the READ-ONLY setting.
Change History (4)
comment:1 Changed 14 years ago by jmoore
- Status changed from new to assigned
comment:2 Changed 14 years ago by jmoore
comment:3 Changed 14 years ago by jmoore
- Remaining Time changed from 1.5 to 0
- Resolution set to fixed
- Status changed from assigned to closed
r6342 implements this functionality.
(In [6343]) renaming exception to ReadOnlyGroupSecurityViolation? (incorrectly specified as #1922)