Changes between Version 33 and Version 34 of HaitiRMSToDo

Timestamp:

01/21/10 12:17:15 (15 years ago)

Author:

Nico Presto

Comment:

--

HaitiRMSToDo

@@ -16 +16 @@
 
 === STATUS ===
-'''production (100120@02:45CT)'''
+'''production (100121@12:15UTC)'''
   * view with sms feeds from Ushahidi
    * disabled personal information fields (fname, lname, phone_num)
-  * with with twitter feeds from TtT
+  * view with twitter feeds from TtT
   * SMS alerts on map viewer
   * pledge system with simple flat-table extending sms feeds table
@@ -27 +27 @@
   * in production
 
-'''experimental (100118@4:34CT)'''
+'''experimental (100121@12:15UTC)'''
   * launchpad branch (~uwthw/sahana/rms)
-  * 3 tables request_aid, pledge_aid, match - building controllers/views
+  * 2 tables request_aid, pledge_aid - building controllers/views
 
 === TODO ===
-  * build logic for matching pledge and request (PRIORITY)
-   * match table that links request_item_id with pledge_item_id
+  * build logic for matching pledge and request (PRIORITY)              
    * percent completion (as pie graph) of pledge
   * pledge dashboard showing multiple pledge items by pledge organization (joined resource commented out in branch)
-  * icon showing status of pledge (red = unpledged, green = pledged)
-  * standardize this wiki page with the other project pages (FB: No big need. This is Temp status...move longer-term goodness to [wiki:UserGuidelinesRMS UserGuidelinesRMS])
+  * icon showing status of pledge set with represent (red = unpledged, green = pledged)
+  * start moving docs to [wiki:UserGuidelinesRMS UserGuidelinesRMS])
   * feed from Tweak the Tweet split feed into 2 tables: #offer & #help
   * report generating functionality assings id (alpha, beta,...) to pledges every ~6 hours to facilitate tracking by relief organizations
+  * connect comment fields to each pledge for follow-up and record keeping by the pledge donors. This table is commented out and can be connected as a component.
+
+=== Strategy ===
+We decided to combine the requests from different feeds into one table via the cron script. This has the benefit of transitioning from the current prod pledge system without changing the current tables. Also it means that feeds are stored "as is" for posterity. The origins are tracked with source (e.g. sms, tweet) and source id (ushahidi ID and TtTid). The source ids are necessary to close the loop with these groups by sending back info on which requests have been filled. The con is that there is duplication among tables.
 
  * Bugs need triaging/fixing: