About the GEDCOM Review Committee
Members of the GEDCOM Review Committee are responsible for reviewing uploaded GEDCOMs to ensure that they meet WeRelate's quality standards before the upload is approved and wiki pages are created.
Overview Committee Liaison
JBS66 is available as a liaison between this group and the Overview Committee. There may be times that additional help is needed for this group to operate smoothly. Some examples include: a need for additional volunteers, questions about tasks, requests for assistance with conflict resolution, requests for policy changes, etc. If you would like help, please feel free to contact me either via my talk page or via email
Current GEDCOM Review Committee Members
If you would like to participate in this committee, please leave a message on the talk page. Thank you!
To monitor uploaded GEDCOMs, click on Gedcom review in the Admin menu. You'll see a list of all GEDCOMs that are somewhere in the import process. The only ones you care about are the ones that need administrative review. They'll have a needs admin review message next to them. Open a second tab to User:Solveig/gedcom review, this is a log of uploaders.
Tabs to check
To review a GEDCOM that needs review, click on the GEDCOM's name of the GEDCOM file. This brings up the GEDCOM review program. Mainly check these three things in the GEDCOM review program:
How many people are being imported? I spend less time on small GEDCOMs than large ones. Also, what's the ratio of warnings to people imported? If there are relatively many warnings for the number of people imported, it's worth spending more time looking at the warnings.
How many warnings are there, and how serious do they look? I've come to the conclusion that nearly every GEDCOM of any size is going to have errors. Very few have come in without warnings. I've come to the conclusion that it's unreasonable to expect people to fix their warnings during the upload process. Maybe they'll fix a few, but not all. At least we've made them click on every warning so that they can see where the problems are. Eventually I'll create a warnings list (like Show duplicates) so that people can see the warnings for their tree. In the meantime I let the GEDCOMs go through if there aren't too many warnings. If there are a lot of warnings I spot-check the warnings to see how serious they are. if often helps to click on the Warnings heading of the table, which sorts the table by type of warning and groups people with the same warning together. Many warnings aren't serious: sometimes children were born before marriage, and it's ok not to know the gender of infants. As I browse the warnings I try to get a sense of how many are serious.
If there are a lot of warnings that look serious, I'll leave a message for the user asking them to look at certain families after the import. If there are too many warnings (say more than 1 in 10 or 20 people to be imported have a serious warning?) then I recommend that we tell the user we can't import their GEDCOM -- that they need to clean up their warnings and re-upload. Although I've left several messages for users, I believe I've told a user that we can't import only once.
The most serious warning is the one about duplicate families within the GEDCOM. This warning can't easily be fixed during GEDCOM import because it's difficult to know which family is the one to exclude. If there are just a few duplicate families, leave a message to the uploader asking them to check their Show duplicates list the following day and merge them. If there are more than a handful of duplicates, don't import the GEDCOM. First Leave a message ask the uploader to clean up their duplicates and re-upload. Then Return to user review and .
Family Matches tab
Especially at the "not a match" lines. If there are a lot of matches, click on the Matched Page header so that the "not a match" lines sort to the top. If it looks to me that one or more of the families are indeed a match, I leave a message for the user asking them to reconsider, and move the GEDCOM back to user review so that they could re-review those families. Once a user left me a message that the reason that they didn't want to merge was because they weren't that certain of their own information. In that case, import the GEDCOM without the families being merged.
Another thing you can do: If you notice that families have been matched but none of the existing families have been updated (the Updated column is completely blank), it might be helpful to spot-check a few of the families to see if the uploader has some good sources to add. Sometimes, you will find that the uploader has some good sources, but didn't update the existing pages with them. In that case, leave a message for the uploader, asking them to update the existing pages with their sources, and move the GEDCOM back to user review so they can do so. Explain that once they've done this they should click on Ready to import again and that it will be imported right away.
The other tabs
We used to spend time seeing how well the place matcher is working, but it looks like it's working reasonably well now, so I don't usually spend time on this tab.
It's disappointing, but a fair number of GEDCOMs come in without sources. I don't think we want to try to fight this issue during GEDCOM upload. Hopefully we'll eventually teach people to source their work. So I don't usually spend time on this tab.
I'm always impressed though when someone has taken the time to match their sources to Source pages, especially now when it's still way too difficult.
Approving the gedcom for import
There are three buttons on this tab:
Here are some sample messages you can use.
If you leave a message for someone, please record it on the contact log. Gedcoms can be deleted if they are more than 30 days old and there has been no activity. As a courtesy, before deleting GEDCOM's from established users, give them advance notification by leaving a message on their talk page.