Advice to merge unsafe

ChrissyM

Although the individual tagged as a merge had no surname, date or place of birth, and the husband's name was slightly different, plus the child was christened in a different area from the other children, I was advised to merge because of no significant differences. The lack of information made the merge unsafe, especially as it is a common surname for the general area. I think lack of information should be taken into account when judging a merge.

Rhonda Budvarson

@ChrissyM thank you again for your feedback :)

Gordon Collett

This sounds like a great example for the developers to closely asses. You should post the two ID numbers so that they can look at both profiles and see if the routine made a mistake in saying it was fine to just charge ahead with the merge or if the analysis was looking at such a large amount of information on the extended family that the merge really was fine.

When you evaluated the situation, what was your conclusion? Was the program correct and you went ahead and merged them? Or did you see that the merge was incorrect and you marked the two people as not a match?