User talk:Rabino1

Watchers

Topics


Welcome

Welcome to WeRelate, your virtual genealogical community. We're glad you have joined us. At WeRelate you can easily create ancestor web pages, connect with cousins and other genealogists, and find new information. To get started:

If you need any help, we will be glad to answer your questions. Just go to the Support page, click on the Add Topic link, type your message, then click the Save Page button. Thanks for participating and see you around! --Support 16:19, 28 February 2016 (UTC)


Next step: Review your GEDCOM [28 February 2016]

You're not done yet!

WeRelate is different from most family tree websites. By contributing to WeRelate you are helping to create Pando for genealogy, a free, unified family tree that combines the best information from all contributors.

Now that you have uploaded Rabino 2013.ged, your next step is to review what your pages will look like, review any potential warnings, and combine (merge) people in your GEDCOM with matching people already on WeRelate. You need to review your GEDCOM before it can finish importing. We will keep your GEDCOM in the queue for two weeks to give you time to review it.

Note: if your gedcom contains many errors or multiple families, we’d ask that you resolve and correct the errors, delete this gedcom and re-submit it without the errors before merging it with families already on WeRelate. If the gedcom is very large, we’d suggest breaking it up into separate files (or families) and importing them one at a time, which makes the review and correction process easier.

Click here to review your GEDCOM

Once you have finished your review and marked your GEDCOM Ready to import, one of our administrators will review your GEDCOM and finalize the import. This usually happens within 24 hours. You will receive a message here when the pages have been created.


--WeRelate agent 16:28, 28 February 2016 (UTC)

Next step: Review your GEDCOM [28 February 2016]

You're not done yet!

WeRelate is different from most family tree websites. By contributing to WeRelate you are helping to create Pando for genealogy, a free, unified family tree that combines the best information from all contributors.

Now that you have uploaded Rabino 2016.ged, your next step is to review what your pages will look like, review any potential warnings, and combine (merge) people in your GEDCOM with matching people already on WeRelate. You need to review your GEDCOM before it can finish importing. We will keep your GEDCOM in the queue for two weeks to give you time to review it.

Note: if your gedcom contains many errors or multiple families, we’d ask that you resolve and correct the errors, delete this gedcom and re-submit it without the errors before merging it with families already on WeRelate. If the gedcom is very large, we’d suggest breaking it up into separate files (or families) and importing them one at a time, which makes the review and correction process easier.

Click here to review your GEDCOM

Once you have finished your review and marked your GEDCOM Ready to import, one of our administrators will review your GEDCOM and finalize the import. This usually happens within 24 hours. You will receive a message here when the pages have been created.


--WeRelate agent 21:12, 28 February 2016 (UTC)

Gedcom Review [29 February 2016]

I am reviewing your gedcom prior to upload and there are some problems.

There are an excessive amount of warnings, are you sure they can be ignored? Some I think should be corrected before importing. For example Unknown Husband Blickensderfer should not be added to WeRelate as the name does not conform to our conventions and as they have no dates and places attached they cannot be checked for duplicates, from the notes you imply thw woman may have had illegitimate children and that is just as likely. As there are no sources given anything is possible. You also have Ulrich Blickensderfer married to an Unknown Blickensderfer, this is probably not her name, people should be added with their birth name to enable matching with pages already created. There are also warnings for childrens births being less than 9 months apart and women over 45 or 55 having children, are you sure these are correct? Do you have any proof?

Many of the places listed are not places but are a random collection of letters and numbers, these cannot be matched to places in our database, some places have been matched but some are incorrect, Gloucester Co, NJ or Maryland has been matched to Gloucester England. You should really correct the places in your software before creating a gedcom and you need to check and match the places before asking for import.

Sources, it is nice to see sources added to gedcoms, it is the proof that moves a family story into being genealogical research. Unfortunately there seems only to be one source and that is excluded, other peoples websites or gedcoms are not sources unless they contain sources that are publicly viewable. If they contain sources you should really add citations to your data as you enter it then everyone will know where to check.

With the family matches there is at least two matches that you have marked as not a match, Evan Shelby and Letitia Cock Cox with Evan Shelby and Letitia Co are obvious, then Christian Blickensderfer and Catherina Schuerger seem to have a correct match despite the alternative spelling of her name. On the matter of names you seem to use things like Cock\Cox to denote possible alternatives, you should really add one name in your software and add the other name as an alternative, this will allow better searching and matching.

I am returning the gedcom for your further review, if you have comments or questions please add them to this page so I will see them.

My suggestion would be to correct the errors in your places list, check and correct all the errors listed on the warnings page in your own copy of the data, adding some primary or secondary sources if you can, then create a new gedcom but select to not add living people, that will simplify the checking and matching. Rhian 10:06, 29 February 2016 (UTC)