CiviCRM Community Forums (archive)

I'm in the process of importing a large (and somewhat dirty) dataset for a large NGO.

Some of the exports list the contact as an individual "associated with" themself - their DB has a members table and a householdmembers table. Family memberships give memberships to all family members, so we've reflected that in those membershi types.

(But they don't want households as contacts, so we've kept their existing model and created a new relationship to use rather than using "Head of household is/for".)

When importing their DB, some imports would generate about 10x as many memberships as others. Investigating, I found that where a contact had been imported and assigned a relationship to themself, this would cause a family membership for that contact to be reflected several thousand times for the same contact.

Is this something worth checking for?

* Should self-relations be permitted at all in CiviCRM?
* Should memberships assigned by self-relation be granted?
* If "yes" to both of the above, then shouldn't we ensure that only one self-related membership is granted?

Can you fix the bug with my toddler too? He insists "Grandpa's not your father. He's my father, Daddy's your father"   

Not sure i understand the exact issue. Can you reproduce the not identifying duplicates on the demo server and give us the steps to reproduce that

thanx

lobo