Identify bakery orphaned accounts on association.drupal.org

Amazon - November 4, 2009 - 17:49
Project:Drupal.org infrastructure
Component:association.drupal.org
Category:task
Priority:normal
Assigned:Amazon
Status:active
Issue tags:DrupalconSF
Description

We are about to do a massive import of profile information from the last 4 drupalcons into CiviCRM. We would like get a.d.o and future drupalcon user accounts synced with Bakery.

By identifying orphaned accounts and merging in Drupalcon profile data we can see if it's possible find the unique keys(drupal.org username and email) necessary to use Bakery.

Kieran

#1

David Strauss - November 4, 2009 - 18:10

Subscribing.

#2

Amazon - November 23, 2009 - 04:22

We did an initial export of 3300 contact records.

Josh did some analysis and concluded that 1400 of the user accounts and profiles had matching usernames and emails.

We need to figure out if we can improve the ratio of unique Drupalcon profiles that can be imported to the new Drupalcon site.

#3

deviantintegral - November 23, 2009 - 17:15

Tagging.

#4

David Strauss - November 23, 2009 - 17:48

I stand by my opinion that we should not be importing accounts into new sites. We should let Bakery create them. We're just asking for account mismatching by attempting to pre-populate a site with "matched" accounts.

#5

Amazon - November 23, 2009 - 18:35

Just so I am clear. We took 3300 unique drupalcon accounts and profiles. We compared these accounts against drupal.org user table. We determined that 1400 had matching username, and emails.

If we have 1400 matches, are we still going to have the problem of account mismatching?

#6

deviantintegral - November 23, 2009 - 19:53

@davidstrauss, the user name -> civicrm profile code is in sites/all/modules/civicrm_drupal_username_sync, and the script to sync accounts before installing the module is in sites/all/modules/civicrm/bin/DrupalUsernameSync.php.

#7

Amazon - November 23, 2009 - 20:09

The problem with the current set-up is that we aren't validating that the username is a valid drupal.org username and that a particular email is the drupal.org email.

So until we get that auto synced with CiviCRM we aren't going to be able to easily sync with future drupalcon sites, including dcsf. We won't be sure the profile information on dcsf is a match with CiviCRM profile info.

@davidstrauss if you've got some thoughts on how to force that username and email sync with bakery validated logins that would be helpful.

 
 

Drupal is a registered trademark of Dries Buytaert.