fineract-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Awasum Yannick <awasum.yann...@skylabase.com>
Subject Re: Requirement to add profession and marital status to m_client table
Date Thu, 25 May 2017 11:56:15 GMT
Its also important to capture details about Next of Kin, Children and
Siblings if possible. This information might be important when you start
looking not only at Credit Scoring but also Insurance and transfer to Value.

On Thu, May 25, 2017 at 12:30 PM, Sendoro Juma <sendoro@singo.co.tz> wrote:

> Dear Nikhil,
>
> Without pre-empting discussions... Marital Status is very key;  as it is
> considered to some extent for credit scoring... in emerging markets.
>
> As for type... May add the following...
> -Widowed
> -Separated
>
> I let to you to decide on how you handle.
>
> BR
> Sendoro
>
>
> ----- Original Message -----
> From: "Nikhil Pawar" <nickrp89@gmail.com>
> To: "dev" <dev@fineract.apache.org>
> Cc: "Ed Cable" <edcable@mifos.org>, "Shaik Nazeer" <nazeer.shaik@
> confluxtechnologies.com>, "Nayan Ambali" <nayan.ambali@gmail.com>
> Sent: Thursday, May 25, 2017 2:23:58 PM
> Subject: Requirement to add profession and marital status to m_client table
>
> Hello Devs,
>
> Its been a long awaited requirement to add Marital status and Profession/
> occupation to m_client table. Clients have been using data tables to work
> around this short coming.
> Marital status would be fed with system defined code_values:
>
>    - Single
>    - Married
>    - Divorced
>
> While Profession/Occupation would be left open for user defined
> code_values.
> Let us know your thoughts about it.
>
> Regards,
> Nikhil
>



-- 


*Awasum Yannick*
Chief Technology Officer
Skylabase
awasum.yannick@skylabase.com  |  Skype: awasum91 | Mobile: +237 676 683 945
<+237+676+683+945> | http://skylabase.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message