Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Reducing the rate of increase of duplicates in FSFT

I am a Stake Temple & Family History Consultant, member of the staff at our stake Family History Center, and I teach a family history class in my ward, so I get a lot of contact with people trying to do good family history research on their ancestral lines. I am getting more and more complaints about others uploading large files by GEDCOM that creates lot of duplicates that have to be sorted out and merged in order to have a clean, well documented tree. I have an idea that would help resolve this problem without putting restriction on uploading GEDCOMs.

There are an enormous amount of duplicates already in FSFT. I have been keeping track of the duplicates I find in my research over the past 3 years and I find over 40% of the people I research in FSFT have one or more duplicates and I don't want that number to go any higher.

My idea is to create a holding folder that uploaded GEDCOMs would be put into, with a separate holding folder for each patron that does an upload, similar to what is done with memories gallery. The patron would have to use the procedure used for adding a new person to FSFT, to add the individuals from the GEDCOM, one at a time to FSFT.
3 people like
this idea
+1
Reply
  • 2
    WikiTree essentially does something like this. In a nutshell, you can run an extensive comparison process on your GEDCOM file. This generates a report from which you can add new people one at a time, using the same procedure as you'd use "longhand", except with the fields pre-populated from your file (reducing the number of errors introduced as typos). Your report stays available as long as you don't go longer than 45 days without looking at it.

    But all of this is predicated on a functional comparison process that actually finds the duplicates (without burdening the user with too many false positives). Currently, FS is missing such a process: neither the "possible duplicates" routine on existing profiles nor the "compare and add" function on imported GEDCOMs can be relied upon to find even the most obvious matches. I find 99% of my duplicates via record hints, not with "possible duplicates". Therefore, the "holding file" idea is premature on FS: first, they need to fix the comparison.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited

  • This reply was removed on 2018-05-16.
    see the change log
  • I do not believe that this would fix the problem I had with indexing a batch. Apparently someone had worked on the file before me and I was supposed to check the file. There was a page 2 with only part information, like a picture of one half of a page. Other than a list of names there was no useful information. On the next picture, there was the remainder of the first page labeled 2B. By jumping back and forth between the pictures, you could do some of the names. There were at least five other pictures of a similar combination. I sent the batch back because it was too much to manage.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. sad, anxious, confused, frustrated kidding, amused, unsure, silly indifferent, undecided, unconcerned happy, confident, thankful, excited