Changes between Version 22 and Version 23 of NextforHMS


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

--

Legend:

Unmodified
Added
Removed
Modified
  • NextforHMS

    v22 v23  
    3737==== Feedback/Question/Discussion ====
    3838
    39 * '''Security''' - enable role management - this is an urgent requirement assigned to sysadmin team: Praneeth (lead), Tim & Dan.  Need written recommendation sent to mark by e-mail by 1600Z on 28 January 2010; meeting in #sahana-py at 1700Z on 28 January.  Background: security for personnel on ground makes it inadvisable to publish publicly the needs and fulfillment information that might be embedded in the HMS - i.e. publishing that medical supplies are to be delivered to this place at this time might put the shipment and relief workers lives at risk.  We need a plan to implement role-based access to different Sahana libraries. I need the sysadmin team to advise which of the following requirements is possible to do through front-end configuration of SahanaPy security settings (preferred) and which will require coding changes (not preferred).  Alternatives are welcome.  The team should also evaluate and advise on the impact shutting down read-only public access to parts of sahana will have on our feeds of data on hospital locations and hospital management data.  Requirements:
    40   * Public/anonymous access:  Read only access to OR, RMS Twitter and 4636 Messages. 
    41      * Option to make HMS hospitals feed with location and general information - but not the shortages table - publicly available
    42      * Can we hide individual fields (like beds available, security status, facility status) from public view without code changes?
    43   * Registered users:  Read only access to entire system (adding PR and HMS / HMS shortages)
    44   * Entry users: Registered users who are given add/edit/update/delete access to OR, PR, HMS
    45   * 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]]
     39 * '''Security''' - enable role management - this is an urgent requirement assigned to sysadmin team: Praneeth (lead), Tim & Dan.  Need written recommendation sent to mark by e-mail by 1600Z on 28 January 2010; meeting in #sahana-py at 1700Z on 28 January.  Background: security for personnel on ground makes it inadvisable to publish publicly the needs and fulfillment information that might be embedded in the HMS - i.e. publishing that medical supplies are to be delivered to this place at this time might put the shipment and relief workers lives at risk.  We need a plan to implement role-based access to different Sahana libraries. I need the sysadmin team to advise which of the following requirements is possible to do through front-end configuration of SahanaPy security settings (preferred) and which will require coding changes (not preferred).  Alternatives are welcome.  The team should also evaluate and advise on the impact shutting down read-only public access to parts of sahana will have on our feeds of data on hospital locations and hospital management data.  Requirements:
     40 * Public/anonymous access:  Read only access to OR, RMS Twitter and 4636 Messages. 
     41   * Option to make HMS hospitals feed with location and general information - but not the shortages table - publicly available
     42   * Can we hide individual fields (like beds available, security status, facility status) from public view without code changes?
     43 * Registered users:  Read only access to entire system (adding PR and HMS / HMS shortages)
     44 * Entry users: Registered users who are given add/edit/update/delete access to OR, PR, HMS
     45 * 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 * Add Link to Bed Capacity, Services, Shortages, Contacts to main ADD Hospital form @ /hms/hospital/create
     47 * Add Link to Bed Capacity, Services, Shortages, Contacts to main ADD Hospital form @ /hms/hospital/create
    4848
    4949'''Notes from dzubey'''
     
    5858==== Accepted ====
    5959
    60  * For RMS - additional fields needed:
    61   * Tick-box - "For Further Review" - this will tag a request as needing review by SOUTHCOM - based on current set of daily priorities - they will want to see a list of those items marked "For Further Review" and will manually want to validate the information as actionable.
    62   * Tick-box - "Validated" - once a request marked "For further review" has been validated, this will be used to identify validated actionable requests for immediate tasking by SOUTHCOM
    6360
    6461 * '''Provenance of data''' - without adding any fields (at this time), we need to display the last time data records were updated and by whom - we should be able to pull from the last modified column and the registered user who made the modification.  This is especially important to allow for evaluation of how old data is and how often it is being updated.  Maybe a big bold splash on upper right when viewing a hospital record would say "Last modified on DDMMYY at HH:MM UTC by <Registered User>".  Or just show the data as additional field in form view or column in table view.
     
    7471----
    7572==== In Progress ====
     73
     74 * For RMS - additional fields needed:
     75  * Tick-box - "For Further Review" - this will tag a request as needing review by SOUTHCOM - based on current set of daily priorities - they will want to see a list of those items marked "For Further Review" and will manually want to validate the information as actionable.
     76  * Tick-box - "Validated" - once a request marked "For further review" has been validated, this will be used to identify validated actionable requests for immediate tasking by SOUTHCOM
    7677
    7778----