Frequently asked questions
What is a GEDCOM?
How should I prepare my data for GEDCOM upload?
This is important, if you do not carry out these 5 simple steps you will create a lot more work for yourself and the upload request may be declined.
It is tempting to just push the button and upload your GEDCOM. However, you will have a more rewarding experience at WeRelate if you follow these suggestions.
Every person should have at least one date and place, for matching purposes, and each event should have at least one primary or secondary source.
I used the Add gedcom tool to upload my gedcom, when can I view the pages on WeRelate?
WeRelate is not like other sites where you can just upload gedcoms and leave them, we are creating a single tree and any data you add is merged into the tree, it can be edited and improved by anyone and to ensure we are all playing the same game we ask users to review their gedcom import before it is added to the main wiki.
A short while after sending your file you will get a message about reviewing your gedcom, the message on your talk page includes a link to the review system, with lots of help. See Review gedcom for all the help. Once you have reviewed all of the data, correcting any errors and making sure that placenames and sources are correctly linked. You also need to be sure any possible matches with existing people and families are either matched correctly or marked as not a match. You should not need to do much work excluding living people as you removed them before creating the gedcom.
When you are sure the data is as good as it can be, it can take several days to check if you have lots of people, you can then select the import request on the last tab. At this point an administrator will check the gedcom and either pass it or return it to you as there are some points they want you to check again, once approved the file goes into the process queue and the data will be online within a hour, you will get another message on your talk page to let you know.
What about living people listed in my GEDCOM?
It is against the law in many jurisdictions to publish data about living people without their consent. WeRelate assumes that people with birth dates in the last 110 years without any thing in the death or burial date or place fields are living. People without birth dates are generally assumed to be dead. Because WeRelate removes all information from living people except the gender and surname, the page created would be empty and named something like "Living Smith". Thus we have adopted a policy of excluding living people from gedcom imports.
How do I use a GEDCOM file on WeRelate?
How do I create/export a GEDCOM file?
How do I upload my GEDCOM file to WeRelate?
What happens to living people in my GEDCOM?
In order to preserve the privacy of living individuals, it is the policy at WeRelate that wiki pages not be created for living individuals, or if they are, that the pages include only surname, gender, and the families to which the individual is related (as a spouse or child). It is your responsibility as a contributor to make sure the living people in your GEDCOM are either excluded from import or marked as "living".
One way to do this is to filter out living people from your GEDCOM before uploading it to WeRelate. Another way is to mark living people as "Living" when you review them during the GEDCOM upload process. As a service, WeRelate uses the following rules to guess which people in your GEDCOM are living. You should review and correct any incorrect guesses.
People who have been marked "Living" and who have not been excluded from import will have wiki pages created for them that contain only the person's surname, gender, and the families to which they belong (as a spouse or child). We create these pages only when needed to connect the "root" person to the tree. Please do not remove the exclude markers on other living people.
I uploaded my GEDCOM, but a distant cousin appears in the Family Tree Explorer window. Where is the rest of my family tree?
When I upload a GEDCOM, why is some of my information not in the fields I expect?
When I upload a GEDCOM, what happens to my images?
Can I create a GEDCOM on WeRelate to export to another application?
Can I update my tree by re-uploading an updated GEDCOM?
How does the information in my GEDCOM appear as wiki pages?
The system creates a Person page for each person in your gedcom (unless the person is marked excluded in gedcom review), a Family page is created for each family (unless marked excluded in gedcom review), and a MySource page is created for each source (unless linked to a Source page in gedcom review). If the gedcom has any repositories (generally rare), the repository name and address are added to the MySource pages that link to that repository.
Source citations in the gedcom become source citations on the Person and Family pages. Notes in the gedcom become notes on the Person and Family pages if they are attached to a specific name, event, or source citation in the gedcom; if the note isn't attached to anything specific in the gedcom then it is added to the big History text box. Images in the GEDCOM are ignored, because GEDCOM stores images as just a filename, which is useless when you're online.
Events and facts in the gedcom become events and facts on the Person and Family pages. LDS events are ignored. If the event/fact doesn't correspond to one of our 50+ event/fact types, it is assigned a type of Other.
Married names and religious names in the gedcom are added appropriately. AKA names become Alternate names. Some gedcom's store name parts (given, surname, prefix, suffix) all together in a single field. When this happens the system looks for slashes (//) or ALL-CAPS to identify the surname. If that fails, uses a list of common name prefixes and suffixes to identify the prefixes and suffixes, and then assumes that the surname is the last word in the field.
The above rules handle everything in the official GEDCOM standard, but some desktop genealogy programs store additional information that is not part of the standard. Anything in a GEDCOM that does not have a corresponding field in WeRelate is added to the big History text box.