Changes between Version 18 and Version 19 of BluePrint/Requests


Ignore:
Timestamp:
03/28/11 03:59:44 (10 years ago)
Author:
Michael Howden
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Requests

    v18 v19  
    11[[TOC]]
    2 = Blueprint for the Request Management Module =
    3 We need to be able to track Requests for Aid & their Fulfilment.
     2= Blue Print - Requests =
    43
    5 == Components ==
    6  * pe_group/Req ('Community' or 'Family')
    7  * Shelter/Req
    8  * Hospital/Req
    9  * Organisation/Req
    10  * Office/Req <- can be used for internal requests, like IT/Stock Requests?
     4== Introduction ==
     5Sahana Eden needs to be able to manage requests for:
     6 * Items (Supplies)
     7 * Assets
     8 * People
    119
    12 == Roles ==
    13  * Pledger marks status as 'Delivered' - pseudo role or onvalidation?
    14  * Requestor marks status as 'Received' - pseudo role or onvalidation?
    15  * Want Sync strategy for this
     10This requires tracking requests, commitments to fulfil requests and the final fulfilment of requests.
    1611
    17 == Issues ==
    18  * Structured into category/subcategory (like Vol Skills widget?)
    19  * Link RMS to Inventory (Warehouse)
    20  * Separate Line Items in Single Req (like PR)
    21    * => Header info entered once :)
    22    * Pledges match line items (like PO)
    23  * RMS Timetable options?
     12== Current Status ==
     13
     14=== To Do ===
     15 * Adjust the commit button so that it only appears for un-fulfiled commitments
     16 * Create a better work-flow link from Req -> Commit -> Send -> Recv
     17  * Disable a single commitment to sent multiple times
     18 * Functionality to show requests which can be fulfilled by the items in a inventory (and perhaps visa versa).
     19 * Ensure that only one packet per item can have a quantity = 1 (and thus be the unit of measure for that item)
     20 * Request Timetable options?
    2421  * 'Immediate'
     22 * Autofill requester Name
     23 * For Shelters #families/#people => Auto Calculate Food/Water/Shelter for simplified reqs
    2524
    26 == Shelter Management/Needs assessment ==
    27  * #families/#people => Food/Water/Shelter needs for simplified RMS reqs
    28 
    29 Haiti Requirements:
    30  * [wiki:HaitiRMSToDo HaitiRMSToDo]
    31 
    32 User Guide for old PHP system:
    33  * http://wiki.sahanafoundation.org/doku.php?id=doc:rms:english
    34 
    35 Wireframes for a proposed system for Nashville Floods:
    36  * http://bit.ly/9UW0tA
    37 
    38 == Usability suggestions for Pakistan Version ==
    39  * [wiki:Pakistan]
    40 
    41  *  Home http://test.eden.sahanafoundation.org/eden/rms/index seems not necessary since the sub menu is quite clear to navigate.
    42 
    43  * Submenu name should be consistent with the link page
    44    * ~~Use "Pledge Aid" instead "View request & Pledge aid"~~
    45    * ~~Use "Pledge" instead "View & edit pledge". “List” & “Add” are two submenu under pledge.~~
    46 
    47  * Add Aid Request
    48    * ~~Requester data should be put on the most top~~
    49    * ~~Request type, date/time should be required~~
    50    * Location/shelter name of requester should be required.
    51       * ((Suggestion))If only existing shelter/organization can make request, then move out country/province/district/town/village.
    52       * ((Suggestion)) is better for usability (more clear) and makes the process easier. Pushing requesters to register in db before making request is also good for relief statistics work.
    53       * If ((Suggestion)) is developed, then the address for shelter/org will be required. And put existing org dropdown on this page.
    54       * If ((Suggestion)) is developed, make either shelter or org is required when make a request.
    55       * If ((Suggestion)) is not developed, check that is address for a requester which is not existing shelter necessary for delivery?
    56    * Is reference doc necessary for aid request? If not, move it out.
    57  
    58  * List Aid Requests
    59    * ~~Message “Click on an ID in the left-hand column to make a Pledge to match a request for aid.” Should be modified to fit the real interface, like:” Click on “Pledge” button in the left-hand column to make a Pledge to match a request for aid.~~
    60    * Add a “search” button instead of press enter tab
    61 
    62  * Pledge a request 
    63    * Request type and data of requester should be put in the “Aid Request Details” section top of the page.
    64    * All columns should be required.
    65    * Add comments column to the pledges table.. http://test.eden.sahanafoundation.org/eden/rms/req/9/pledge
    66    * Use “Pledge This Request” instead  “Add New Pledge”
    67    * Use “List pledges for this request” instead “list pledge” which points to “all pledges” in this module
    68    * Consider to add pledge type(same as request type) which may make the process easier and the message more clear.
    69    * Location map problem, see ticket: #514
    70 
    71  * List pledges http://test.eden.sahanafoundation.org/eden/rms/pledge
    72    * Since there’s some space on the page, try to add message column on the page.
    73    * Use “edit” instead of “open” for each pledge since it’s editable not only browse. And users do edit status.
    74    * Add a “search” button instead of press enter tab.
    75    * Search is not working , see ticket #512
    76    * Move Page no. button to be closed to pledge table.
    77 
    78  * Edit pledge
    79    * ~~Delete function is not working , see ticket~~: #513
    80    * Delete is not necessary since status “canceled” is there.
    81 
    82  * Add pledge
    83    * All columns should be required.
    84    * Pledge type should be necessary for this process.
    85 
    86 ----
    87 BluePrints
     25== Also See ==
     26 * UserGuidelines/Logistics
     27=== Other Requirements ===
     28 * HaitiRMSToDo
     29 * User Guide for Sahana Agasti: http://wiki.sahanafoundation.org/doku.php?id=doc:rms:english
     30 * Wireframes for a proposed system for Nashville Floods: http://bit.ly/9UW0tA