Attention: This site does not support the current version of your web browser. To get the best possible experience using our website we recommend that you upgrade to a newer version or install another browser

Skip main navigation
FamilySearch
  • Overview
  • Tree
  • Find
  • Following
  • My Contributions
  • Private People
  • Records
  • Images
  • Family Tree
  • Genealogies
  • Catalog
  • Books
  • Research Wiki
  • Cemeteries
  • Overview
  • Gallery
  • People
  • Find
  • Overview
  • Opportunities
  • Your Impact
  • Indexing
  • All Activities
  • Together App
  • Surname Origins
  • All About Me
  • Compare-a-Face
  • Famous Relatives
  • Record My Story
  • Picture My Heritage
Sign In Create Account
Sign In Create Account
  • Overview
  • Tree
  • Find
  • Following
  • My Contributions
  • Private People
  • Records
  • Images
  • Family Tree
  • Genealogies
  • Catalog
  • Books
  • Research Wiki
  • Cemeteries
  • Overview
  • Gallery
  • People
  • Find
  • Overview
  • Opportunities
  • Your Impact
  • Indexing
  • All Activities
  • Together App
  • Surname Origins
  • All About Me
  • Compare-a-Face
  • Famous Relatives
  • Record My Story
  • Picture My Heritage
Skip to contentHome
  • Community Home
  • Ask a Question
  • Community News
  • Groups
  • Sign In
  • Register
  • Home› Welcome to the FamilySearch Community!› Ask a Question› Family Tree

    Glitch in Source Linker

    jlwestra
    jlwestra ✭✭✭
    December 22, 2021 edited July 16, 2024 in Family Tree

    The Source Linker is an amazing tool, but we have encountered a glitch when the Source Linker is used to add new people into Family Tree (FT). We have seen this glitch many times when looking at marriage records from the Netherlands, and when we want to add in parents of the bride or groom to FT, and when the parent has a three part name, two given names, and one surname.  When we see the person to be added to FT, in the left hand column, from the source, it shows the three part name. When we click on Add, the Source Linker brings up a box, Add to Family Tree, and populates that box with the name of the person to be added to FT. However, the name that populates in that box is not exactly the name that was found on the source. The name in the box has First Name, as the first of the two given names from the source. Then the Last Name in the box is entered as the Second Given Name from the Source. The surname from the source is not entered by the Source Linker into that box at all. If I discover this when I am adding, I can copy the full name from the source, and put it into the Add to Family Tree box. However, I might not always discover this problem, and might end up entering a name of a person into FT, from a given source, and the name that gets entered into FT is not exactly the same as the name from the source.  

    One example of this problem, so you can reproduce the problem, starts with Hessel Nauta 16 April 1843 – 11 January 1918 MBC8-H2H, who is listed as the Husband of my 9th Cousin, twice removed. This Hessel has another marriage, to Systke Reversma 1840 – Deceased LB4D-RKV. The parents of this Systke are in FT, but the parents of those parents are not. When I go to the father of Systke, Ruurd Hanzes Reversma 1810 – Deceased L1G8-8WG, I see five sources. One of those sources is for the marriage of Ruurd, in 1834, and it shows a box that says: This source has not been attached to all people found in the record.

    When I click on Unfinished Attachments, I see the opportunity to add the parents of the spouse of Ruurd. The mother shows a three part name in the source: Sydske Sydzes Schaafsma. However when I click on Add, the Add to Family Tree box has the name of the person to be added as Sydske Sydzes, and had lost the surname from the source. You can see the same problem if you try to add the parents of the groom. It is almost as if the Source Linker is trying to input names into FT, following the old patronymics naming system.

    Tagged:
    • Source Linker
    • Last name issue
    0

    Welcome!

    It looks like you're new here. Sign in or register to get started.
    Sign In
    Register

    Answers

    • Sanra
      Sanra ✭✭✭✭
      December 22, 2021

      @jlwestra

      Thank you for posting in the Community about the Source Linker glitch. Another missionary said the best thing to do would be to correct the names before Creating and attaching the record. When you click add for Sydske Sydzes Schaafsma, leave the Sydske in the first name field, and add Sydzes and Schaafsma in the last name field, because it could be the Sydzes is the mother's maiden name, and the Schaafsma is the farm name. You will then have the complete name listed when you attach the record. It might be useful to add an estimate birth date for the parents, like (about 20 years before Ruurd's birth, or 1790) to the record prior to creating it.

      We hope this information is helpful.

      0
    • jlwestra
      jlwestra ✭✭✭
      December 24, 2021

      Sanra 

      Thank you for your reply to my post about the Source Linker. What you suggest is typically called a workaround, which is often used to work around a malfunction in the software. The workaround is usually temporary, until the malfunction in the software can be corrected. In this case, it shouldn't be a difficult fix, since the Source Linker in most other cases, handles these names correctly. In this case, the name Sydzes is not the mother's maiden name. It is the father's given name with an added s, kind of like Hansen in Danish in the old patronymic naming system. The name Schaafsma is not a farm name. It is the accepted surname for the family. The name Sydske Sydzes might have been the name listed for Sydske at her birth, but the family later took on the surname Schaafsma, so Sydske would be listed with the name Sydske Sydzes Schaafsma in later records, such as her marriage, and in this document, which is the marriage of her child. In most cases, the name listed in FT records from the Netherlands is the later name, which is the case above. So it would be far better to fix the original malfunction, rather than have dozens or perhaps hundreds of patrons be forever expected to follow some vague workaround. If the programmers were to see this case, they might easily be able to generate a fix for the problem, since they could replicate this situation in testing their fix. What is the best way to get this case to the programmers? It could be sent on to the programmers, or I could resubmit this case in another category. Please let me know what I can do to make this happen.

      0
    • Sanra
      Sanra ✭✭✭✭
      December 26, 2021

      @jlwestra

      Your concern will be forwarded to a specialty team for review and resolution. You may be contacted by that team if they need more information.

      0
    This discussion has been closed.
    Clear
    No Groups Found

    Welcome!

    It looks like you're new here. Sign in or register to get started.
    Sign In
    Register

    Quick Links

    • Community Code of Conduct
    • Contact Us
    • Free Research Consultation
    • Get More Help
    • My Bookmarks0
    • My Discussions
    • My Drafts0
    • My Groups
    • Suggest an Idea

    Categories

    • All Categories
    • 42.6K Ask a Question
    • 3.3K General Questions
    • 568 FamilySearch Center
    • 6.7K Get Involved/Indexing
    • 639 FamilySearch Account
    • 6.5K Family Tree
    • 5.1K Search
    • 993 Memories
    • 2 Suggest an Idea
    • 472 Other Languages
    • 62 Community News
    • Groups
    • About
    • Volunteer
    • Blog
    • Site Map
    • DNA
    • Solutions Gallery
    • Mobile Apps
    • Contact Us
    • Cookie Preferences

    FamilySearch Terms of Use | Privacy Notice

    © 2025 by Intellectual Reserve, Inc. All rights reserved. A service provided by The Church of Jesus Christ of Latter-day Saints

    The Church of Jesus Christ of Latter-day Saints logo

    Change Language

    Recently used languages