upload image

GEDCOM Changes

Privacy Level: Open (White)
Date: [unknown] [unknown]
Location: [unknown]
Profile manager: LJ Russell private message [send private message]
This page has been accessed 99 times.

Trying to understand the GEDCOMpare Process and what makes a good WikiTreer is at the same time is just too darn hard for most folks if not all. You have to be acquainted with WikiTree before you can import via GEDCOMpare.

A member wishing to load by GEDCOMpare should have a minimum time on WikiTree and a minimum of manually created Profiles. I am not sure how to get away from having someone like a Leader check that they created the Profiles in an accepted manner. This would still need to be figured out.

Now bear with me because this is where the fun starts. Most of the problems with new users trying to add by GEDCOMpare is their files are way too large to start with If I remember correctly, the old system would not let you add anyone if there where more than 500(?) Suggested Matches per file. Also, you could not have more than 10(?) Confirmed Matches or you were stopped from adding as well. Why, to decrease the amount of errors, especially duplicates.

Another big problem was folks started just clicking on Rejected just to get through their file as fast as they could, hence a bunch of duplicates. So GEDCOMpare was built to basically force or ensure folks to really compare possible Suggested Matches in a very user friendly format. Since it was made more user friendly, as well as system friendly, these restrictions were lifted. And this did away with as Ellen pointed out, the inordinate amount of merges that were being proposed. But the problem still is, people still want their names added NOW! And since there are no restrictions on how many you can import from a single gedcom file and with the time it takes to go through the Compare Process before you get the Add button, which psychologically is the Golden Ticket, frustration abounds.

Now back to my fix. It seems the biggest problem is the size of the files that are being loaded especially by new WikiTree Members . Gedcom files have a numbering system built into the file specifications to facilitate links between family members. So we get P. 1, P. 2 up to P. ##### whatever. Could we build the GEDCOMpare process so that the first time you use it, only the P.1 through P. 25 rows appear in the GEDCOMpare List. This gives the first time user a taste of what is to come and is a nice training session. When completed a new button will appear or become available down near Refresh that maybe says Continue. This will then in essence perform a refresh of the file, but now the rest of the file appears.

Now if this possible to limit the amount of rows seen by using the gedcom file numbering system, could we not then limit the amount of rows seen overall. OK, someone hits Continue and like a Refresh, it warns this may take some time and check your GEDCOMpare Page later. Now, when it is done, the GEDCOMpare List can only show say 300 names at a time. So now it would only show P. 26 to P. 325. To carry this a step further, each group of 300 rows would have its own GEDCOMpare List available. So say someone uploads a file called MyFile.ged with 1,896 names. The first Learning Page would show up as MyFile 1. After the Continue Button is applied they would see MyFile 1 MyFile 2 My File 3 up to in this case MyFile 7. Each one is its own entity to be worked on. Part of the GEDCOMpare Certification Training would ensure that they complete them in order. Though functionally, you should be able to work on MyFile 7 first and go backwards if you were so inclined. What is done on one does not affect another.LJR.

I am not suggesting any change to the actual GEDCOMpare Process in each list, they are just shorter versions. The user would still perform all the standards operations in each GEDCOMpare List as if they were looking at the whole file. It just breaks it down into easier to manage and complete sections. They perform all of the Compares of Suggested Matches in the first List. Get their Add button faster and finish that section of their file before they move on to the next section or List Page.

The GEDCOMpare Page would still list all uploded GEDCOM Files. When you click on the name,

GEDCOM ID: File Name Uploaded Status Last Edited
459865: MyFile.ged 31 Aug 2018 Ready 11 Sep 2018

a new intermediary page will appear that lists the separate files attributed to the main file.

459865: MyFile.ged
Report List Name Created Status Last Edited
MyFile 1 31 Aug 2018 Completed 8 Sep 2018
MyFile 2 31 Aug 2018 Ready11 Sep 2018
MyFile 3 31 Aug 2018 Waiting
MyFile 4 31 Aug 2018 Waiting
And so on.

The user then chooses the file from here to get the GEDCOMpare List Page with all of the Compare Box and Add & Edit Box, and the listed rows with affiliated Compares or Search Parameter. The First time a user chooses their GEDCOM file, only MyFile 1 would appear. This larger page would appear only after they hit the Continue Button. Maybe a running count of Total Names -Matched - Rejected - Completed could go in a column(s) after the last Edited Date column?

Basically, this is not a rewrite of what GEDCOMpare does, just how it displays what the work area is. I love GEDCOMpare, but just think it needs a little tweak about file size.This is just a rough draft idea and very much open to discussion...Please.

One of the major reasons I thought this up is that trying to get users to make smaller gedcom files to upload is nigh on impossible. If this works, this is not as much of issue anymore.

  • Login to edit this profile and add images.
  • Private Messages: Send a private message to the Profile Manager. (Best when privacy is an issue.)
  • Public Comments: Login to post. (Best for messages specifically directed to those editing this profile. Limit 20 per day.)
Comments: 1

Leave a message for others who see this profile.
There are no comments yet.
Login to post a comment.
Sounds like a good idea. And I think breaking it into manageable chunks is an encouragement to the user to get to the prize faster (seeing their peeps on the tree) but also allows them to see the results of a smaller chunk. I often think that the number of orphaned or essentially abandoned GEDCOM profiles is the result of overwhelming number of profiles at the same time. Like it!