Hi Sendoro,
Yes, you are correct regarding identification of family member. It was
difficult for me to develop functionality which would update/ delete a family
member record and then I came up with a work around of identifying the record
by using its client family member id. I am working on your requirement to add
identifiers and mobile number. Let me figure out a proper structure and would
enhance the api.
As of now, I am not storing physical address of client family member, will that
be problem/inconvenience ?If yes, we can discuss this further.
Regards,Nikhil
From: Sendoro Juma <[email protected]>
To: [email protected]; Nikhil Pawar <[email protected]>
Cc: Ed Cable <[email protected]>; Nayan Ambali <[email protected]>; Shaik
Nazeer <[email protected]>; Sendoro Juma
<[email protected]>
Sent: Wednesday, 14 June 2017 11:09 PM
Subject: Re: Requirement to capture Family details of client in Fineract
Hello Nikhil,
Family member(s) identify proof; I think is important so that the information
collected can be of verified.
Info. like ID #, ID Doc Type, Mobile # of the family members... //note Mobile
#should be in first page because nowadays it might be the easier thing to
verify.
I didn't see the address tab, I'm assuming that you will capture the physical
address.
My few cents.
Regards
Sendoro
----- Original Message -----
From: "Nikhil Pawar" <[email protected]>
To: "Sendoro Juma" <[email protected]>
Cc: "Ed Cable" <[email protected]>, "Nayan Ambali" <[email protected]>,
"Shaik Nazeer" <[email protected]>, "Nikhil Pawar"
<[email protected]>, "dev" <[email protected]>
Sent: Wednesday, June 14, 2017 8:18:28 PM
Subject: Re: Requirement to capture Family details of client in Fineract
Hello All,
Please find mock up of Family detail screen in the below
link.https://cwiki.apache.org/confluence/display/FINERACT/Family+Members+details
Kindly let me know if you have any feedback/changes/concerns with respect to
these screens.
Regards,Nikhil
From: Nikhil Pawar <[email protected]>
To: Sendoro Juma <[email protected]>
Cc: Ed Cable <[email protected]>; Nayan Ambali <[email protected]>; Shaik
Nazeer <[email protected]>; dev <[email protected]>
Sent: Monday, 12 June 2017 12:13 PM
Subject: Re: Requirement to capture Family details of client in Fineract
Hello Sendoro,
Thank you for your response. You are correct, we are using this information for
making inquiry with credit bureau and then reporting the standing of client to
credit bureau as well.(However, we are not using this information to determine
the credit score ourselves)As you said, you are storing the identifiers of
family members in custom fields. I am assuming that you must have created a
separate table for family members and in that table you are storing family
identifiers as well.In order to simplify the design and be consistent with
client model, we are planning to create a new table for storing family members'
identifiers(similar to m_client_identifiers).Let us know, your take on this
approach and would this be beneficial to you.
Regards,Nikhil
From: Sendoro Juma <[email protected]>
To: dev <[email protected]>; Nikhil Pawar <[email protected]>
Cc: Ed Cable <[email protected]>; Nayan Ambali <[email protected]>; Shaik
Nazeer <[email protected]>
Sent: Friday, 9 June 2017 9:36 PM
Subject: Re: Requirement to capture Family details of client in Fineract
Hello Nikhil,
Apologies for delay.
As I said earlier if I get you correct!!! This relation and information are
considered
1. credit score
2. Away to recover loan...
How we use today
- using custom fields
What info required
Marital status[mandatory] [Options are: Single, Married, Divorced, Widowed]
Nationa Identity # [Mandatory]
Identity Document Type: {Options Passport, National ID, Driving License,
Election ID}
Mobile number#
Physical Address
- Home Address
- Work Address
Future Looking
TIN # //Tax Identification Number
SSN # //Social Security Number
Note that... it is becoming now that Mobile # needs to be considered
mandatory... reason being, future looking fintech... the mobile operator calls
logs may be used to score credit worth of a customer... or related field kept.
Regards
Sendoro
----- Original Message -----
From: "Nikhil Pawar" <[email protected]>
To: "Sendoro Juma" <[email protected]>
Cc: "Ed Cable" <[email protected]>, "Nayan Ambali" <[email protected]>,
"dev" <[email protected]>, "Shaik Nazeer"
<[email protected]>
Sent: Thursday, June 8, 2017 10:09:04 PM
Subject: Re: Requirement to capture Family details of client in Fineract
Hello Sendoro,
We wanted to further understand the requirement of adding the Identifiers to
family members.Could you please let us know, if you are currently using this
set up.If yes, how is storing identifiers corresponding to family members
helping you in your operations.
Regards,Nikhil
From: Sendoro Juma <[email protected]>
To: [email protected]; Nikhil Pawar <[email protected]>
Cc: Ed Cable <[email protected]>; Nayan Ambali <[email protected]>; Shaik
Nazeer <[email protected]>
Sent: Thursday, 25 May 2017 4:42 PM
Subject: Re: Requirement to capture Family details of client in Fineract
Dear Nikhil,
I immediate spot "Marital Status", missing
May be these are needed too to fully identify the person.
National Identity #
Identity Document Type:
Regards
Sendoro
----- Original Message -----
From: "Nikhil Pawar" <[email protected]>
To: "Nikhil Pawar" <[email protected]>, "Dev" <[email protected]>
Cc: "Ed Cable" <[email protected]>, "Nayan Ambali" <[email protected]>,
"Shaik Nazeer" <[email protected]>
Sent: Thursday, May 25, 2017 2:05:25 PM
Subject: Re: Requirement to capture Family details of client in Fineract
Hello Devs,
Here are the proposed fields for the relationship table: Table name:
m_family_members-----------------------------------------------------------------------------------
- id (long)
- client_id (long) (Foreign Key) links id of
m_client
- FirstName (String)
- MiddleName (String)
- LastName (String)
- Qualification (String)
- relationship_cv_id (long) (Foreign Key) links id m_code_value
- profession_cv_id (long) (Foreign Key) links id m_code_value
- Gender_cv_id (long) (Foreign Key) links id m_code_value
- DateOfBirth (date dd:mm:yyyy)
Let me know, if you want to add additional fields.
Regards,Nikhil
From: Nikhil Pawar <[email protected]>
To: Dev <[email protected]>
Cc: Ed Cable <[email protected]>; Nayan Ambali <[email protected]>; Shaik
Nazeer <[email protected]>
Sent: Wednesday, 24 May 2017 3:32 PM
Subject: Requirement to capture Family details of client in Fineract
Hello Devs,
During integration of Equifax India , I felt the need to capture the Family
details of the client in Fineract.Currently I have hard coded the values to
make things work as there is no provision in Fineract to store the details of
Family.
However in the process of making the Integration generic, we would have to
capture these details in dedicated table.I would soon come up with the design
of the family details table.Meanwhile, if community members have alternative
suggestions, they are highly welcomed.
Regards,Nikhil
