You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@fineract.apache.org by ni...@yahoo.in.INVALID on 2016/06/29 12:37:42 UTC

[IMPORTANT] Query regarding standard address table

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

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
>

Re: [Mifos-developer] [IMPORTANT] Query regarding standard address table

Posted by Ed Cable <ed...@gmail.com>.
+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: [IMPORTANT] Query regarding standard address table

Posted by ni...@yahoo.in.INVALID.
I could not convince myself with your third point.Let me explain by taking a simple use case of slum dwellers in Mumbai.In Mumbai there is one government scheme named as 'SRA' wherein slum dwellers are given houses in building in exchange of their slums.In between this exchange, there is a time slot of 4-5 years wherein slum dwellers have address proof of their slums( which is not in existence now) and are currently living in temporary accommodation( whose address proof) they don't have.Only in such cases it makes sense to store two addresses( permanent and current). In rest of the cases, we would rather go with permanent address, instead of storing two same address.So is there still a need of storing a boolean value.Let me know your view on this.
Regards,Nikhil
      From: Saransh Sharma <sa...@theupscale.in>
 To: dev@fineract.incubator.apache.org 
Cc: Nayan Ambali <na...@gmail.com>; NIKHIL PAWAR <ni...@yahoo.in>; Dayna Harp <dh...@mifos.org>; Mifos Software Development <mi...@lists.sourceforge.net>; Markus Geiß <mg...@mifos.org>; Ed Cable <ed...@mifos.org>; Nazeer Shaik <na...@confluxtechnologies.com>
 Sent: Thursday, 30 June 2016 3:29 PM
 Subject: Re: [IMPORTANT] Query regarding standard address table
   
See, the flow is generic while adding addresses for the customer the basic
flow should be,

1 Address Type as suggested by Srinivasan but it should not duplicate the
same address type we should be able to add more, addressType as per the
requirements once the addressType is created it should not create the same
addressType again

2 State Type we can load it from CodeValues

3. There are some cases when the customer have same address for case like
Permanent and Residential a boolean for sameAddressType should be
introduced or isBoth kind of boolean should be introduced and once the
addresses are same it should not create new address type with the following
one,

On Thu, Jun 30, 2016 at 3:20 PM Nikhil Pawar <ni...@gmail.com> wrote:

> Latitude and longitude are also the attributes along with other fields of
> the address table.
>
> Regards,
> Nikhil
>
> On Thu, Jun 30, 2016 at 3:15 PM, Saransh Sharma <sa...@theupscale.in>
> wrote:
>
> > What about geo mapping ? which enables the latitude and longitude from
> > google maps or some other service
> >
> > On Thu, Jun 30, 2016 at 2:41 PM Nikhil Pawar <ni...@gmail.com> wrote:
> >
> > > Hello All,
> > >
> > > Please find the attached schema diagram of the proposed Address and
> > > related configuration tables.
> > > A quick description of the diagram:
> > > Address table:
> > > The fields of the address table would be configurable. The user can
> > select
> > > the field via field configuration table.
> > > Rest of the fields are self explanatory.
> > >
> > >
> > > On Thu, Jun 30, 2016 at 1:48 PM, Ankit Sharma <an...@theupscale.in>
> > wrote:
> > >
> > >> Hi team,
> > >> We have already made addresses - official, residential and permanent
> as
> > a
> > >> standard feature of CB.
> > >> Looking forward on this.
> > >>
> > >> Ankit Sharma
> > >> Upscale
> > >>
> > >> > On 30-Jun-2016, at 1:42 PM, Ashok <as...@confluxtechnologies.com>
> > >> wrote:
> > >> >
> > >> > +1
> > >> >
> > >> > It makes sense to have a standard address with minimal fields to
> > >> support CB
> > >> > or any other integrations and can be extended/configurable by
> > >> organization.
> > >> >
> > >> > Thanks and Regards,
> > >> > Ashok
> > >> >
> > >> > On Wed, Jun 29, 2016 at 6:19 PM, Nayan Ambali <
> nayan.ambali@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
> > >> >>
> > >>
> > >
> > >
> >
>


  

