| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Eileenmcnaughton | T230954 Middle name and initial appearing in first or last name fields causing lots of manual dedupe | |||
| Resolved | Eileenmcnaughton | T238606 First name field conflicts on nick name not being handled automatically (round 1) | |||
| Resolved | Eileenmcnaughton | T242159 Create UI for DS to add new resolvable names |
Event Timeline
@MBeat33 @NNichols @RLewis @LeanneS @krobinson
We just deployed a patch for this. It works off a table of names pairs (at the moment it only has the 23 listed below but the goal is you will be able to save to it) and identifies equivalent names & resolves conflicts on them. This is how it works .....
James Wales gave in 2018, Jim Wales gave in 2019
It looks up the table & determines Jim is a nick name of James. In this example it keeps Jim as the more recent name. If James were more recent it would keep that and ALSO put Jim in the nick_name field.
There is also handling for common mispelings - although only 2 at the moment. In this case it understands that one version is 'better' than the other
name_a,name_b,is_name_b_nickname,is_name_b_inferior
Benjamin,Benjamain,0,1
Richard,Rchard,0,1
Anthony,Tony,1,0
Bradford,Brad,1,0
Christopher,Chris,1,0
Constance,Connie,1,0
Elijah,Eli,1,0
Geoffrey,Geoff,1,0
Gregory,Greg,1,0
James,Jim,1,0
Jeffrey,Jeff,1,0,
Jonathan,Jon,1,0,
Mathew,Matt,1,0
Michael,Mike,1,0
Peter,Pete,1,0
Philip,Phil,1,0
Robert,Bob,1,0
Rudolf,Rudy,1,0
Samuel,Sam,1,0
Stephen,Steve,1,0
Theodore,Ted,1,0
Timothy,Tim,1,0
William,Bill,1,0
There are more patterns I can spot but this might be as long as a piece of string - perhaps we should close this out now & add new ones as they arise