Be able to merge LPIDs

Bug #1174526 reported by Andrew Starr-Bochicchio
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
D-A-T Overview
Triaged
Low
Unassigned

Bug Description

In LP: #1166477, we added the ability to edit people. We probably want to be able to merge people that have two LPIDs.

On Wed, Apr 24, 2013 at 4:32 AM, Daniel Holbach <email address hidden> wrote:
> On 16.04.2013 18:44, Andrew Starr-Bochicchio wrote:
>> Maybe I'm just overthinking this... The case that I'm concerned about
>> is when we need to "merge" a lpid. Uploads.objects also have lpids
>> associated with them, so the Person.object and each of the
>> Uploads.objects would need to have their lpid changed. Then we'd need
>> to update the other related objects like total uploads, etc... Next
>> we'd need to remove the row in the database for the "old" lpid. If the
>> "old" account still exists, we might need to add it to some kind of
>> blacklist to make sure the importer doesn't just create it again. We
>> get the lpid by from Launchpad using 'people.getByEmail(email=e)'
>> There's no guarantee that will give us the 'correct' one if someone
>> has the same email associated with more than one account.
>
> in the case where we override the LPID, we could potentially have a
> field called "original_lpid" which would be null, where we'd still store
> the original one in. I'm just not sure what to do if somebody changes LP
> IDs a couple of times... ho hum.
>
>
>> I don't know how many people have two LP accounts. Maybe its not that
>> many, but I was thinking that using a management command allow us to
>> do batch updating. Maybe this is unnecessary...
>
> Yeah. It'd probably take some data analysis to see if this is a concern.

Changed in dat-overview:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.