Re: [IMPORTANT] Query regarding standard address table

Posted by Nikhil Pawar <ni...@gmail.com>.
I could not convince myself with your third point.
Let me explain by taking a simple use case of slum dwellers in Mumbai.
In Mumbai there is one government scheme named as 'SRA' wherein slum
dwellers are given houses in building in exchange of their slums.
In between this exchange, there is a time slot of 4-5 years wherein slum
dwellers have address proof of their slums( which is not in existence now)
and are currently living in temporary accommodation( whose address proof)
they don't have.
Only in such cases it makes sense to store two addresses( permanent and
current). In rest of the cases, we would rather go with permanent address,
instead of storing two same address.
So is there still a need of storing a boolean value.Let me know your view
on this.

Regards,
Nikhil

On Thu, Jun 30, 2016 at 3:29 PM, Saransh Sharma <sa...@theupscale.in>
wrote:

> See, the flow is generic while adding addresses for the customer the basic
> flow should be,
>
> 1 Address Type as suggested by Srinivasan but it should not duplicate the
> same address type we should be able to add more, addressType as per the
> requirements once the addressType is created it should not create the same
> addressType again
>
> 2 State Type we can load it from CodeValues
>
> 3. There are some cases when the customer have same address for case like
> Permanent and Residential a boolean for sameAddressType should be
> introduced or isBoth kind of boolean should be introduced and once the
> addresses are same it should not create new address type with the following
> one,
>
> On Thu, Jun 30, 2016 at 3:20 PM Nikhil Pawar <ni...@gmail.com> wrote:
>
> > Latitude and longitude are also the attributes along with other fields of
> > the address table.
> >
> > Regards,
> > Nikhil
> >
> > On Thu, Jun 30, 2016 at 3:15 PM, Saransh Sharma <sa...@theupscale.in>
> > wrote:
> >
> > > What about geo mapping ? which enables the latitude and longitude from
> > > google maps or some other service
> > >
> > > On Thu, Jun 30, 2016 at 2:41 PM Nikhil Pawar <ni...@gmail.com>
> wrote:
> > >
> > > > Hello All,
> > > >
> > > > Please find the attached schema diagram of the proposed Address and
> > > > related configuration tables.
> > > > A quick description of the diagram:
> > > > Address table:
> > > > The fields of the address table would be configurable. The user can
> > > select
> > > > the field via field configuration table.
> > > > Rest of the fields are self explanatory.
> > > >
> > > >
> > > > On Thu, Jun 30, 2016 at 1:48 PM, Ankit Sharma <an...@theupscale.in>
> > > wrote:
> > > >
> > > >> Hi team,
> > > >> We have already made addresses - official, residential and permanent
> > as
> > > a
> > > >> standard feature of CB.
> > > >> Looking forward on this.
> > > >>
> > > >> Ankit Sharma
> > > >> Upscale
> > > >>
> > > >> > On 30-Jun-2016, at 1:42 PM, Ashok <as...@confluxtechnologies.com>
> > > >> wrote:
> > > >> >
> > > >> > +1
> > > >> >
> > > >> > It makes sense to have a standard address with minimal fields to
> > > >> support CB
> > > >> > or any other integrations and can be extended/configurable by
> > > >> organization.
> > > >> >
> > > >> > Thanks and Regards,
> > > >> > Ashok
> > > >> >
> > > >> > On Wed, Jun 29, 2016 at 6:19 PM, Nayan Ambali <
> > nayan.ambali@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
> > > >> >>
> > > >>
> > > >
> > > >
> > >
> >
>

Re: [IMPORTANT] Query regarding standard address table

Posted by Saransh Sharma <sa...@theupscale.in>.
See, the flow is generic while adding addresses for the customer the basic
flow should be,

