Hmm. Then I think... citizenship might be better modeled with an entity like PartyCitizenship or
PersonCitizenship, where to primary key would be [partyId, citizenship]. Something like that.
It never occurred to me that a Person can have more than 1 citizenship! Thanks.
:)
Jonathon
stodorov wrote:
yes, Jonathon.
I think this is the right way, to create <extend-entity> to include
Nationality and Language.
I mean to say, Nationality like child's place of birth or bloodline. This is
personally for all life and can not be changed.
I not mean citizenship. A citizenship can be changed or one person can have
two or more citizenships. In this case concactmech with purpose is better
idea.
But in different country, citizenship and nationality can be different means
or they can be the same.
I think to use <extend-entity> and to include this fields.
Thanks!
jonwimp wrote:
Contact mechs are used for contact mechanisms. Doesn't direct tie/relate
to a Person.
While it could be possible to attach "language" to a contact mech, it'll
be weird for a Person to
have say Mobile Phone A on which only English can be spoken and Mobile
Phone B on which only
Spanish can be used. This is still valid, though, for a PartyGroup that
has various contact mechs
in different countries/locales speaking different languages.
Language and Nationality are best tied to the Person himself/herself, not
to the Person's contact
mechs.
Jonathon
BJ Freeman wrote:
somebody can correct me if i am off base.
I think you you can use the contactmech type and purpose for this.
Stanimir Todorov sent the following on 9/10/2007 3:25 AM:
Hi all,
I am a novice in Ofbiz. This is the best project :)
I have a question about Person. I need to put Person Language and Person
Nationality, but I don't find the way during creating a Person.
May be, this is good idea to add this functionality in Ofbiz entities
(Person) like fields Language and Nationality.
I am not sure if this is the right way?
I need of suggestion and I will be glad to help about this.
Thanks!
