[
http://mifosforge.jira.com/browse/MIFOSADMIN-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
johnwoodlock updated MIFOSADMIN-289:
------------------------------------
Attachment: RiseUpdateScript.sql
Sumit: The above script cleans rise data... as with the digamber & dds scripts
just replace the database name in the top line before running it thru mysql.
Everyone:
Comments are included in the attached file RiseUpdateScript.sql .... however
the biggest issue with Rise data was the lack of status history for loans.
There were 5324 loans in total. 4448 has no history. 876 had some but not
enough (e.g. 831 had nothing to indicate disbursement).
The major thing the script does is rebuild a good enough history for the loans
(for the DW). Here's a summary of the rebuild approach:
1) For loans with some loan history but not having an 'Application approved'
status 2 new entries are created, one for Application Approved and one for the
disbursement transition from approved to in good standing.
also depending on the current status (bad standing or cancelled) another entry
may be added to keep the history honest.
2) for loans without a status history... current status's were 5,9 and 6 (good
standing, bad standing, closed obligation met), 2 new entries are created, one
for Application Approved (using the account created_date as the history date)
and one for the disbursement transition from approved to in good standing
(using the disbursement date as the history date).
Then, for loans that have a current status of 'in bad standing' ... 83 of
them... a transition from good to bad standing is created with the history date
set to the disbursement date (although its unlikely to be the right date, its
probably best choice)
For loans that have a current status of 'closed obligation met' ... 185 of
them... a transition from good standing to closed obligation met is created
with the history date set to the highest transaction date found (should be last
repayment)
----
Note: I saw Binny's message that Rise are still doing some data work until next
week. Maybe Sumit can send me the output from running the script (x rows
updated etc. can talk with Sumit separately if needed)
> Get ETL Clean-up scripts for all MFIs
> -------------------------------------
>
> Key: MIFOSADMIN-289
> URL: http://mifosforge.jira.com/browse/MIFOSADMIN-289
> Project: mifos administration
> Issue Type: Story
> Reporter: Ryan Whitney
> Assignee: johnwoodlock
> Priority: Major
> Fix For: Cloud Release A, Cloud Release A - Iteration 5
>
> Attachments: DDSUpdateScript.sql, RiseUpdateScript.sql
>
>
> Already completed for Digamber, but this needs to be done for:
> In priority Order:
> KEEF
> Rise
> Light MF
> DDS - Open item, may be stalled will check up on this.
> Create sub-tasks for each of the MFI's you'd like, or we'll leave it at the
> story level.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