1 Address Type as suggested by Srinivasan but it should not duplicate the
same address type we should be able to add more, addressType as per the
requirements once the addressType is created it should not create the same
addressType again

2 State Type we can load it from CodeValues

3. There are some cases when the customer have same address for case like
Permanent and Residential a boolean for sameAddressType should be
introduced or isBoth kind of boolean should be introduced and once the
addresses are same it should not create new address type with the following
one,

On Thu, Jun 30, 2016 at 3:20 PM Nikhil Pawar <ni...@gmail.com> wrote:

> Latitude and longitude are also the attributes along with other fields of
> the address table.
>
> Regards,
> Nikhil
>
> On Thu, Jun 30, 2016 at 3:15 PM, Saransh Sharma <sa...@theupscale.in>
> wrote:
>
> > What about geo mapping ? which enables the latitude and longitude from
> > google maps or some other service
> >
> > On Thu, Jun 30, 2016 at 2:41 PM Nikhil Pawar <ni...@gmail.com> wrote:
> >
> > > Hello All,
> > >
> > > Please find the attached schema diagram of the proposed Address and
> > > related configuration tables.
> > > A quick description of the diagram:
> > > Address table:
> > > The fields of the address table would be configurable. The user can
> > select
> > > the field via field configuration table.
> > > Rest of the fields are self explanatory.
> > >
> > >
> > > On Thu, Jun 30, 2016 at 1:48 PM, Ankit Sharma <an...@theupscale.in>
> > wrote:
> > >
> > >> Hi team,
> > >> We have already made addresses - official, residential and permanent
> as
> > a
> > >> standard feature of CB.
> > >> Looking forward on this.
> > >>
> > >> Ankit Sharma
> > >> Upscale
> > >>
> > >> > On 30-Jun-2016, at 1:42 PM, Ashok <as...@confluxtechnologies.com>
> > >> wrote:
> > >> >
> > >> > +1
> > >> >
> > >> > It makes sense to have a standard address with minimal fields to
> > >> support CB
> > >> > or any other integrations and can be extended/configurable by
> > >> organization.
> > >> >
> > >> > Thanks and Regards,
> > >> > Ashok
> > >> >
> > >> > On Wed, Jun 29, 2016 at 6:19 PM, Nayan Ambali <
> nayan.ambali@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
> > >> >>
> > >>
> > >
> > >
> >
>

Re: [IMPORTANT] Query regarding standard address table

Posted by Nikhil Pawar <ni...@gmail.com>.
Latitude and longitude are also the attributes along with other fields of
the address table.

Regards,
Nikhil

On Thu, Jun 30, 2016 at 3:15 PM, Saransh Sharma <sa...@theupscale.in>
wrote:

> What about geo mapping ? which enables the latitude and longitude from
> google maps or some other service
>
> On Thu, Jun 30, 2016 at 2:41 PM Nikhil Pawar <ni...@gmail.com> wrote:
>
> > Hello All,
> >
> > Please find the attached schema diagram of the proposed Address and
> > related configuration tables.
> > A quick description of the diagram:
> > Address table:
> > The fields of the address table would be configurable. The user can
> select
> > the field via field configuration table.
> > Rest of the fields are self explanatory.
> >
> >
> > On Thu, Jun 30, 2016 at 1:48 PM, Ankit Sharma <an...@theupscale.in>
> wrote:
> >
> >> Hi team,
> >> We have already made addresses - official, residential and permanent as
> a
> >> standard feature of CB.
> >> Looking forward on this.
> >>
> >> Ankit Sharma
> >> Upscale
> >>
> >> > On 30-Jun-2016, at 1:42 PM, Ashok <as...@confluxtechnologies.com>
> >> wrote:
> >> >
> >> > +1
> >> >
> >> > It makes sense to have a standard address with minimal fields to
> >> support CB
> >> > or any other integrations and can be extended/configurable by
> >> organization.
> >> >
> >> > Thanks and Regards,
> >> > Ashok
> >> >
> >> > On Wed, Jun 29, 2016 at 6:19 PM, Nayan Ambali <nayan.ambali@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
> >> >>
> >>
> >
> >
>

