Tools for using family tree/Search: Difference between revisions

added information about why all sources even those that seem to be duplicates
No edit summary
(added information about why all sources even those that seem to be duplicates)
Line 13: Line 13:
https://familysearch.org/blog/en/common-mistakes-family-tree-data  
https://familysearch.org/blog/en/common-mistakes-family-tree-data  


==== Making Hints More Accurate ====
==== Making Hints More Accurate ====


Always accept an FamilySearch hint that is right, even when it is a duplicate because this reduces the possibility that another user will create a duplicate person to match the duplicate record. If you attach the duplicate source to the correct person, others will see your ancestor. When someone searches for a record of their ancestor, they will come to a screen that says, review match in Tree. They will see that the person is already in Family Tree If you declare it not a match they will be able to link that source to a duplicate person
Always accept an FamilySearch hint that is right, even when it is a duplicate because this reduces the possibility that another user will create a duplicate person to match the duplicate record. If you attach the duplicate source to the correct person, others will see your ancestor. When someone searches for a record of their ancestor, they will come to a screen that says, review match in Tree. They will see that the person is already in Family Tree If you declare it not a match they will be able to link that source to a duplicate person  


If this feels like clutter follow the instructions below to create a Title Source to seperate duplicate sources. Here is a sample picture. [Image:
If this feels like clutter follow the instructions How to Organize Sources: Using Title Sources to create a heading to seperate duplicate sources. <br>
https://d2r1vs3d9006ap.cloudfront.net...]


Marking correct hints as not a match damage the hinting system. You are giving the hinting system incorrect information. It says oh I [the program] made a mistake; this record really does not belong to this person so I need to revise my [the program's] methodology for finding potential source matches.
Marking correct hints as not a match damage the hinting system. You are giving the hinting system incorrect information. It says oh I [the program] made a mistake; this record really does not belong to this person so I need to revise my [the program's] methodology for finding potential source matches.  


If you mark matching duplicate hints as "Not a Match", it will degrade the ability of Hints to connect correct sources to people. We have been advised by FamilySearch personnel that this is the worst thing to do. In the future, it may not give you hints for that family member that are valid because of the not a match you declared. It also reduces the likelihood of someone else clicking "Not-a-match" by mistake.
If you mark matching duplicate hints as "Not a Match", it will degrade the ability of Hints to connect correct sources to people. We have been advised by FamilySearch personnel that this is the worst thing to do. In the future, it may not give you hints for that family member that are valid because of the not a match you declared. It also reduces the likelihood of someone else clicking "Not-a-match" by mistake.  


Finally It tells the hinting system that it is not that person. Since there are often other people in the same record (spouse and/or parent and/or child), you are telling the system that those relationships don't belong to those people, either.
Finally It tells the hinting system that it is not that person. Since there are often other people in the same record (spouse and/or parent and/or child), you are telling the system that those relationships don't belong to those people, either.  


It may seem wasteful to attach duplicate third party records when the same record is already attached in FamilySearch. But those third party records often have images attached. PLUS, sometimes they have more transcribed information. So we want both.
It may seem wasteful to attach duplicate third party records when the same record is already attached in FamilySearch. But those third party records often have images attached. PLUS, sometimes they have more transcribed information. So we want both.  


In the future there are plans to let users "bundle" duplicate sources together. Meanwhile, please attach them and feel free to create a "Title Sources"
In the future there are plans to let users "bundle" duplicate sources together. Meanwhile, please attach them and feel free to create a "Title Sources"  


==== FamilySearch Person Centric System introduces a Modern Linking Model.  ====
==== FamilySearch Person Centric System introduces a Modern Linking Model.  ====
75

edits