Changes between Version 25 and Version 26 of NextforHMS


Ignore:
Timestamp:
01/28/10 23:31:36 (12 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • NextforHMS

    v25 v26  
    4545 * Options to create additional groups that have add/edit/update/delete access to each individual registry - and bundle people that way.  e.g. Tim has write privileges to OR and PR but not HMS or RMS; Praneeth has write privileges to RMS but nothing else; Dan has write privileges to RMS, OR, and PR but not HMS. [[BR]]
    4646
    47  * Added the following roles (auth.group):
     47 * Add Link to Bed Capacity, Services, Shortages, Contacts to main ADD Hospital form @ /hms/hospital/create
     48
     49'''Notes from dzubey'''
     50
     51>> Need to establish who are our user groups? Then based on that what rights should they NOT have.
     52> * nursix says: I added the following roles (auth.group):
    4853
    4954   ||'''Role'''||'''proposed for'''||
     
    5459   ||HMSAdmin||access to everything in HMS||
    5560
    56  * Add Link to Bed Capacity, Services, Shortages, Contacts to main ADD Hospital form @ /hms/hospital/create
     61>> If the main concern is keeping certain data away from the general public, and we are time crunched, then a generic anonymous / read-only / read-write structure is fine...but this makes it very hard to change in the future.
    5762
    58 '''Notes from dzubey'''
     63>> There is an more optimal method of assigning flags to users, which indicate what capabilities they are allowed, as opposed to role-based (nursix thinks: role-based ACL is a proven good solution, implemented by the web2py framework, so nothing we have to develop, and you can always add one "role" per user and thus establish an individual ACL)
    5964
    60  - Need to establish who are our user groups? Then based on that what rights should they NOT have.
    61  - If the main concern is keeping certain data away from the general public, and we are time crunched, then a generic anonymous / read-only / read-write structure is fine...but this makes it very hard to change in the future.
    62 
    63  - There is an more optimal method of assigning flags to users, which indicate what capabilities they are allowed, as opposed to role-based (nursix thinks: role-based ACL is a proven good solution, implemented by the web2py framework, so nothing we have to develop, and you can always add one "role" per user and thus establish an individual ACL)
    64 
    65  - we've already leaked a good quantity of data to various search engines and blogs and whatnot. I imagine this current push is to secure future data we capture.
     65>> we've already leaked a good quantity of data to various search engines and blogs and whatnot. I imagine this current push is to secure future data we capture.
    6666----
    6767==== Accepted ====