On 2/18/10 21:53, "Keith Woodlock" <[email protected]> wrote:
> Ryan, Kay,
>
>>> 1. As for the name, Repayment-Moratorium - Can we come up with a more
>>> descriptive name? I liked Repayment-Push out more
>
> My feeling is that Moratorium is alright if that name makes sense in
> the domain of finance and micro finance.. i.e. what would a domain
> expert call this? what are the customers requesting the feature
> calling it?
That's kind of a hard call. A moratorium in microfinance, as I understand
it, is basically giving clients a reprieve on their payments when tragedy
strikes (ie, a typhoon strikes so you want to give people four weeks to
recover before having to repay). So maybe it makes sense as it can be used
to do that, just weird that it falls under holidays.
Maybe the answer is to rename the section from just Holiday to "Holiday &
Moratoriums". Probably not a big deal though.
>>> 3. Since you are working in the schedule area, would this be a good time to
>>> clean up the LSIM feature?
>>> For example, for a few Mifos users they don¹t really have meetings.
>>> Instead, they set a schedule for repayment per loan account.
>>> The LSIM was meant to get around this but it still has a few bugs and
>>> doesn¹t work so great, so wondering if this would be a good time to add an
>>> option to decouple the scheduling?
>
> As far as LSIM goes, the ideal solution is to not have schedules
> coupled to meeting at all. Then when is non 'teller model' mode,
> constraints can be enforced on 'schedule generation' to make it comply
> with 'loan officer/customer meeting schedule', in 'teller model' mode,
> then there is no need to apply these constraints,only those of the
> loan repayment schedule itself.
>
> This is probably a reasonable amount of work but having looked at
> meetingBO recently I could see there was method there used when 'LSIM'
> is configured to be on that generate the same 'dates' as the normal
> 'getAllDates' generation method.. see
> MeetingGetAllDatesVersusIndependentOfMeetingTest.java in trunk.
>
> Again, when as we approach the current schedule generation of the fly
> work and the current refactoring of 'schedule date generation' this
> LSIM is falls into consideration. Again with this: if it becomes a
> priority we can focus in on it.
Good to know, I can follow-up internally. Personally, I think getting the
LSIM feature to work properly, or rather, de-couple the meeting schedules
would be a huge win for us. I also realize that we may not have the time
and resources at this time. That said, a "reasonable" amount of time
doesn't sound like something we could put in quick :)
Thanks for the follow up!
Ryan
--
Ryan Whitney
Mifos Technical Program Manager
[email protected]
Mifos - Technology that Empowers Microfinance (www.mifos.org)
Our mission is to enable the poor, especially the poorest, to create a world
without poverty.
<http://grameenfoundation.org/take-action/ingenuity-fund-challenge/>
P please consider the environment before printing this e-mail.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Mifos-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-users