I'm new to Geni, uploaded a Gedcom with just my ancestors. Got a message about a potential merge (which apparently affects further uploading of that branch of my gedcom). What concerned me was that, while it almost certainly was the same person, the other (existing) tree had significant incorrect information. This particular ancestor I'd spent quite a bit of time researching, so it wasn't just a matter of personal opinion.
I declined to make that match; not sure that was the right thing to do, but it seemed like at best the "merged" person would contain much of that incorrect information. I saw no way to attach any sort of quality ranking - the only alternative might have been to contact the person with the other tree and point out the incorrect data.
What is the right course of action here? And is there any mechanism to tag incorrect data? I'd want to do that and be able to attach source materials, etc., but not necessarily have to spend the time to get into an extended debate.
Since that one case I've seen a few others pop up; often close enough that I'd say "OK" to the match, even if the other data had issues, some easily recognizable (dropping a leading "Johann", not uncommon in PA Germans, some obvious typos, etc. - essentially minor errors, not substantial ones like the first case.) Any thoughts/comments appreciated.
Date
Votes
2 comments
-
Clancy Elizabeth Matthews This also happened to me. The profile the person merged to in my tree is clearly a different person with a different maiden name, parents and siblings. I never agreed to the merge and responded to the person concerned to explain why and the differences. Regardless, it seems to have been facilitated by a Geni curator merging the profile earlier for another individual and making them a profile manager. I'm no longer a Pro subscriber and unable to undo the merge or request assistance via a ticket to have it correct it back. I agree there should be a mechanism to tag incorrect data and it should remain accessible to original profile managers regardless of whether they have a current Pro or Premium subscription or not.
-
MD, FACP Stephen Bruce Strum Totally agree that when viewing what is clearly the same person in someone else’s tree that I have no apparent recourse to address misinformation the other person may now be “importing” into my tree as a result of a merge. I am also a MyHeritage user and that site handles this issue by itemizing the key findings in each of the parties involved when there clearly is a match. I want a quality family tree and there needs to be a way to address wrong information in a merge, or even accepting a match.
Please sign in to leave a comment.