What is the best course of action when dealing with more than 15 duplicates? Just go through each du
Respuestas
-
Im not sure what anyone else will say
but in the end you have to merge them one by one . . .
I dont know of any short way of doing it.
HOWEVER
be very aware of records that are linked to other "supposed" family members
if you merge two records - that have different sets of children
you may be wreaking more havoc then just leaving them seperate and first making sure all the children are connected or disconnected correctly.
merging two records when one or both records don't have children attached is one thing.
but when merging records where both have spouses/wives I am pretty cautious of merging.
and please dont merge two records unless you know 100% sure they are the same.
Id rather have various orphan records around - - then have to back out a merge that didnt quite end up as you thought.
realize you are merging more than just that one person - you are also bringing together all the connected family also (spouses, children ect.) so unless all those connected family really do belong together - then I wouldn't merge them together - until this extended family can be rectified.
I have seen too many merges end up doing more damage than what they were trying to solve.
0 -
Yes, I agree that they should be done one by one. This will help with accuracy.
0 -
[ be sure and click "expand post" to see full post ]
I have some pretty strong feelings about the merge process - both in seeing that needed merges occur - but also noting the negative impact that bad merges can have and be hard to fix.
So I took some time to compile 16 tips to consider when merging duplicate records.
I am all for merging duplicate records! 😃
But I cringe when bad merges happen just because people were careless or didnt see the true impact.
Here are some tips of mine:. The intent is NOT to discourage people from doing merges.
The intent is for people to think and analyze the impact of a merge before they do it.
Things to keep in mind when merging two individuals in FamilySearch
1) FamilySearch does show "Possible Duplicates" - the emphasis there should be "POSSIBLE"
Dont assume they are the same. and dont merge them without doing "your homework" to know they are the same and the remaining information is correct as can be known.
2) Realize that FamilySearch Family Tree is a collaborative database.
Anything you do will impact what other people do and see.
Anything you do potentially can impact for good or for bad-0 the work other people are doing.
3) Be patient and analyze the records well before merging. Dont be too much in a hurry and don't be careless when merging records.
you can easily wreak havoc on the work of others in doing a bad merge.
4) Realize that you aren't just merging what you perceive as duplicate individuals - but rather you are potentially merging two families together.
Consider the following scenario. Johh Doe (1800-1850) is recorded twice in FamilySearch. But, one record has one set of parents and children
and the other record has a different set of parents and children. If you merge these two records you will have one person with all the previous children and two sets pf parents. Consider the real possibiliity that even though the birth/death dates may be an exact match - that actually someone before you has attributed the wrong birth date to one of the duplicates (because they were confused about the persons identity)
Be very cautious of merging two duplicates where both sets of records have (different) spouse or children.
5) Just because two people have the same birth and/or death date doesn't always mean that they should be merged (due to what was discussed in the previous item)
6) When you have conflicting vital information between the two records - do a little bit of research as to what information appears to be more accurate.
7) When you have two records you need to merge - do you understand the difference of whether you start with record 1 and merge with record 2
or start with record 2 and merge with record 1. Have you noted the "switch position" option in the merge process? Do you understand the impact of switching position"? Do you understand how to choose the remaining correct info when there is correct info from both sides of the two records?
If you don't understand this - consider having someone more experienced to do the merge.
8) Make contact with others researching the family (past submitters of info to these two records) and see if they agree with you on how the records should be merged.
9) In many cases duplicates exist because one record is still marked as a "living individual" and one record has a death date (is deceased)
FamilySearch keep track of records for living persons in a totally different way that it does deceased persons. If you see a child of a set of parents duplicates - but one is marked as living and one is marked as deceased (and if you know the death information is correct) then first update the death information on the one that is missing - and then you will be able to merge the two (FamilySearch does not allow merging of live with deceased persons)
10) In some cases it appears that FamilySearcg has a different set of parent records for each child in the (same actual) family.
This may occur for records that were created decades ago where family relationships were not all tied together before the temple work is done.
Usually this type of scenario will be straight forward - but tedious in the merge process.
11) In some cases two different people with the same name - but married to two different spouses and were actually two different people - have been mistakenly merged together. if a good amount of time has gone by (and other people have since made other changes) backing out the merge may not be easy or possible.
Rather you may be forced to create a new record for one of the pre-merged persons.
12) Dont just assume that two children by the same name and same set of parents were actually the same person.
Especially in earlier centuries - child mortality was much higher - and it was not uncommon to find multiple children given the same name - having siblings with the same name who had died before they were born.
13) Be much more cautious of merging people with common names (such as John Smith) that could really be two different people - as compared to people with unusual names (such as Herbert Simone Allizoni).
14) Its good to know how to do a merge - if you have never done one before. But start out with very straightforward merges.
Straight forward merges could include:
a) duplicate children where one is marked as deceased and one as living.
b) duplicates where one of the records is not hooked to any parent or child. (an "orphan record") - but where dates or other info make it obvious they are the same person.
c) duplicates both hooked to the same exact set of parents but no children or spouse involved for one or both of the duplicate records.
15) Don't just focus on the two records being merged. Before and after the merge - look at all the interconnected relationships and see if they need merging also.
but dont do a complex merge like this without analyzing all the needed merges ahead of time. Write down the FamilySearch identifiers (ID's) ahead of time for all the people involved.
16) Don't assume just because two people have the same name, same birth year and same spouse first name - that they must be the same person. Way too many people have wreaked havoc on a set of data - because of this mis-assumption.
0 -
I agree with Dennis in all of his points. I have made it a rule for myself and I teach that when a merge needs to be made, begin bottom then move up. If there are children that need to be merged (assuming the merge meets all other criteria) do the kids first before parents or grandparents.
0 -
great point.
0 -
I put the tree to show all the generations clearly. So can see spouse of children too.
Also agree with others.
0
