Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 46E77200CA7 for ; Wed, 14 Jun 2017 20:18:20 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 45728160BDB; Wed, 14 Jun 2017 18:18:20 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3D4E6160BD6 for ; Wed, 14 Jun 2017 20:18:19 +0200 (CEST) Received: (qmail 58973 invoked by uid 500); 14 Jun 2017 18:18:18 -0000 Mailing-List: contact dev-help@fineract.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.apache.org Delivered-To: mailing list dev@fineract.apache.org Received: (qmail 58961 invoked by uid 99); 14 Jun 2017 18:18:18 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2017 18:18:18 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id B46A8C32D1 for ; Wed, 14 Jun 2017 18:18:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.8 X-Spam-Level: *** X-Spam-Status: No, score=3.8 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=2, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_FILL_THIS_FORM_SHORT=0.01] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id w9wbJRZs2Thm for ; Wed, 14 Jun 2017 18:18:14 +0000 (UTC) Received: from mail-it0-f66.google.com (mail-it0-f66.google.com [209.85.214.66]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id DBEAF5F297 for ; Wed, 14 Jun 2017 18:18:13 +0000 (UTC) Received: by mail-it0-f66.google.com with SMTP id 185so814465itv.3 for ; Wed, 14 Jun 2017 11:18:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:reply-to:to:cc:message-id:in-reply-to:references:subject :mime-version:content-length; bh=6oOHR6GfU2yvyoHzKMBl5PxpJgZcCzs8FTp2W1c1zls=; b=chk2SSKBzwOPYCn2ug4vMyG1okPLkdnp/cH0gNld5xjWuyuQul5WlMutdJE+My5B3K Nu02ITvFqNq4CY/RHHquAB542h7l/iJ/lAnusNgODalzFN4MGnS4mwpGHoKmh6LVI5A0 JHuw7RJbYg/8chw/gUqgQumtvZIAILUwGWAIIXSDzYcUiL+qX11Qfcv+xcScqIqH6C1H lIrC/QPyGGvLneQ2WJRjk7kCZ4VlRSqZBijr0NrVInvLs8Zm1aHDNEzKw1/dEir4wUyY Eu85AnqAeaBqBK8HeR1uIC6UTWCuCXy1iiKHjccE/5RhdDW4Sn3mupePxnqP/LG76Zlx 1WTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:to:cc:message-id:in-reply-to :references:subject:mime-version:content-length; bh=6oOHR6GfU2yvyoHzKMBl5PxpJgZcCzs8FTp2W1c1zls=; b=TohF82MaKWkoRgjoN5WSDr78C5fM8Ej//7xWOcGTZiLLgoCF/WSc8VwJY5EUQfcG5I xW+TFirDTakU01mzGVXt0wvJMLSsf6pPkyt0q4UvvpMgVOnVWj36EEIGJ3HR4dPXQYgr T6VtQloGIS861IASqQwDZGwxsJynSd3aIeA6EgiCrNExQ7v/dsuyBk6vWutvL0187PrG JIVpgUgkNaUDFAmhCHoIvbTo7IJrzIpS06ef9svBCrdQFPm+nDy4IgUPx1uvvUWr0f4q BUD9FqOE/pBeerEIyPMqb8wCo8LctLyNLRDQ/QKZdCKtHE8lHpct5PAZhbRxXAXB62+M q/3g== X-Gm-Message-State: AKS2vOxYwZe/VBypHirsAd0s76ovbeCUP9FbnUx8NM/apk6kSbHrPwa/ BXaNQkKqXkAz5G9qtBE= X-Received: by 10.36.105.13 with SMTP id e13mr1422667itc.64.1497464292664; Wed, 14 Jun 2017 11:18:12 -0700 (PDT) Received: from smtpsendws102.mail.ne1.yahoo.com (smtpsendws102.mail.ne1.yahoo.com. [98.138.101.179]) by smtp.gmail.com with ESMTPSA id b62sm368520itd.2.2017.06.14.11.18.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Jun 2017 11:18:12 -0700 (PDT) X-YMail-OSG: GTGelOcVM1mnUKEq.0SFEHt7quFoDMfYAjItSba_ui.h7ccxg4qQOMn49m6ueat DiztvaW8VhEAzDGau0V5kq_FaGKl2.q.wl.MkAZSlvgZoQHxg5uuMFGW8UrvdUdY5VlSnQH5wG10 F8.OXWIfz4ZBaAFs8K.WjKqcsHyCj1Luf13IeP1uv0y7G9c.G__4S2v6qum7jh0mQaTpy_9KA_I_ e0MrJCpsP8M08nN_fb6Bw8UuFyvSgzJeIiDfZvAyxExI7WhVEci_Ot4Kte4rf.JjXfvLvCqQVAAe R7bmEr1uGEu2f4DHRRYXdMleD3B5I6H5gtaRx_1SRyIui6ImEdUlbx9C5Z8BwOch4d_ds9oAWYJ7 ydOQFqx2u7RdyZdRmD3f0QAgsYqNyLLmEkrm0w9E46_oHRFX8IUnhL_bp1D6PLriMuzFZ0KqOFu4 mRMX5C53xsV4GPqdDGDELcZIsfRCA31Fj_JPhwGtd_QZrc9eOoWhMXo2JzLMUjNPj84VMNnxe1.b oW3uvHb7JGUU4ENX90VLWJFkSlugOjGJgXdfvSPJkTnOlUjk1rIbv.YwMhBET9Noy Received: from jws600045.mail.sg3.yahoo.com by smtpsendws102.mail.ne1.yahoo.com; Wed, 14 Jun 2017 18:18:09 +0000; 1497464289.997 Date: Wed, 14 Jun 2017 18:17:42 +0000 (UTC) From: Nikhil Pawar Reply-To: Nikhil Pawar To: Sendoro Juma , "dev@fineract.apache.org" Cc: Ed Cable , Nayan Ambali , Shaik Nazeer Message-ID: <145362393.11513614.1497464262423@mail.yahoo.com> In-Reply-To: <433350554.27112.1497461846664.JavaMail.zimbra@singoafrica.com> References: <360772882.1559859.1495620152804.ref@mail.yahoo.com> <360772882.1559859.1495620152804@mail.yahoo.com> <374818557.1611545.1495710325807@mail.yahoo.com> <128663537.594.1495710665342.JavaMail.zimbra@singo.co.tz> <639536155.6271120.1496948944569@mail.yahoo.com> <563840003.123981.1497024264302.JavaMail.zimbra@singo.co.tz> <1386632395.8821066.1497249803120@mail.yahoo.com> <2106477116.11411362.1497460708554@mail.yahoo.com> <433350554.27112.1497461846664.JavaMail.zimbra@singoafrica.com> Subject: Re: Requirement to capture Family details of client in Fineract MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11513613_2090603887.1497464262418" X-Mailer: WebService/1.1.9778 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 archived-at: Wed, 14 Jun 2017 18:18:20 -0000 ------=_Part_11513613_2090603887.1497464262418 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Sendoro, Yes, you are correct regarding identification of family member. It was diff= icult for me to develop functionality which would update/ delete a family m= ember record and then I came up with a work around of identifying the recor= d by using its =C2=A0client family member id.=C2=A0I am working on your req= uirement to add identifiers and mobile number. Let me figure out a proper s= tructure 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=C2=A0 From: Sendoro Juma To: dev@fineract.apache.org; Nikhil Pawar =20 Cc: Ed Cable ; Nayan Ambali ; Sh= aik Nazeer ; Sendoro Juma Sent: Wednesday, 14 June 2017 11:09 PM Subject: Re: Requirement to capture Family details of client in Fineract =20 Hello Nikhil, Family member(s) identify proof; I think is important so that the informati= on collected can be of verified.=20 Info. like ID #, ID Doc Type, Mobile # of the family members... //note Mobi= le #should be in first page because nowadays it might be the easier thing t= o verify. I didn't see the address tab, I'm assuming that you will capture the physic= al address. My few cents. Regards Sendoro ----- Original Message ----- From: "Nikhil Pawar" To: "Sendoro Juma" Cc: "Ed Cable" , "Nayan Ambali" = , "Shaik Nazeer" , "Nikhil Pawar" , "dev" 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 t= o these screens. Regards,Nikhil =C2=A0 =C2=A0 =C2=A0 From: Nikhil Pawar To: Sendoro Juma =20 Cc: Ed Cable ; Nayan Ambali ; Sh= aik Nazeer ; dev Sent: Monday, 12 June 2017 12:13 PM Subject: Re: Requirement to capture Family details of client in Fineract =C2=A0=20 Hello Sendoro, Thank you for your response.=C2=A0You are correct, we are using this inform= ation for making inquiry with credit bureau and then reporting the standing= of client=C2=A0to credit bureau as well.(However, we are not using this in= formation to determine the credit score ourselves)As you said, you are stor= ing the identifiers of family members in custom fields. I am assuming that = you must have created a separate =C2=A0table 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_identifi= ers).Let us know, your take on this approach and would this be beneficial t= o you. Regards,Nikhil =C2=A0 =C2=A0 =C2=A0 From: Sendoro Juma To: dev ; Nikhil Pawar =20 Cc: Ed Cable ; Nayan Ambali ; Sh= aik Nazeer Sent: Friday, 9 June 2017 9:36 PM Subject: Re: Requirement to capture Family details of client in Fineract =C2=A0=20 Hello Nikhil, Apologies for delay. As I said earlier if I get you correct!!! This relation and information are= considered=20 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 #=C2=A0 =C2=A0 =C2=A0 [Mandatory] Identity Document Type:=C2=A0 {Options Passport, National ID, Driving Licen= se, Election ID} Mobile number#=20 Physical Address=20 =C2=A0 - Home Address =C2=A0 - Work Address=20 Future Looking TIN #=C2=A0 =C2=A0 =C2=A0 //Tax Identification Number SSN #=C2=A0 =C2=A0 =C2=A0 //Social Security Number=20 Note that... it is becoming now that Mobile # needs to be considered mandat= ory... reason being, future looking fintech... the mobile operator calls lo= gs may be used to score credit worth of a customer... or related field kept= . Regards Sendoro ----- Original Message ----- From: "Nikhil Pawar" To: "Sendoro Juma" Cc: "Ed Cable" , "Nayan Ambali" = , "dev" , "Shaik Nazeer" 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 t= o family members.Could you please let us know, if you are currently using t= his set up.If yes, how is storing identifiers corresponding to family membe= rs helping you in your operations. Regards,Nikhil =C2=A0 =C2=A0 =C2=A0 From: Sendoro Juma To: dev@fineract.apache.org; Nikhil Pawar =20 Cc: Ed Cable ; Nayan Ambali ; Sh= aik Nazeer Sent: Thursday, 25 May 2017 4:42 PM Subject: Re: Requirement to capture Family details of client in Fineract =C2=A0=20 Dear Nikhil, I immediate spot "Marital Status", missing=20 May be these are needed too to fully identify the person. National Identity #=20 Identity Document Type:=20 Regards Sendoro=20 ----- Original Message ----- From: "Nikhil Pawar" To: "Nikhil Pawar" , "Dev" Cc: "Ed Cable" , "Nayan Ambali" = , "Shaik Nazeer" 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:=C2=A0Table name: m= _family_members------------------------------------------------------------= -----------------------=C2=A0=20 =C2=A0 - =C2=A0id =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (long)=C2=A0= =20 =C2=A0 - =C2=A0client_id =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (long) (Foreign Key) links id of m_clien= t=C2=A0=20 =C2=A0 - =C2=A0FirstName =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0(String)=C2=A0=20 =C2=A0 - =C2=A0MiddleName =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0(String)=C2=A0=20 =C2=A0 - =C2=A0LastName =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0(String)=C2=A0=20 =C2=A0 - =C2=A0Qualification =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 (String)=C2=A0=20 =C2=A0 - =C2=A0relationship_cv_id =C2=A0 =C2=A0 =C2=A0 =C2=A0 (long) (Forei= gn Key) links id m_code_value=C2=A0=20 =C2=A0 - =C2=A0profession_cv_id =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (long) (= Foreign Key) links id m_code_value=C2=A0=20 =C2=A0 - =C2=A0Gender_cv_id =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 (long) (Foreign Key) links id m_code_value=C2=A0=20 =C2=A0 - =C2=A0DateOfBirth =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 (date dd:mm:yyyy)=C2=A0=20 Let me know, if you want to add additional fields. Regards,Nikhil =C2=A0 =C2=A0 =C2=A0 From: Nikhil Pawar To: Dev =20 Cc: Ed Cable ; Nayan Ambali ; Sh= aik Nazeer Sent: Wednesday, 24 May 2017 3:32 PM Subject: Requirement to capture Family details of client in Fineract =C2=A0=20 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 t= o make things work as there is no provision in Fineract to store the detail= s of Family. =C2=A0However in the process of making the Integration generic, we would ha= ve to capture these details in dedicated table.I would soon come up with th= e design of the family details table.Meanwhile, if community members have a= lternative suggestions, they are highly welcomed. Regards,Nikhil =20 ------=_Part_11513613_2090603887.1497464262418--