[
http://mifosforge.jira.com/browse/MIFOSBI-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
johnwoodlock resolved MIFOSBI-316.
----------------------------------
Resolution: Fixed
Scheduled For: Release
Change now in git.
When 'duplicate' loan officer names are identified as an issue the dim_customer
entry is associated with the 0 personnnel_key and a warning message is put on
the log to aid troubleshooting.
> ETL Stops if Staff Names have Duplicates
> ----------------------------------------
>
> Key: MIFOSBI-316
> URL: http://mifosforge.jira.com/browse/MIFOSBI-316
> Project: mifos business intelligence
> Issue Type: Improvement
> Affects Versions: Mifos BI 1.2
> Reporter: johnwoodlock
> Assignee: johnwoodlock
> Fix For: Mifos BI 1.3
>
>
> Currently, the ETL will stop near its start if there are duplicate Personnel
> display_names (and takes name changes into account to). Mifos allows
> duplicate display_names but the ETL doesn't because the audit tables use the
> display_name rather then the personnel_id to record loan officer
> reassignments... so a duplicate display_name mean ambiguity.
> Proposal is to identify when this problem occurs for loan officer
> reassignment and Warn instead of stop and allocate for the time being to
> personnel '-1' which is a bucket to identify the extent of this problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
