Thanks, everyone for your inputs. Nicolas, Yes, we can manage things with PartyClassification to maintain time span of it as well, it brings some complexities to handle now, as a party can be in multiple classifications on the same time, etc etc, maintaining PartyRelationship is a high-level idea, I liked it :)
Currently, I think we can go with managing the *current* marital status of the party, as we all have experienced during surfing the web, which can be achieved by Enumeration thing. -- Best Regards, Suraj Khurana TECHNICAL CONSULTANT mobile: +91 9669750002 email: [email protected] *www.hotwax.co <http://www.hotwax.co/>* On Wed, Apr 10, 2019 at 11:54 AM Devanshu Vyas <[email protected]> wrote: > +1 > > Thanks & Regards, > Devanshu Vyas. > > > On Tue, Apr 9, 2019 at 12:51 PM Suraj Khurana <[email protected]> > wrote: > >> Hello, >> >> Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* >> entity. I think we can enhance it and make it derived from *Enumeration* >> pattern. >> >> *Classification of legal marital status* >> >> - 1 - Married (and not separated) ... >> - 2 - Widowed (including living common law) ... >> - 3 - Separated (and not Divorced) ... >> - 4 - Divorced (including living common law) ... >> - 5 - Single (including living common law) >> >> Please share your thoughts. >> >> -- >> Best regards, >> Suraj Khurana >> TECHNICAL CONSULTANT >> mobile: +91 9669750002 >> email: [email protected] >> *www.hotwax.co <http://www.hotwax.co/>* >> >