Re: [IMPORTANT] Query regarding standard address table

Posted by Saransh Sharma <sa...@theupscale.in>.
What about geo mapping ? which enables the latitude and longitude from
google maps or some other service

On Thu, Jun 30, 2016 at 2:41 PM Nikhil Pawar <ni...@gmail.com> wrote:

> Hello All,
>
> Please find the attached schema diagram of the proposed Address and
> related configuration tables.
> A quick description of the diagram:
> Address table:
> The fields of the address table would be configurable. The user can select
> the field via field configuration table.
> Rest of the fields are self explanatory.
>
>
> On Thu, Jun 30, 2016 at 1:48 PM, Ankit Sharma <an...@theupscale.in> wrote:
>
>> Hi team,
>> We have already made addresses - official, residential and permanent as a
>> standard feature of CB.
>> Looking forward on this.
>>
>> Ankit Sharma
>> Upscale
>>
>> > On 30-Jun-2016, at 1:42 PM, Ashok <as...@confluxtechnologies.com>
>> wrote:
>> >
>> > +1
>> >
>> > It makes sense to have a standard address with minimal fields to
>> support CB
>> > or any other integrations and can be extended/configurable by
>> organization.
>> >
>> > Thanks and Regards,
>> > Ashok
>> >
>> > On Wed, Jun 29, 2016 at 6:19 PM, 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
>> >>
>>
>
>

Re: [IMPORTANT] Query regarding standard address table

Posted by Nikhil Pawar <ni...@gmail.com>.
Hello All,

Please find the attached schema diagram of the proposed Address and related
configuration tables.
A quick description of the diagram:
Address table:
The fields of the address table would be configurable. The user can select
the field via field configuration table.
Rest of the fields are self explanatory.


On Thu, Jun 30, 2016 at 1:48 PM, Ankit Sharma <an...@theupscale.in> wrote:

> Hi team,
> We have already made addresses - official, residential and permanent as a
> standard feature of CB.
> Looking forward on this.
>
> Ankit Sharma
> Upscale
>
> > On 30-Jun-2016, at 1:42 PM, Ashok <as...@confluxtechnologies.com> wrote:
> >
> > +1
> >
> > It makes sense to have a standard address with minimal fields to support
> CB
> > or any other integrations and can be extended/configurable by
> organization.
> >
> > Thanks and Regards,
> > Ashok
> >
> > On Wed, Jun 29, 2016 at 6:19 PM, 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
> >>
>

Re: [IMPORTANT] Query regarding standard address table

Posted by Ankit Sharma <an...@theupscale.in>.
Hi team, 
We have already made addresses - official, residential and permanent as a standard feature of CB.
Looking forward on this.

Ankit Sharma
Upscale

> On 30-Jun-2016, at 1:42 PM, Ashok <as...@confluxtechnologies.com> wrote:
> 
> +1
> 
> It makes sense to have a standard address with minimal fields to support CB
> or any other integrations and can be extended/configurable by organization.
> 
> Thanks and Regards,
> Ashok
> 
> On Wed, Jun 29, 2016 at 6:19 PM, 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
>> 

Re: [IMPORTANT] Query regarding standard address table

Posted by Ashok <as...@confluxtechnologies.com>.
+1

It makes sense to have a standard address with minimal fields to support CB
or any other integrations and can be extended/configurable by organization.

Thanks and Regards,
Ashok

On Wed, Jun 29, 2016 at 6:19 PM, 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
>>
>>
>

Re: [IMPORTANT] Query regarding standard address table

Posted by Nayan Ambali <na...@gmail.com>.
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
>
>