Changes between Initial Version and Version 1 of Permissions


Ignore:
Timestamp:
Mar 24, 2009, 10:01:29 PM (15 years ago)
Author:
simonp
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Permissions

    v1 v1  
     1= Proposal number : ? Proposal title : Permissions Changes - Editing and Ownership =
     2
     3|| '''Date''' || 2009/03/23 ||
     4|| '''Contact(s)''' || Simon Pigot ||
     5|| '''Last edited''' || [[Timestamp]] ||
     6|| '''Status''' || draft - complete in BlueNetMEST sandbox ||
     7|| '''Assigned to release''' || 2.4 ||
     8|| '''Resources''' || Available ||
     9
     10== Overview ==
     11
     12As of 2.2 Editing rights were removed and bundled with ownership. For many workflows (the majority perhaps) this means that ownership must be transferred by a user-admin or above in order for any other user (even one in the same group) to be able to edit the record. In addition, the transfer ownership (prior to the implementation of the massive new owner operation - see [wiki:MoreMassiveOperations]) operation could only transfer all records belonging to one user to another.
     13
     14Restoration of editing rights also means that they must be included in the database setup, privileges screens and users who have editing rights must see 'Create' and 'Edit' buttons not just 'Create'.
     15
     16It was also not clear when a registered user was viewing the summary of records returned from a search:
     17
     18 * who owns the record
     19 * what categories it belongs too and what the privileges are on the record.
     20
     21It is proposed that the summary of records returned by a search should show:
     22
     23 * who the owner is
     24 * privileges and categories buttons (clicking on the button will show details but only the owner of the record can change them - they are disabled for everyone else)
     25
     26A light-weight alternative to this is may be to show a visual indicator of whether the current user is the owner or not (eg. using the lock-unlock icons) and whether the record is published to all/intranet/internal (using a green/orange/red traffic light signal).
     27
     28=== Proposal Type ===
     29 * '''Type''': User interface and core functionality additions
     30 * '''App''': !GeoNetwork
     31 * '''Module''': Metadata XSLTs, Datamanager (add some additional fields to geonet:info)
     32
     33=== Links ===
     34 * This has been available in the BlueNetMEST sandbox for some time - tested by users in the !BlueNet project
     35
     36=== Voting History ===
     37 * None yet
     38
     39----
     40
     41== Motivations ==
     42
     43Workflow impaired by bundling editing rights with ownership.
     44
     45Permissions and ownership should be visible to registered users who have view/publish rights on a record. This is analogus to a filesystem where if a user can see a file then they can see the permissions on that file and who owns it.
     46
     47== Proposal ==
     48
     49See overview.
     50
     51=== Backwards Compatibility Issues ===
     52
     53Reintroduction of editing rights to the !OperationsAllowed table means that existing 2.2 installations will need to modify this table by hand.
     54
     55== Risks ==
     56
     57== Participants ==
     58 * As above
     59