Changes between Version 1 and Version 2 of PakistanDevelopers

08/20/10 09:46:36 (14 years ago)
Michael Howden



  • PakistanDevelopers

    v1 v2  
    5252 * [BluePrintImporter PDF Importer?]
    5353 * Test the XForms controller with component resource to have OCRable forms to collect this info
     55=== Rotary Club ===
     56Rotary Club are training 750-1000 volunteers to collect data.
     58 1. We should be able to register volunteers, and assign them to geographic regions.  This would help us query and know the number of people working in each geographic area. 
     59 2. Volunteers belonging to a group (like geographic area) could then be sent messages via SMS service.  So an interface to let us do that that would be great.
     60 3. When our volunteers go out, they would enter data about the status of inventory at their locations, and items required urgently.  They would also be able to update the status of a shelter, in that they may setup a place as a shelter and provides its Lon/Lat, or they may remove a place as shelter for it may have been inundated too. 
     61 4. We want to record damages to people/life, and property.  Currently, we can record life losses in Incident Reporting, while property losses can be registered in Situation Reports & Assessments. 
     62 5. We can also record loss to farm animal and cattle.  There could be (a) field(s) to do that.  Instead of going for a table of animal and then entering the number of lost animals, we could give an open text field. 
     63 6. We want to see the Situations, Assessments, Schools and Flood Reports to be visible on the map as well.  Can that be done?
     64 7. We would love to see an option where we could define a warehouse/shelter/school, where we could mention the inventory available there, and their count.  This feature is available in Agasti.  If provided, our volunteers would be able to trace themselves the items they need and where they are placed. 
     65 8. Missing Persons:
     66 * When adding a new missing person, we would need to provide his hometown (from where he was lost) and the location of his residence.  Like someone could be missing from a camp/shelter in Peshawar, while his residence would be in Swat. 
     67 * When reporting a missing person, we should be able to provide his photo too.  This should be optional.
     68 * An option should be there, like a status/flag, to tell if the person has been found.  Additional information like “where from” would be an added plus, but not essential.
     69 9. When entering a shelter or inventory, we would like to identify the city/location where it is located.  This is the first anchor of reference.  Also, we should be allowed to (optionally) provide coordinates, or point the location on the map.  That way, it should be visible on the map when someone takes a view of the map with shelter, inventory and incident overviews. This would be very helpful. 
     70 10. Since I can see the situation and incidents are different in the system, “Situation” should also be available in the map overlays. 
     72==== Sync ====
     73Want to be able to collect data on offline laptops & sync to base
     74 * This means that the schema for this module is pretty fixed as we can't update remote laptops
     75  * Extra data can be incoporated into comments fields for transferring to new optional fields centrally by-hand
     76  * Can still develop UI tweaks to ease data entry (just won't be visible to remote laptops): Labels/Help
     77  * Can still develop Reporting functionality
     78  * Can still develop other modules
     79 * Power may be an issue, so best to have printed copies of the Assessment Tool as well
     80 * Sync process should be tested thoroughly (even if kept to a very simple Data upload facility)
     82==== SMS ====
     83 * Outbound to alert teams (working with a local telco to get details)
     84 * SMS inbound for them to report incidents (separate to the general public whose reports we can pull from Ushahidi so can use the general shortcode)