|Version 7 (modified by 13 years ago) ( diff ),|
Blueprint for the Request Management Module
We need to be able to track Requests for Aid & their Fulfilment.
- pe_group/Req ('Community' or 'Family')
- Office/Req <- can be used for internal requests, like IT/Stock Requests?
- Pledger marks status as 'Delivered' - pseudo role or onvalidation?
- Requestor marks status as 'Received' - pseudo role or onvalidation?
- Want Sync strategy for this
- Structured into category/subcategory (like Vol Skills widget?)
- Link RMS to Inventory (Warehouse)
- Separate Line Items in Single Req (like PR)
- => Header info entered once :)
- Pledges match line items (like PO)
- RMS Timetable options?
Shelter Management/Needs assessment
- #families/#people => Food/Water/Shelter needs for simplified RMS reqs
User Guide for old PHP system:
Wireframes for a proposed system for Nashville Floods:
Usability suggestion for Pakistan Vesion
- Home http://test.eden.sahanafoundation.org/eden/rms/index seems not necessary since the sub menu is quite clear to navigate.
- Submenu name should be consistent with the link page
- View request & Pledge aid Pledge Aid
- View & edit pledge Pledge. “List” & “Add” are two submenu under it.
Page for offer help.doc
) - added by 13 years ago.
Taiwan design for 'Offer Help' page
- Usability suggestion for RMS.doc (32.0 KB ) - added by 13 years ago.
Requirement of Request Management.doc
) - added by 12 years ago.
Download all attachments as: .zip
Note: See TracWiki for help on using the wiki.