Hello Sendoro, After you brought this point forward. I went through the documentation of an Indian Credit bureau and they are expecting following values for marital status:
- Cohabitating - Divorced - Married - Not Asked - Not Given - Other - Separated - Single - To Be Married - Widowed For obvious reasons, we cannot accommodate all the fields expected by different credit bureaus. I think we should wait for further inputs from the community as to what fields they feel are important to be included and come to general consensus. Regards, Nikhil On Thu, May 25, 2017 at 5:00 PM, Sendoro Juma <[email protected]> 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" <[email protected]> > To: "dev" <[email protected]> > Cc: "Ed Cable" <[email protected]>, "Shaik Nazeer" <nazeer.shaik@ > confluxtechnologies.com>, "Nayan Ambali" <[email protected]> > 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 >
