Merges not working correctly

[shevett]

Merges don't work as they should; when accounts are merged, the disabled account still holds on to the email address, which makes logging in a problem. One example of this behavior is listed below.

Here's what we'd ideally like to see when merges happen:

Copy all data from to-be-disabled account to correct account. [this is not happening currently] Any data that is an exact duplicate (e.g., both accounts have the same street address) can be overwritten. Any data where the field is populated in both accounts but is not an exact duplicate (e.g., two different email addresses) should be treated thusly: -- no data should be deleted from the to-remain-active account, -- the data from the newer account should be marked as primary, -- the data from the older account should be marked as not primary. Note that "newer" and "older" apply regardless of which direction the account is being merged. I.e., whether we're merging into the newer account or into the older account, the newer data should be considered primary. Once the copy is complete, ALL data should be deleted from the to-be-disabled account, to prevent disabled account errors when people try to log in. [this is not happening currently]

I don't know how feasible that is in Congo; if you can't make it do exactly that, at least make sure all data is properly wiped from the disabled account so people can log in.

Thanks, -- Josh Rachlin (wearing my Arisia Registration hat, not my Intercon Ops hat, though there's no reason Intercon's version of Congo shouldn't also work this way)

Example disabled badge numbers that still have associated email addresses: 100423 100486 100342 99965 (sort of; it looks like this one was half-fixed by Kathryn)

I can come up with more examples if you need me to.

[shevett]

Imported from trac issue 315. Created by intercon on 2013-10-24T11:53:06, last modified: 2014-01-07T16:55:37

[shevett]

Josh and I discussed this over the weekend. The email merge issue is defeinitely hot.