My Contributions - A category for merged duplicates
I realize you don't want to promote random merging which results in mashed up people. However, it would be nice to know that we improved the family tree from the "Great 2012 Upgrade" which included SO MANY DUPLICATES based on the prior thinking of on extractions etc.
We've come a long way baby since that time. As a FHC consultant, I am spending a considerable amount of time merging profiles spawned by various records and I'd like to know how well I'm doing with out tracking it myself and loosing focus on the real purpose of the work.
Thank you for your consideration
Director, Redmond ONSITE Family History Center
Director, Sammammish Valley VIRTUAL Family History Center
Advisor, Kirkland ONSITE Family History Center
Paul W ✭✭✭✭✭
I have raised this issue (over the years) on a number of occasions. Usually, when I have been overwhelmed by the number of merges required to fix the issue you mention. When a couple has, say, twelve children and they were carried over to Family Tree with twelve IDs for the father and twelve for the mother, it has seemed like work that might have been avoidable!
However, I have received the response that there was no other way to add these individuals (with multiple IDs) to Family Tree (in 2012), given the way the records had been indexed in earlier programs.
I have come to accept the reasoning behind the fact that there could not have been a way of merging the IDs before they came into Family Tree, but it is still exasperating to encounter this issue - especially when, in some cases, the records themselves were duplicated: meaning, instead of, say, 12 IDs per parent to merge, there might even be 24 - in addition to the merging of the children's IDs!0