[
http://mifosforge.jira.com/browse/MIFOS-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kay Chau updated MIFOS-3621:
----------------------------
Fix Version/s: (was: Release E - Iteration 6)
Release E - Iteration 7
> Produce DW 'Document' for Design Review and Testing Purposes
> ------------------------------------------------------------
>
> Key: MIFOS-3621
> URL: http://mifosforge.jira.com/browse/MIFOS-3621
> Project: mifos
> Issue Type: Story
> Components: Reports Module
> Reporter: johnwoodlock
> Assignee: johnwoodlock
> Fix For: Release E - Iteration 7, Release E
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> Need to layout what I've done so far in DW Schema and ETL work so that it can
> be considered and improved upon (and help testing discussion)
> Already have got a schema that reflects scope as stated in mifos-3617 and ETL
> that does an initial but not accurate data load into that schema.
> Got to where I've got to from 1) previous experience and understanding of
> mifos and mifos reporting and mostly 2) the business requirements implied in
> a set of standard reports Kay/Emily drew up... with 3 being most important
> right now.
--
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
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
