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.
- Timestamp:
-
02/04/10 10:12:54 (14 years ago)
- Author:
-
jmoore
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v3
|
v4
|
|
3 | 3 | A system or group administrator who views or attempts to annotate data belonging in a private or non-member group may break group-based security settings for the owner. |
4 | 4 | |
5 | | Options: |
| 5 | == Options: == |
| 6 | |
6 | 7 | * make objects belong to admins public |
| 8 | * '''-1''' since objects would appear as ''disembodied hands'' for non-owners. |
7 | 9 | * make annotations/rendering settings/thumbnails belong to the owner (or the group in the case of a shared group which the admin is not a member of)) |
| 10 | * '''-1''' since objects would suddenly appear to the owner as his/her own. |
8 | 11 | * make the session read-only (with special handling for rendering settings and thumbnails) |
| 12 | * '''?''' |
9 | 13 | * add a flag or other marker to allow user-reading of such data. |
| 14 | * Dicussion: an "`AsAdmin`" flag would mark any object which was created via admin privilege, so that when a PI annotates in a shared group, there is no flag but in a private group, there is. Then if the PI-user is removed as an owner or the admin is removed from the "system" group, the object would still be marked as special. |
| 15 | * Would need special handling on down- (and up-?) grades of permissions. |
| 16 | * Is this identical to making public above? |
10 | 17 | * ??? |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.13036 sec.)