You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by Ed Cable <ed...@gmail.com> on 2016/06/29 17:53:53 UTC
Re: [Mifos-developer] [IMPORTANT] Query regarding standard address table
+1 from my side to making client address a standard out of the box feature
as a part of the core client record provided we address sander's feedback
from the previous thread on this on April 12 -
https://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201604.mbox/browser
and make the fields generic enough such that it supports the most common
address formats used worldwide. We should incorporate all the feedback and
discussion from that thread regarding turning these fields on and off and
the proper field-level validations.
This is coming up on numerous active threads and I thank Nayan for
recognizing all the different use cases where not having address fields as
part of core client record is an inhibitor.
On Wed, Jun 29, 2016 at 5:49 AM, Nayan Ambali <na...@gmail.com>
wrote:
> Dayna, Markus,
>
> I feel, adding standard address to customer solves other problems too,
> example address can be made mandatory before activating client, address can
> be capture along with customer creation, Geo location based service on
> Android can built.
>
> i vote for adding client address as standard(out of box) feature.
>
> Thanks
> Nayan Ambali
>
>
>
> Thanks and Regards,
> Nayan Ambali
> +91 9591996042
> skype: nayangambali
>
> On Wed, Jun 29, 2016 at 6:07 PM, <ni...@yahoo.in> wrote:
>
>> Hello Devs,
>>
>> While designing the credit bureau module, I came across few design
>> questions and I wanted community's opinion on that.
>> When you make a credit check query, the credit bureau expects you to send
>> the address along with few other identifiers.
>>
>> In order to fetch the address fields in a more hassle free and less error
>> prone way, I was thinking if we can standardize the address as core table.
>> By standardizing this address table, we may remove the need for defining
>> custom data table for storing addresses.
>>
>> Let me know your thoughts on this proposal of mine.
>>
>> Regards,
>> Nikhil
>>
>>
>
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> Mifos-developer mailing list
> mifos-developer@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
Re: [Mifos-developer] [IMPORTANT] Query regarding standard address table
Posted by Nayan Ambali <na...@gmail.com>.
Thanks Markus for the support and the pointer to the ISO standard, looks
like ISO spec are not available for free :(
@Ed, sometimes solutions are simple and known but we tend to over think
about problem as complex, if I look back and see the implementation of
Mifos 2,x, we had option to enable, disable and make fields mandatory, we
can simply adapt the same strategy here, if some one is not interest to use
the address, just disable it and continue with data table.
@Nikil,
Can you come-up with data model for the same and share with dev community
for review, so that you can start working on immediately.
also please read the discussion at
http://stackoverflow.com/questions/307027/is-this-a-good-way-to-model-address-information-in-a-relational-database
Thanks
Nayan Ambali
Thanks and Regards,
Nayan Ambali
+91 9591996042
skype: nayangambali
On Thu, Jun 30, 2016 at 10:25 AM, Markus Geiß <ma...@live.de> wrote:
> Hey all,
>
>
>
> agreed. BTW there is a ISO standard covering addressing, ISO 19160.
>
> We should consider this when implementing addresses.
>
>
>
> Cheers
>
>
>
> Markus
>
>
>
> Von: Saransh Sharma<ma...@theupscale.in>
> Gesendet: Donnerstag, 30. Juni 2016 01:34
> An: dev@fineract.incubator.apache.org<mailto:
> dev@fineract.incubator.apache.org>
> Betreff: Re: [Mifos-developer] [IMPORTANT] Query regarding standard
> address table
>
>
>
>
> https://github.com/maektwain/INNOVA/blob/master/mifosng-provider/src/main/java/org/mifosplatform/portfolio/client/api/ClientAddressApiResource.java
>
> We have been using this standard API of addresses you can have a look at
> it, we have infact desgined the UI in community app, the business logic is
> standard here, but we can always extend
>
> On Thu, Jun 30, 2016 at 12:11 AM Ed Cable <ed...@mifos.org> wrote:
>
> > +1 from my side to making client address a standard out of the box
> feature
> > as a part of the core client record provided we address sander's feedback
> > from the previous thread on this on April 12 -
> >
> >
> https://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201604.mbox/browser
> > and make the fields generic enough such that it supports the most common
> > address formats used worldwide. We should incorporate all the feedback
> and
> > discussion from that thread regarding turning these fields on and off and
> > the proper field-level validations.
> >
> > This is coming up on numerous active threads and I thank Nayan for
> > recognizing all the different use cases where not having address fields
> as
> > part of core client record is an inhibitor.
> >
> > On Wed, Jun 29, 2016 at 5:49 AM, Nayan Ambali <na...@gmail.com>
> > wrote:
> >
> > > Dayna, Markus,
> > >
> > > I feel, adding standard address to customer solves other problems too,
> > > example address can be made mandatory before activating client, address
> > can
> > > be capture along with customer creation, Geo location based service on
> > > Android can built.
> > >
> > > i vote for adding client address as standard(out of box) feature.
> > >
> > > Thanks
> > > Nayan Ambali
> > >
> > >
> > >
> > > Thanks and Regards,
> > > Nayan Ambali
> > > +91 9591996042
> > > skype: nayangambali
> > >
> > > On Wed, Jun 29, 2016 at 6:07 PM, <ni...@yahoo.in> wrote:
> > >
> > >> Hello Devs,
> > >>
> > >> While designing the credit bureau module, I came across few design
> > >> questions and I wanted community's opinion on that.
> > >> When you make a credit check query, the credit bureau expects you to
> > send
> > >> the address along with few other identifiers.
> > >>
> > >> In order to fetch the address fields in a more hassle free and less
> > error
> > >> prone way, I was thinking if we can standardize the address as core
> > table.
> > >> By standardizing this address table, we may remove the need for
> defining
> > >> custom data table for storing addresses.
> > >>
> > >> Let me know your thoughts on this proposal of mine.
> > >>
> > >> Regards,
> > >> Nikhil
> > >>
> > >>
> > >
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> > > Francisco, CA to explore cutting-edge tech and listen to tech
> luminaries
> > > present their vision of the future. This family event has something for
> > > everyone, including kids. Get more information and register today.
> > > http://sdm.link/attshape
> > > Mifos-developer mailing list
> > > mifos-developer@lists.sourceforge.net
> > > Unsubscribe or change settings at:
> > > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> > >
> >
>
AW: [Mifos-developer] [IMPORTANT] Query regarding standard address
table
Posted by Markus Geiß <ma...@live.de>.
Hey all,
agreed. BTW there is a ISO standard covering addressing, ISO 19160.
We should consider this when implementing addresses.
Cheers
Markus
Von: Saransh Sharma<ma...@theupscale.in>
Gesendet: Donnerstag, 30. Juni 2016 01:34
An: dev@fineract.incubator.apache.org<ma...@fineract.incubator.apache.org>
Betreff: Re: [Mifos-developer] [IMPORTANT] Query regarding standard address table
https://github.com/maektwain/INNOVA/blob/master/mifosng-provider/src/main/java/org/mifosplatform/portfolio/client/api/ClientAddressApiResource.java
We have been using this standard API of addresses you can have a look at
it, we have infact desgined the UI in community app, the business logic is
standard here, but we can always extend
On Thu, Jun 30, 2016 at 12:11 AM Ed Cable <ed...@mifos.org> wrote:
> +1 from my side to making client address a standard out of the box feature
> as a part of the core client record provided we address sander's feedback
> from the previous thread on this on April 12 -
>
> https://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201604.mbox/browser
> and make the fields generic enough such that it supports the most common
> address formats used worldwide. We should incorporate all the feedback and
> discussion from that thread regarding turning these fields on and off and
> the proper field-level validations.
>
> This is coming up on numerous active threads and I thank Nayan for
> recognizing all the different use cases where not having address fields as
> part of core client record is an inhibitor.
>
> On Wed, Jun 29, 2016 at 5:49 AM, Nayan Ambali <na...@gmail.com>
> wrote:
>
> > Dayna, Markus,
> >
> > I feel, adding standard address to customer solves other problems too,
> > example address can be made mandatory before activating client, address
> can
> > be capture along with customer creation, Geo location based service on
> > Android can built.
> >
> > i vote for adding client address as standard(out of box) feature.
> >
> > Thanks
> > Nayan Ambali
> >
> >
> >
> > Thanks and Regards,
> > Nayan Ambali
> > +91 9591996042
> > skype: nayangambali
> >
> > On Wed, Jun 29, 2016 at 6:07 PM, <ni...@yahoo.in> wrote:
> >
> >> Hello Devs,
> >>
> >> While designing the credit bureau module, I came across few design
> >> questions and I wanted community's opinion on that.
> >> When you make a credit check query, the credit bureau expects you to
> send
> >> the address along with few other identifiers.
> >>
> >> In order to fetch the address fields in a more hassle free and less
> error
> >> prone way, I was thinking if we can standardize the address as core
> table.
> >> By standardizing this address table, we may remove the need for defining
> >> custom data table for storing addresses.
> >>
> >> Let me know your thoughts on this proposal of mine.
> >>
> >> Regards,
> >> Nikhil
> >>
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> > Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> > present their vision of the future. This family event has something for
> > everyone, including kids. Get more information and register today.
> > http://sdm.link/attshape
> > Mifos-developer mailing list
> > mifos-developer@lists.sourceforge.net
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> >
>
Re: [Mifos-developer] [IMPORTANT] Query regarding standard address table
Posted by Saransh Sharma <sa...@theupscale.in>.
https://github.com/maektwain/INNOVA/blob/master/mifosng-provider/src/main/java/org/mifosplatform/portfolio/client/api/ClientAddressApiResource.java
We have been using this standard API of addresses you can have a look at
it, we have infact desgined the UI in community app, the business logic is
standard here, but we can always extend
On Thu, Jun 30, 2016 at 12:11 AM Ed Cable <ed...@mifos.org> wrote:
> +1 from my side to making client address a standard out of the box feature
> as a part of the core client record provided we address sander's feedback
> from the previous thread on this on April 12 -
>
> https://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201604.mbox/browser
> and make the fields generic enough such that it supports the most common
> address formats used worldwide. We should incorporate all the feedback and
> discussion from that thread regarding turning these fields on and off and
> the proper field-level validations.
>
> This is coming up on numerous active threads and I thank Nayan for
> recognizing all the different use cases where not having address fields as
> part of core client record is an inhibitor.
>
> On Wed, Jun 29, 2016 at 5:49 AM, Nayan Ambali <na...@gmail.com>
> wrote:
>
> > Dayna, Markus,
> >
> > I feel, adding standard address to customer solves other problems too,
> > example address can be made mandatory before activating client, address
> can
> > be capture along with customer creation, Geo location based service on
> > Android can built.
> >
> > i vote for adding client address as standard(out of box) feature.
> >
> > Thanks
> > Nayan Ambali
> >
> >
> >
> > Thanks and Regards,
> > Nayan Ambali
> > +91 9591996042
> > skype: nayangambali
> >
> > On Wed, Jun 29, 2016 at 6:07 PM, <ni...@yahoo.in> wrote:
> >
> >> Hello Devs,
> >>
> >> While designing the credit bureau module, I came across few design
> >> questions and I wanted community's opinion on that.
> >> When you make a credit check query, the credit bureau expects you to
> send
> >> the address along with few other identifiers.
> >>
> >> In order to fetch the address fields in a more hassle free and less
> error
> >> prone way, I was thinking if we can standardize the address as core
> table.
> >> By standardizing this address table, we may remove the need for defining
> >> custom data table for storing addresses.
> >>
> >> Let me know your thoughts on this proposal of mine.
> >>
> >> Regards,
> >> Nikhil
> >>
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> > Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> > present their vision of the future. This family event has something for
> > everyone, including kids. Get more information and register today.
> > http://sdm.link/attshape
> > Mifos-developer mailing list
> > mifos-developer@lists.sourceforge.net
> > Unsubscribe or change settings at:
> > https://lists.sourceforge.net/lists/listinfo/mifos-developer
> >
>
Fwd: [Mifos-developer] [IMPORTANT] Query regarding standard address table
Posted by Ed Cable <ed...@mifos.org>.
+1 from my side to making client address a standard out of the box feature
as a part of the core client record provided we address sander's feedback
from the previous thread on this on April 12 -
https://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201604.mbox/browser
and make the fields generic enough such that it supports the most common
address formats used worldwide. We should incorporate all the feedback and
discussion from that thread regarding turning these fields on and off and
the proper field-level validations.
This is coming up on numerous active threads and I thank Nayan for
recognizing all the different use cases where not having address fields as
part of core client record is an inhibitor.
On Wed, Jun 29, 2016 at 5:49 AM, Nayan Ambali <na...@gmail.com>
wrote:
> Dayna, Markus,
>
> I feel, adding standard address to customer solves other problems too,
> example address can be made mandatory before activating client, address can
> be capture along with customer creation, Geo location based service on
> Android can built.
>
> i vote for adding client address as standard(out of box) feature.
>
> Thanks
> Nayan Ambali
>
>
>
> Thanks and Regards,
> Nayan Ambali
> +91 9591996042
> skype: nayangambali
>
> On Wed, Jun 29, 2016 at 6:07 PM, <ni...@yahoo.in> wrote:
>
>> Hello Devs,
>>
>> While designing the credit bureau module, I came across few design
>> questions and I wanted community's opinion on that.
>> When you make a credit check query, the credit bureau expects you to send
>> the address along with few other identifiers.
>>
>> In order to fetch the address fields in a more hassle free and less error
>> prone way, I was thinking if we can standardize the address as core table.
>> By standardizing this address table, we may remove the need for defining
>> custom data table for storing addresses.
>>
>> Let me know your thoughts on this proposal of mine.
>>
>> Regards,
>> Nikhil
>>
>>
>
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> Mifos-developer mailing list
> mifos-developer@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>
Re: [Mifos-developer] [IMPORTANT] Query regarding standard address table
Posted by srinivasa Rao Yedida <sr...@gmail.com>.
HI
Address should be the part to the client profile even there should be two
type of address are very important to the profile.
1) Communication address
2) Permanent address
+ I vote for adding this option
On Wed, Jun 29, 2016 at 11:23 PM, Ed Cable <ed...@gmail.com> wrote:
> +1 from my side to making client address a standard out of the box feature
> as a part of the core client record provided we address sander's feedback
> from the previous thread on this on April 12 -
> https://mail-archives.apache.org/mod_mbox/incubator-fineract-dev/201604.mbox/browser
> and make the fields generic enough such that it supports the most common
> address formats used worldwide. We should incorporate all the feedback and
> discussion from that thread regarding turning these fields on and off and
> the proper field-level validations.
>
> This is coming up on numerous active threads and I thank Nayan for
> recognizing all the different use cases where not having address fields as
> part of core client record is an inhibitor.
>
> On Wed, Jun 29, 2016 at 5:49 AM, Nayan Ambali <na...@gmail.com>
> wrote:
>
>> Dayna, Markus,
>>
>> I feel, adding standard address to customer solves other problems too,
>> example address can be made mandatory before activating client, address can
>> be capture along with customer creation, Geo location based service on
>> Android can built.
>>
>> i vote for adding client address as standard(out of box) feature.
>>
>> Thanks
>> Nayan Ambali
>>
>>
>>
>> Thanks and Regards,
>> Nayan Ambali
>> +91 9591996042
>> skype: nayangambali
>>
>> On Wed, Jun 29, 2016 at 6:07 PM, <ni...@yahoo.in> wrote:
>>
>>> Hello Devs,
>>>
>>> While designing the credit bureau module, I came across few design
>>> questions and I wanted community's opinion on that.
>>> When you make a credit check query, the credit bureau expects you to
>>> send the address along with few other identifiers.
>>>
>>> In order to fetch the address fields in a more hassle free and less
>>> error prone way, I was thinking if we can standardize the address as core
>>> table.
>>> By standardizing this address table, we may remove the need for defining
>>> custom data table for storing addresses.
>>>
>>> Let me know your thoughts on this proposal of mine.
>>>
>>> Regards,
>>> Nikhil
>>>
>>>
>>
>>
>> ------------------------------------------------------------------------------
>> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
>> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
>> present their vision of the future. This family event has something for
>> everyone, including kids. Get more information and register today.
>> http://sdm.link/attshape
>> Mifos-developer mailing list
>> mifos-developer@lists.sourceforge.net
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>>
>
>
>
> ------------------------------------------------------------------------------
> Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San
> Francisco, CA to explore cutting-edge tech and listen to tech luminaries
> present their vision of the future. This family event has something for
> everyone, including kids. Get more information and register today.
> http://sdm.link/attshape
> Mifos-developer mailing list
> mifos-developer@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>