[
http://mifosforge.jira.com/browse/MIFOS-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Chau moved MIFOSBI-118 to MIFOS-4286:
-----------------------------------------
Component/s: (was: Data Warehouse)
Reports Module
Fix Version/s: (was: Mifos BI 1.0 BETA - Iteration 12)
(was: Mifos BI 1.0 BETA)
Elsie F
Scheduled For: Release
Affects Version/s: (was: Mifos BI 1.0 BETA - Iteration 12)
(was: Mifos BI 1.0 BETA)
Release E
Key: MIFOS-4286 (was: MIFOSBI-118)
Project: mifos (was: mifos business intelligence)
> Add timestamps to mifos tables loan_schedules & customer_attendance to
> benefit ETL incremental updates
> ------------------------------------------------------------------------------------------------------
>
> Key: MIFOS-4286
> URL: http://mifosforge.jira.com/browse/MIFOS-4286
> Project: mifos
> Issue Type: Story
> Components: Reports Module
> Affects Versions: Release E
> Reporter: johnwoodlock
> Assignee: johnwoodlock
> Fix For: Elsie F
>
>
> loan_schedule and customer_attendance are 2 tables which are brought into the
> Data Warehouse.
> Although there are dates on these tables, I can't find anything sensible that
> allows me to know the 'system' date that records are added or updated to them.
> A timestamp column is a simple way to allow this.
> Without the timestamp I have to clear down the DW version and copy all of
> their data over each time. Not a major problem for small MFI's (even Secdep)
> but would be for bigger ones.
> It would be best to add this to Release E to get it out of the way and not
> have it on our backlog. However, if it isn't done in Release E we'd tackle
> it the same way we will tackle 1.6 use of DW. We'd manually add the
> timestamp before we put the DW live on an MFI (part of the data quality
> check). And then when we eventually get round to putting it onto the mifos
> schema formally... the upgrade has to check that the column isn't already
> there.
> May be similar thing for PPI surveys but not sure yet (waiting to talk to Van)
> work involved is very simple but we'd have to time it for a big MFI like GK
> to see how much it might add to their upgrade (I don't think its huge but
> they are big tables at GK)
--
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
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Mifos-issues mailing list
Mifos-issues@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues
