Timeline for contact match script?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2015 at 1:50 | answer | added | Eliot Mason | timeline score: 1 | |
| Jun 17, 2015 at 1:07 | comment | added | Sonicthoughts | @JoeMurray - yes, but I think that would still require the subject matter expert to use the UI interactively - no? Was hoping to present "likely" matches in a separate list. I suppose this is an edge case anyway but thought someone may have tackled it before. | |
| Jun 17, 2015 at 1:03 | comment | added | Joe Murray♦ | Another approach would be to import remembering to tag the new contacts appropriately, then use the dupe merging facilities | |
| Jun 10, 2015 at 3:12 | comment | added | Sonicthoughts | It's filled with issues (spellings, etc.) I thought it might be good to generate a list of suggestions similar to the auto-complete widget so someone could quickly identify likely matches without having to use import forms/process. so, "Andy Hunt" would return "Andrew Hunt", "Mr. and Mrs. Andrew Hunt", etc. and the contact ID. | |
| Jun 9, 2015 at 15:20 | comment | added | Andie Hunt | What are the inconsistencies? Is it a matter of sometimes someone uses a nickname? Are there any other fields besides first name, last name, and contribution amount? | |
| Jun 9, 2015 at 14:17 | comment | added | Sonicthoughts | Also, my first attempt is using drush and api: $result = civicrm_api3('Contact', 'get', array( 'sequential' => 1, 'return' => "id,first_name,last_name,display_name", 'display_name' => "john smith",) I'm not clear on the matching logic though as it seems to be fuzzy. | |
| Jun 9, 2015 at 13:46 | history | asked | Sonicthoughts | CC BY-SA 3.0 |