Cimballi wrote: > Not sure about the original idea, but from my point of view this helps > to know what kind of contact mech is behind the purpose type. > For example, if you have a party and you want to get its primary email > contact mech, you search for PRIMARY_EMAIL and you know you will have > only emails (well, if you didn't mess up everything... :-). > If it was only PRIMARY, it could be any kind of contact mech, you > would then have to go through the list to retrieve the contact mech of > type email.
There is a view to handle that. > > Maybe another solution would be to have hierarchical types, so you > would have PRIMARY and a child PRIMARY_EMAIL, and looking for PRIMARY > would return PRIMARY and PRIMARY_EMAIL. PRIMARY_EMAIL and PRIMARY_LOCATION are not normalized. You know it is already an EMAIL_ADDRESS or a POSTAL_ADDRESS, by looking at the associated ContactMech.contactMechTypeId field.
