Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Merging People in FamilySearch Family Tree - Presentation

5,627 views

Published on

This is a presentation originally given at the 2013 BYU Conference on Family History and Genealogy and again with updated content for a presentation at the 2017 BYU Conference on Family History. This presentation helps users become more familiar with and successful using the merge-related features of FamilySearch's Family Tree.

Published in: Technology
  • Ben, I just realized what a neophyte I am at this slideshow thingy. Obviously, if there were sounds, it would be on youtube; is that correct? I still think it's a little dry, though. No personal animus intended at all; I wish I had been in a position to attend your presentations in person.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • I would have enjoyed (or gotten more out of) the presentation if there had been a vocal accompaniment. Or, perhaps, stick figure illustrations? The info is good but a little dry..
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Merging People in FamilySearch Family Tree - Presentation

  1. 1. © 2013 by Intellectual Reserve, Inc. All rights reserved. Merging People in FamilySearch Family Tree BYU Conference on Family History and Genealogy July 27, 2017 BYU Conference on Family History and Genealogy July 31, 2013 Riverton FamilySearch Library Saturday Seminar October 19, 2013 Family History Support Missionary Training November 13, 2013 Sandy Crescent Stake Family History Training February 20, 2014 Ben Baker bakerb@familysearch.org
  2. 2. Background • Over 7 years as a Software Engineer at FamilySearch • Initial implementation and responsibility over merge- related features with continued interest in tracking trends • Try to do my own genealogy and help others • I’m here to learn from real users of our services • Hope I’ll be able to help you today • E-mail me (bakerb@familysearch.org) to get a copy of this presentation or for specific merge-related problems • Click here for the related printed handout materials
  3. 3. Why Merging is Necessary
  4. 4. Lots of Inputs + Imperfect Patrons + Imperfect Algorithms ≈ Lots of Duplication Ancestral File Record Extraction Family Tree More …
  5. 5. What Merge Is • Removal of a duplicate copy of the same real person • A way to choose the best conclusions to improve the data on the resulting merged person What Merge Is Not • An all-purpose clean up tool to get rid of data you don’t like • The same as deleting a person • The same as a new.familysearch combine
  6. 6. Delete Person Deleting a person will delete all relationships that person was in, orphan any LDS temple ordinances and won’t keep a link to the real person. Use with care! Only recommend using when you’re sure the person is fictitious (Ex. wrong gender) Often, a relationship should be deleted or a merge should be done. Man Wife WifeMan
  7. 7. new.familysearch Combine Family Tree Merge A B A B A B A’ B Merging B into A will delete (archive/tombstone) B, potentially changing A with some of B’s data. Combining B into A will result in A with B as an “inner person” of A. Data from both persons is preserved and can be selected as viewable values.
  8. 8. Merge Process Overview
  9. 9. Review the persons in the list and take an appropriate action: 1. If there are people in the list that look like they may be the same real person, click on the Review Merge button to see more details 2. If you’re pretty sure a possible duplicate is not the same real person, click on the Not a Match link and enter a reason why you believe this is not the same real person. 3. If a person shows up in the “Can’t Be Merged at This Time” list, a constraint is preventing the merge.
  10. 10. Terminology for Persons in Merges • Surviving person • Resulting person • Person merged into • Left hand side of merge page • This is the person that will remain when the merge is completed and whose data is changed as specified with data from the second person in the merge. • Duplicate person • Deleted person • Archived person • Person merged away • Right hand side of merge page • This person will be deleted (or archived or tombstoned if you prefer those terms) during the merge. • There will be a pointer or forwarding ID that points to person 1 so you will know where the "real" copy of the person is, but this second person will no longer be active in the system.
  11. 11. Merge by ID
  12. 12. What is automatically copied during a merge? 1. Photos 2. Stories 3. Documents 4. Notes 5. Watches 6. Not a match declarations 7. Discussions 8. LDS Temple ordinances Insider Tip Use beta.familysearch.org to test hypotheses regarding what does/doesn’t occur during a merge. There is an out of date copy of data on production (familysearch.org) there. Note: Dismissed research suggestions are cleared on the resulting person after a merge.
  13. 13. Star Ranking Levels Possible Duplicates Screen • Shows 3-star and above matches • Estimate 92% of persons presented are real matches • Estimate 97.4% of all real matches are being presented Temple Reservation Check • Will flag if there are any 4-star and above matches • Estimate 99% of persons presented are matches • Estimate 89.5% of all real matches are being presented • Doesn’t show unmergeable persons
  14. 14. Star Ranking Levels cont. 5-star – Estimate 99.76% are real matches 4-star – Estimate 93.25% are real matches 3-star – Estimate 51.13% are real matches 2-star – Estimate 2.73% are real matches 1-star – Estimate 0.24% are real matches Saw huge drop in Not a Match declarations when 2-star matches were eliminated from results several years ago.
  15. 15. Star Ranking Advanced Insider’s Tips If you really want to see all of the possible duplicates a person has, including those below 3-stars, you can get them by going to the following URL after logging in. Substitute the person ID of the person you’d like to see the possible duplicates for. You can vary the matchThreshold if you really want too. https://familysearch.org/tree-data/match/by-id/{personId}?matchThreshold=1.0 If you want to see more information about how well two persons match, their match score in both directions (which may be different), merge constraints, and not a match declarations, enter the following URL after logging in. Substitute the person IDs of the two persons you are interested in. https://familysearch.org/tree-data/match/score/{personId1}/{personId2} ** WARNING** Both of these will give you back data in a “ugly” computer format called JSON. To make it a bit more human readable, Google for a JSON formatter which you can paste the result in to make it more readable. The one I usually use is http://jsonviewer.stack.hu/.
  16. 16. June 27 is a special day 1844 – 2002 – 2016
  17. 17. Before Family Tree Database Family Tree Web UI Family Tree Mobile App Partner Products … Family Tree Web UI Family Tree Mobile App Partner Products … Family Tree Database new.familysearch Database After
  18. 18. Top constraints preventing merges 1. Relationship with read only persons (locked relationship) 2. Too many inner persons 3. LDS ordinances not available and other access controls 4. Other order only – Must preserve membership 5. Multiple church membership records (CMIS) 6. Read only (locked) person 7. Merging would cause loop (nFS) 8. Gender mismatch 9. Parent and child 10. Other nFS related constraints 1. Will force merge direction to preserve read only relationships Still can’t merge if both persons share same read only relationship. 2. No longer a constraint 3. Can merge many – ordinances still not available 4. Order no longer required to preserve church membership 5. All church membership records preserved 6. Still can’t merge 7. Mergeable if no loop in Family Tree 8. Still can’t merge 9. Still can’t merge 10. Many will be mergeable, but some may not be until new limits are addressed
  19. 19. Individuals of Unusual Size (IOUS) Are No More Prior to June 27, 2016 many persons could not be merged because the result was too large for the system. This is no longer an issue and has permitted many gateway ancestors to be properly merged. Another huge benefit of the new system is vastly improved speed to merge, unmerge and restore. Prior to June 27, 2016 some operations on large persons took over 5 minutes to complete and would time out.
  20. 20. New System Limits Most commonly seen preventing merges Number of person notes – 50 Number of sets of parents – 50 Number of conclusions – 200 Number of children – 400 Number of couple relationships – 200 Other system limits Length of note – 10,752 characters Total length of all person notes – 215,040 Number of relationship notes – 12 Total length of all relationship notes – 129,024 Total length of all person and relationship notes – 376,320 Number of person sources – 200 Number of relationship sources – 50 Number of memories – 1000 Number of person not-a-matches – 400 Number of discussions – 20 Other internal data limits will result in a generic message
  21. 21. Merge Constraints and Limits Merge Constraints Limits Merge Constraints and Limits Constraints Preventing Merges Locked Relationship Locked Person Gender Mismatch Different Spaces Parent and Child All other Limits Preventing Merges Note Count Parents Count Conclusion Count Child Count Couple Count
  22. 22. A Bunch of Interesting Metrics From April - June 2017 Average number of merges/day – 53,485 Average number of unmerges/day – 249 Average number of restores/day – 281 Number of merges undone by unmerge or restore – 1 in 103 Back in new.familysearch, 1 in 4 combines were undone with a separate Percent increase in merges/day compared to 2016 – 1% Compared to 22% increase from 2015 to 2016 Other operations continue to increase much faster than 1% year over year June 2017 Percent of possible duplicates displayed that are mergeable – 98.3% and rising Average number of possible duplicates displayed – 1.3 and falling Number of persons visited with 100 or more duplicates – 164 and falling All Time Metrics Maximum merges in a day – 82,762 on April 2, 2017 Most merges by the same patron in a month – 13,188 in Jan 2017 Most merges involving the same person in a month – 413 in April 2017
  23. 23. How to Undo Incorrect Merges
  24. 24. Two Ways to Restore After a Merge 1. Unmerge • Undoes all merge changes, restoring both persons to the pre- merge state • Can currently only be done if no changes have taken place on either person since the merge • To unmerge, click on the Show All link in the Latest Changes box to the right of a person who was merged into. Then click on the Unmerge button and enter a reason for the unmerge. 2. Restore Person • Restores the person who was deleted to the pre-merge state, but leaves the merged person alone • Is only option if changes have taken place since the original merge • To restore a person, bring up the deleted person page and click on the Restore Person link.
  25. 25. Best Practices
  26. 26. Merge the person with less data into the person with more data • Will result in less changes in the change history • Copying data from the deleted person won’t result in many changes attributed to you • Is more likely to execute quickly and less likely to have an error because there are fewer operations being performed
  27. 27. Resist the impulse to remove data you don’t like (during merge and otherwise) • The current best course of action is to clean up the person as best as possible to represent a single real person. • Making these changes outside of a merge allows for better documenting of the reasons why changes are taking place.
  28. 28. Copy all data unique to the right hand side, unless you know it is not correct • My opinion is that relationships and sources should always be added (copied) on a merge • Not copying data will result in it no longer being active in the tree • Not bringing relationships over can make holes in other patron’s trees and reduce the likelihood of true matches showing in Possible Duplicates. • I believe if you really don’t want a relationship or source on the resulting merged person, you should delete it before or after the merge with its own justification.
  29. 29. Collaborate with other users • If you see people doing merges that don’t make sense, help them understand what they did wrong in a kind way • Call support if there are problems with “merge wars” • You can also use Report Abuse to report users who are destroying data
  30. 30. Specific Examples and Frequently Asked Questions
  31. 31. The core question to always ask is: “Are these two persons the same real person?”
  32. 32. Common Scenarios 1. I see some children belonging to two parents and others belonging to a single parent with the same ID as one of the coupled parents • This is actually not a case for merging • The first thing to do is make sure all of the correct children appear under the couple. If any don’t, you need to add a relationship from the child to both parents. • Then go and delete the single parent relationships to each child 2. The same spouse, child or parents a person already has appears on the right on a different line of the merge page when I’m choosing what to Add/Replace/Reject. • Make sure you add (copy) the relationship to the merged person • This is likely another duplicate that also needs to be merged 3. See Additional References in syllabus for additional scenarios
  33. 33. Question Why can’t you give an indicator as to whether there are any possible duplicates on a person? Answer The call to check for possible duplicates uses a fair amount of system resources, so we don’t want to do this every time a person page is opened. We are looking into ways to speed this up and/or provide better mechanisms to let patrons know when possible duplicates exist.
  34. 34. Question Should I mark a person as Not a Match if I’m not sure they are the same person or not? Answer It depends. If you’re worried about other people merging them and want to do more research it may be a good option, but remember Not a Matches will not appear as Possible Duplicates.
  35. 35. Question What if I know a person matches, but doesn’t show up in the possible duplicates list? Answer After clicking the Possible Duplicates link from the person page, click on the Merge by ID tab. Copy the ID you would like to merge into the text box and proceed with the merge as usual.
  36. 36. Question What happened if I went through all the steps to merge, clicked Finish Merge and I get a pink message that these persons can’t be merged? Answer Most likely you have encountered a bug. Please call support to report it.
  37. 37. Question What if I get a pink message after trying to unmerge or restore a person? Is that an error too? Answer Yes, most likely. Please follow the same steps as listed in the previous question.
  38. 38. Question What happens to LDS temple ordinances during a merge? Answer Any ordinances on the person deleted by the merge are automatically copied to the resulting person
  39. 39. Question What happens to photos and stories attached to a person during a merge? Answer Any photos and stories on the person deleted during the merge will be copied to the resulting merged person.
  40. 40. Question How do I mark a person as Not a Match if they don’t show up as a Possible Duplicate? Answer Enter the Person ID as if you were doing a Merge by ID and then click the Not a Match link.
  41. 41. Additional References to Learn More
  42. 42. FamilySearch Help Center Enter “merge” as a search team in Frequently Asked Questions on https://familysearch.org/ask/#/tree/
  43. 43. Duplicates in Family Tree Presentation https://familysearch.org/ask/learningViewer/31
  44. 44. The Family History Guide http://thefhguide.com/project-1-family-tree.html#goal-11
  45. 45. Additional Q & A

×