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.

Changes between Version 20 and Version 21 of Ticket #1434


Ignore:
Timestamp:
01/22/10 11:12:35 (14 years ago)
Author:
jmoore
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1434 – Description

    v20 v21  
    1 = Server changes phase 1: = 
     1This ticket is the story umbrella for all the permissions improvements planned for milestone:OMERO-Beta4.2 in order to re-activate group-sharing. Linked tickets are available under [WorkPlan/Permissions] 
    22 
    3  * Add "private/public" to EventContext 
    4  * choice to make groups public on creation? cF. ticket:1204 (essentially re-opening that ticket) 
    5  * All new objects are created in current group (warning/exception on explicit) with proper permissions for group 
    6  * All linked objects are checked for group (warning/exception on mixed group and/or mixed permissions) 
    7  * No object can be linked to an object of another group, regardless of permissions. 
    8  * All returned graphs are group-consistent, i.e. consist only of objects from a single group (with the exception of system types) 
    9  * Admin method to make group public (sends email) 
    10  * Prevent changing groups to "755" except through API! 
    11  * Check interaction with runAsAdmin & privileged-tokens. (ie. which has the highest priority) 
    12  * what happens to root/admin data when linked? automatically put in a matching group since root/admin will be able to read it? 
    13  * #1310 setGroup 
    14  * #320 changeGroup 
     3=== Items under discussion === 
    154 
    16 = Upgrade: = 
     5The following items are '''not''' listed on the WorkPlan page. If they are deemed important for 4.2, they should be moved there. If not, they should either be deleted or moved to their own tickets. 
    176 
    18  * Make all groups private (currently rw-r-r) 
    19  * Detect if any data is in a mixed graph and raise exception 
    20  * Make all group data private (enums?) 
    21  
    22 = Possible changes: = 
    23  
    24  * Enumerations made global 
    25  * IAdmin limits each user to a single group (?) 
    26  * Remove "default" group 
    27  * "user" group becomes the "user private space" 
    28  * thumbnails, annotation links, etc. become a new type of object: 
    29    "shared" (or similar) which don't prevent delete. 
     7 * thumbnails, annotation links, etc. become a new type of object: "shared" (or similar) which don't prevent delete. 
    308 * In some cases, automatically convert object's group to the attached to object? (From #1171, is this necessary if other groups are not visible?) 
    31  
    32 = Gui changes: = 
    33  
    34  * "Move Y to group" - like the deleteY() methods, this would move an 
    35    entire graph to a user's "group space". There may need to be some 
    36    duplicating of tags, etc. 
    37  
    38  * Login option: "private space" or "group space" 
    39  
    40  
    41 = Rollback: = 
    42  * #337 (remove locking) 
    43  * #1405 (remove configurable default perms) 
    44  * possibly #1204 (make group global) 
    45  * possibly #307 (remove 'soft' perms) 
    469 
    4710---- 

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

We're Hiring!