User talk:FranklySpeaking

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 13:37, 30 May 2013 (EDT)


Next step: Review your GEDCOM [30 May 2013]

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 Bluford Family GEDCOM.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 17:29, 30 May 2013 (EDT)

Next step: Review your GEDCOM [30 May 2013]

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 Bluford Hawkins Family GEDCOM.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 20:44, 30 May 2013 (EDT)

Bluford Hawkins Family GEDCOM.ged Imported Successfully [1 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 20:12, 1 June 2013 (EDT)

Next step: Review your GEDCOM [2 June 2013]

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 Francis Cunningham Hawkins Family GEDCOM.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 22:03, 2 June 2013 (EDT)

Francis Cunningham Hawkins Family GEDCOM.ged Imported Successfully [3 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 13:20, 3 June 2013 (EDT)

Next step: Review your GEDCOM [3 June 2013]

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 Francis Claiborne Hawkins, Sr. GEDCOM.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 22:50, 3 June 2013 (EDT)

Francis Claiborne Hawkins, Sr. GEDCOM.ged Imported Successfully [4 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 15:05, 4 June 2013 (EDT)

Next step: Review your GEDCOM [4 June 2013]

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 Noah Hawkins Family (1767) GEDCOM.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 18:40, 4 June 2013 (EDT)

Noah Hawkins Family (1767) GEDCOM.ged Imported Successfully [7 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 07:42, 7 June 2013 (EDT)

Next step: Review your GEDCOM [14 June 2013]

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 Cornelis Franciscus Keuzenkamp Family GEDCOM.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:51, 14 June 2013 (EDT)

Cornelis Franciscus Keuzenkamp Family GEDCOM.ged Imported Successfully [16 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 06:30, 16 June 2013 (EDT)

Next step: Review your GEDCOM [19 June 2013]

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 Pieter Keuzenkamp Family GEDCOM.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 10:20, 19 June 2013 (EDT)

Pieter Keuzenkamp Family GEDCOM.ged Imported Successfully [20 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 07:24, 20 June 2013 (EDT)

Page titles [20 June 2013]

Hi, I noticed that you renamed a few family pages to titles such as Teunis Cornelis Keuzenkamp and Martha Marie Augustine Wallet. When renaming pages, please include only the first and last names (or first and patronymic if it was before 1811 and the person did not adopt a surname in their lifetime). Middle names can be added when editing a page. The full name will appear in the blue box on pages, as well as in search results. I renamed the pages for you to follow this convention. If you have any questions, just let me know. Thank you, --Jennifer (JBS66) 16:48, 20 June 2013 (EDT)


Hi Jennifer, Thanks for the heads up. I knew about adding the middle names during the editing process for person pages, but not for family pages. Will be sure to do it that way in the future. :-) Best, Frank

P.S. Don't be bashful about giving me feedback. I'm new and still learning.--Frank 18:05, 20 June 2013 (EDT)


Next step: Review your GEDCOM [21 June 2013]

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 Pieter Keuzenkamp, Sr. Family GEDCOM.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:34, 21 June 2013 (EDT)

Pieter Keuzenkamp, Sr. Family GEDCOM.ged Imported Successfully [22 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 17:45, 22 June 2013 (EDT)

Next step: Review your GEDCOM [25 June 2013]

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 Gerrit Cornelis Keuzenkamp Family GEDCOM.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 15:47, 25 June 2013 (EDT)

Gerrit Cornelis Keuzenkamp Family GEDCOM.ged Imported Successfully [26 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 13:42, 26 June 2013 (EDT)

Next step: Review your GEDCOM [26 June 2013]

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 Teunis Keuzenkamp Family GEDCOM.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:58, 26 June 2013 (EDT)

Teunis Keuzenkamp Family GEDCOM.ged Imported Successfully [28 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 10:13, 28 June 2013 (EDT)

Next step: Review your GEDCOM [28 June 2013]

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 Daniel Keuzenkamp Family GEDCOM.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 12:33, 28 June 2013 (EDT)

Daniel Keuzenkamp Family GEDCOM.ged Imported Successfully [29 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 06:08, 29 June 2013 (EDT)

Next step: Review your GEDCOM [29 June 2013]

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 Tuenis Keuzenkamp Family GEDCOM.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 08:23, 29 June 2013 (EDT)

Tuenis Keuzenkamp Family GEDCOM.ged Imported Successfully [29 June 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 14:07, 29 June 2013 (EDT)

Next step: Review your GEDCOM [1 July 2013]

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 Noah Hawkins (1808) Family GEDCOM.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 12:48, 1 July 2013 (EDT)

Noah Hawkins (1808) Family GEDCOM.ged Imported Successfully [2 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 17:18, 2 July 2013 (EDT)

Next step: Review your GEDCOM [4 July 2013]

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 Francis Charles Brinkmann Family GEDCOM.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 14:01, 4 July 2013 (EDT)

Francis Charles Brinkmann Family GEDCOM.ged Imported Successfully [5 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 16:37, 5 July 2013 (EDT)

Next step: Review your GEDCOM [6 July 2013]

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 Francis Henry Brinkmann Family GEDCOM.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 19:50, 6 July 2013 (EDT)

Francis Henry Brinkmann Family GEDCOM.ged Imported Successfully [9 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 08:27, 9 July 2013 (EDT)

Next step: Review your GEDCOM [16 July 2013]

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 William R. Barclay Family GEDCOM.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 14:22, 16 July 2013 (EDT)

William R. Barclay Family GEDCOM.ged Imported Successfully [17 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 11:06, 17 July 2013 (EDT)

Next step: Review your GEDCOM [17 July 2013]

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 John Anderson Jr. Family GEDCOM.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:04, 17 July 2013 (EDT)

John Anderson Jr. Family GEDCOM.ged Imported Successfully [20 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 09:51, 20 July 2013 (EDT)

Next step: Review your GEDCOM [20 July 2013]

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 William Adamson Family GEDCOM.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:23, 20 July 2013 (EDT)

William Adamson Family GEDCOM.ged Imported Successfully [22 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 09:22, 22 July 2013 (EDT)

Next step: Review your GEDCOM [23 July 2013]

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 Thomas Adamson Family GEDCOM.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 07:26, 23 July 2013 (EDT)

Thomas Adamson Family GEDCOM.ged Imported Successfully [24 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 07:20, 24 July 2013 (EDT)

Next step: Review your GEDCOM [27 July 2013]

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 Emery Ford Porter Family GEDCOM.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 09:16, 27 July 2013 (EDT)

Emery Ford Porter Family GEDCOM.ged Imported Successfully [29 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 09:37, 29 July 2013 (EDT)

Next step: Review your GEDCOM [30 July 2013]

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 William Porter Family GEDCOM.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 13:31, 30 July 2013 (EDT)

William Porter Family GEDCOM.ged Imported Successfully [30 July 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 19:47, 30 July 2013 (EDT)

Next step: Review your GEDCOM [2 August 2013]

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 Philo Thomas Porter Family GEDCOM.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:45, 2 August 2013 (EDT)

Philo Thomas Porter Family GEDCOM.ged Imported Successfully [3 August 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 22:54, 3 August 2013 (EDT)

Next step: Review your GEDCOM [6 August 2013]

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 Thomas Porter Family GEDCOM.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 15:33, 6 August 2013 (EDT)

Thomas Porter Family GEDCOM.ged Imported Successfully [6 August 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 22:00, 6 August 2013 (EDT)

Next step: Review your GEDCOM [8 August 2013]

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 William Porter Family GEDCOM.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 10:58, 8 August 2013 (EDT)

GEDCOM upload for 'early' people [9 August 2013]

Hi Frank, I tweaked the settings, you can now upload GEDCOM files where people between 1550-1750 will be included. The file you currently have in the queue will not be reprocessed automatically, however, files you upload in the future will take this new setting into account. If you have any questions about this, just let me know! --Jennifer (JBS66) 11:05, 9 August 2013 (EDT)


Thank you, Jennifer. You have saved me hours of tedious data entry! :-) Best, Frank--Frank 11:11, 9 August 2013 (EDT)


William Porter Family GEDCOM.ged Imported Successfully [12 August 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 07:24, 12 August 2013 (EDT)

Next step: Review your GEDCOM [12 August 2013]

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 Nehemiah Porter Family GEDCOM.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 20:01, 12 August 2013 (EDT)

Nehemiah Porter Family GEDCOM.ged Imported Successfully [13 August 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 13:37, 13 August 2013 (EDT)

Next step: Review your GEDCOM [14 August 2013]

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 Daniel Dillman Family GEDCOM.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 08:22, 14 August 2013 (EDT)

Daniel Dillman Family GEDCOM.ged Imported Successfully [18 August 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 09:34, 18 August 2013 (EDT)

Next step: Review your GEDCOM [18 August 2013]

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 Jacob Dillman Family GEDCOM.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 17:40, 18 August 2013 (EDT)

Jacob Dillman Family GEDCOM.ged Imported Successfully [19 August 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 23:25, 19 August 2013 (EDT)

Hello [23 August 2013]

Hi Frank, got your note on my Talk Page regarding the Spitler family. Although I am not directly related to this family, they are part of a very large project that I and a few others here have been working on, Early Settlers of Augusta County, Virginia. documenting many of the early families that either passed through or settled in Augusta County. Feel free to add the Augusta County Banner to other Augusta County families, as it makes it easier for us working this project to be able to identify and add records and other sources...

Thanks again for the note, hope to see some additions to the Augusta County Settlers. I noticed you've been adding a bunch of gedcoms recently, so I'm sure we'll be "bumping" into each other once in a while.

Best regards and have a great weekend,

Jim:)--Delijim 18:40, 23 August 2013 (EDT)


Next step: Review your GEDCOM [25 August 2013]

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 Azel Miner Family GEDCOM.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 10:13, 25 August 2013 (EDT)

Azel Miner Family GEDCOM.ged Imported Successfully [26 August 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 11:22, 26 August 2013 (EDT)

Next step: Review your GEDCOM [30 August 2013]

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 Elihu Minor Family GEDCOM.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 10:10, 30 August 2013 (EDT)

Elihu Minor Family GEDCOM.ged Imported Successfully [2 September 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 10:10, 2 September 2013 (EDT)

Next step: Review your GEDCOM [3 September 2013]

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 William Minor Family GEDCOM.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 10:56, 3 September 2013 (EDT)

William Minor Family GEDCOM.ged Imported Successfully [4 September 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 20:40, 4 September 2013 (EDT)

Next step: Review your GEDCOM [11 September 2013]

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 Benjamin Ford White Family GEDCOM.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 17:05, 11 September 2013 (EDT)

Benjamin Ford White Family GEDCOM.ged Imported Successfully [13 September 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 00:53, 14 September 2013 (EDT)

Next step: Review your GEDCOM [14 September 2013]

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 Daniel White Jr. Family GEDCOM.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 20:01, 14 September 2013 (EDT)

Daniel White Jr. Family GEDCOM.ged Imported Successfully [16 September 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 09:43, 16 September 2013 (EDT)

Next step: Review your GEDCOM [18 September 2013]

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 Daniel White Family GEDCOM.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 11:01, 18 September 2013 (EDT)

Daniel White Family GEDCOM.ged Imported Successfully [18 September 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 22:52, 18 September 2013 (EDT)

primary sources [21 September 2013]

On Person:Remember Read (1): a transcript of the actual deed would be primary. A source telling you there is such a deed is secondary. --Jrich 02:47, 21 September 2013 (UTC)


Yes, that makes very good sense. I appreciate the input and will treat sources differently from now on. BTW, I found your thoughts on "The Need for Sources" to be quite insightful and instructive. Thanks...--Frank 11:56, 21 September 2013 (UTC)


Leading Zeroes [26 September 2013]

Please note that the only place the WR Style Guide calls for leading zeroes is in the special case of a three-digit year. --Pkeegstra 13:26, 26 September 2013 (UTC)


Thanks...--Frank 17:01, 26 September 2013 (UTC)


Remember Read [19 October 2013]

This isn't about whether it is a baptism or a christening. It is about how the website is used. We put this information in the christening spot because that is where all the other pages have it. Even with recent changes, the christening spot is still in a preferred spot because it is easier to enter and it (for me at least) visible in edit mode whereas baptism requires scrolling down to notice. You need to create a suggestion on the Suggestion Page if you want to make baptism treated differently and to change the tens of thousands of pages that already use christening. --Jrich 15:29, 19 October 2013 (UTC)

Indeed, I have an action item from the Oversight Committee to confirm that none of the major Christian traditions which baptize infants understand any semantic difference between the words "baptism" and "christening". If that is the case, we would probably propose the converse, that the two events be unified. On a related note, perhaps a higher priority enhancement should be implementation of an event with the semantics of GEDCOM's "adult christening" for baptisms not involving infants, with the implication that this would *not* be a proxy for birth. (The "adult" is a bit problematic, as some Christian groups allow children as young as six to request such a believer baptism.) --Pkeegstra 17:17, 19 October 2013 (UTC)


Regarding Remember Read's page, all three sources refer to baptism. Entering baptism dates in the christening field would not reflect the genealogical record. Baptism and christening are not always the same depending on the religion and its local traditions. We previously discussed this at some length in another thread re: Thomas Minor (see below)

As I understand your comment, you still believe baptism dates should be entered in the christening field for the sake of consistency using the argument that it's how we've always done it. I don't see that as a compelling argument to enter data that isn't based on what the sources say. You had it right in your personal writeup when you said: "I tend to dislike any practice that claims to make genealogy easy (because it isn't: it requires attention to detail, precision, perserverence, thoroughness, and objectivity)..."

The difference between baptism and christening is precisely what this discussion is about. To not make the distinction is to ignore the detail and to be imprecise. For now, WeRelete is set up to accomodate the distinction.

Maybe the task Pkeegstra has underway will help. I am interested in contributing to any initiative that would address baptism and christening in such a way as to accomodate all Christian religions.

Lastly, in an unrelated matter, I'd like to understand the reason Jrich deleted Remember Read's Married Name from her record.


From User:DataAnalyst talk page: Thomas Minor Revisions [3 October 2013] Thanks for the input, I'm on board with your point re: christening vs. birth date. However, in this case, I believe Thomas' page is now incorrect. Here's why:

-Source 2 indicates that Thomas was baptized 23 Apr 1608 (not christened).

-No source listed in the record indicates Thomas was ever christened. This makes the current record factually incorrect.

-Source 7 (by John A Miner) is clear that Thomas was born 23 Apr 1608, not baptised or christened. All of John's published work consistently indicates 1608 as Thomas' birth date. John is the lifelong Miner/Minor researcher and founder of the Miner Association. Very credible source is my point. Was Thomas born or baptized 23 Apr 1608. I don't know - both are shown in the record.

-As now written, the terms christening and baptism are being used interchangeably - a problem I've noticed in many WeRelate records. Baptism is typically the act of bringing the child into the church family. Christening is the naming ceremony. There are exceptions, but the record as it relates to Miner/Minor is quite consistent in its use of baptism.

I hope I've clearly explained why I made the changes. I believe they make the record more factually correct than the way it is now. Maybe some note regarding the slim likelyhood that Thomas was born and baptised on the same day is in order. Problem is, both are purported to be true - just depends on who you want to believe. That's why I included 23 Apr 1608 as a birth date and as a baptism date.

Best, Frank--Frank 03:13, 25 September 2013 (UTC)

If you read the GEDCOM standard, the meaning of the BAPM tag, and the CHR tag seem interchangeable. BAPM {BAPTISM}: = The event of baptism (not LDS), performed in infancy or later. CHR {CHRISTENING}: = The religious event (not LDS) of baptizing and/or naming a child. CHRA {ADULT_CHRISTENING}: = The religious event (not LDS) of baptizing and/or naming an adult person. It used to be that the two tags were treated differently, with Christening understood by the system, Baptism not. Now they seem to be handled the same. Still Christening corresponds to the always-there fact, next to the birth, while Baptism is optionally displayed, at the bottom in the edit screen. In practice, I believe nearly everybody simply uses christening, partially due to the historical differences, partially because its position on the display represents why either of these events are of interest. It is basically a church event that acts as a proxy for birth when birth is missing, or to confirm reasonableness of the birth when it is there. Adult baptism is seldom documented because it seldom has much use, except perhaps to note residence changes or name changes due to marriage, etc. --Jrich 04:19, 25 September 2013 (UTC) [Adding the following to keep the topic in one location. --Jrich 14:17, 25 September 2013 (UTC)] es, the GEDCOM standard does appear to use the terms baptism and christening interchangeably. The broad non-specific nature of the definition accommodates the different and widely varying practices of all religions. It is not meant as as a defacto one-size-fits-all standard. To apply it as such diminishes the wonderful and rich diversity of our religions.

A case in point is the Minor/Miner family baptisms of 15 Sep 1751, when four Minor children ranging in age from a few months to a few years old were baptized in the First Church of New London, CT. Clearly, this was not a naming ceremony, but rather a ceremony to bring the children into the church and its belief system. To note these ceremonies in the WeRelate record as a christening is not historically correct, nor would it be consistent with Connecticut VRs, church records, and the independent conclusions of multiple genealogists.

Consider Hans Landis, the Swiss Anabaptist Minister martyred in 1614 by the civil authorities of the canton of Zurich, Switzerland. He is emblematic of an entire religion based on when and how many times a person of faith should be baptized. The Anabaptists (meaning twice baptised) later evolved into the Mennonites, Amish, and numerous other offshoots all with their own distinct timing and religious dogma surrounding baptism. Neither the term nor pracice of christening (as in a naming ceremony) is used by any of these faiths.

Next steps:

1) WeRelate data entry protocals should be adjusted to accomodate the diverse and unique practices of all religions. 2) The baptism entry should be used when applicable. In my opinion, it should be on par with the christening entry; that is, neither baptism or christening should have preference. 3) More attention needs to be paid to the distinction between baptism and christening, including the use of christening as a defacto birth record - a practice that should be avoided if for no other reason than accuracy in my opinion.--Frank 13:12, 25 September 2013 (UTC)

First of all, your statement "bring the children into the church" is not clearly so. Usually communion does that. And most infant deaths are recorded with no name for the child. So I disagree with your base argument, at least to the "clearly" extent. Second, baptism was a subject of much religious dissension during the time period in question, so practices of modern religions have no bearing on what was done then, and further I have no desire to become a religious-history nut to figure it out. Third, it doesn't seem to be the meaning of the ceremony itself that makes baptism or christening important to genealogy. Fourth, since the rest of world, including software makers, are using GEDCOM, the data coming into WeRelate is going to be that way whether WeRelate chooses to make itself different or not. So no matter what rules are written, incoming data will tend to use either tag for either meaning and soon there will be no consistency anyway. --Jrich 14:17, 25 September 2013 (UTC)

To move the conversation along, let's put all the esoteric religious discussion aside - at least for now. For me, this all boils down to whether or not the data in WeRelate reflects the historical record; that is, vital records, church records, family bibles, and the rest. What do the records say? The answers are what should be in WeRelate.--Frank 14:53, 25 September 2013 (UTC)

Two points:

First point: Each country has its own history of recording births/baptisms, which is worth understanding. Unlike the U.S., which introduced civil vital records fairly early, the UK did not introduce this practice (nationally) until 1837. Prior to that, the primary source of "birth" information was parish registers, which recorded baptism date. Occasionally, they also recorded the birth date, but this was not common practice (for more specific information, see this article). Therefore, any date from the UK as early as 1608 that purports to be a birth date is highly suspicious - it was likely a baptism date, and there is no record of the birth date.

Second point: Unfortunately, while it is reasonable to use an early (pre-1700) baptism date as a proxy for a birth date (it would normally be within a month or so of birth), some genealogists have chosen to represent it in their work as the actual birth date. This appears to be the case with the book by John A Miner - whether or not he was personally responsible for this representation in the book.

John A Miner is also co-author of The Curious Pedigree of Lt. Thomas Minor, which clearly indicates that the date is a baptism date, and does not provide a birth date (p. 183: '...the Thomas Myner baptized at Chew Magna on 23 April 1608.' and p. 184: 'Thomas bp. 23 April 1608'). This is much more believable. Therefore, I believe the WeRelate page as I corrected it is accurate.

As for the "christening" vs. "baptism" fact - my personal preference would be to use the "baptism" fact, but my genealogy program (and I believe WeRelate) do not treat them the same and the only way to get the date to display as a proxy for birth date is to use the "christening" fact. So that's what I (and many others) do - as Jrich pointed out.--DataAnalyst 03:15, 26 September 2013 (UTC)

Thanks for the clarifying thoughtful response. Appreciate it. One last question for you: as the practice applies to WeRelate, what is the thinking behind having a christening date display as a proxy for the birth date? If its primary purpose is to populate the header field, what possibility is there to allow baptism dates to be used for the same purpose? In my way of thinking, such a change would result in much improved data integrity - at least when it comes to birth-baptism-christening dates! Best,--Frank 03:45, 26 September 2013 (UTC)

From a quick test (not saved), it looks like WeRelate does in fact display baptism the same as christening. It still applies the "chr:" label, though. I was not aware of that when I reverted the page, so I could have left the baptism date while removing the birth date. My software (last updated Sep 2011) does not treat them the same, so when I upload a GEDCOM file, it will always be christening date. One of the implications of WeRelate treating them the same, is that if all you have is a baptism date and you are pretty sure it was not in infancy (e.g., a number of children in the same family baptized at the same time, or the baptism of an Anabaptist), you should estimate a birth year so that the baptism is not treated as a proxy for birth date. I was not aware of this and will have to keep it in mind.--DataAnalyst 11:59, 27 September 2013 (UTC) Yes, I've also noticed the system takes baptism dates and posts them in the header as a christening date. Appreciate you confirming I wasn't imagining it! Over time, I'll probably revert Thomas' date back to a baptism if you have no major objection...--Frank 12:10, 27 September 2013 (UTC)

I have no issue with that.--DataAnalyst 12:12, 27 September 2013 (UTC) I have to concur that if an event which by all indications is performed in an Anglican church in Chew Magna, Somerset, England cannot be called a "christening" then I'm not sure what the word means. My understanding is that preference for the term christening comes from the Anglican (US Episcopalian) and the Catholic communities. Calvinist communities in the UK (Church of Scotland or Reformed in England) and their successors (e.g. New England Congregational or Unitarian) are the ones who historically prefer the term "baptism". (Speaking as a Calvinist, but from the Dutch tradition.) So absent specific evidence to the contrary, I cannot construe an event in England as anything other than Anglican. --Pkeegstra 13:28, 3 October 2013 (UTC)

Far from being an expert, I 'googled' "anglican christening" and got the following web page about baptism from the Church of England. It references part of today's ceremony as coming from their 1662 Book of Prayer. Offered as a point on the curve.... http://www.churchofengland.org/weddings-baptisms-funerals/baptism-confirmation/baptism.aspx

Also see this page from the Church of England explaining the difference between christening and baptism - at least how they view it. http://www.churchofengland.org/media-centre/news/2013/07/top-10-facts-about-christenings.aspx Frank 16:07, 3 October 2013 (UTC)

You know, I can't recall a single documented instance actually called "Christening" in pages I've worked on. There could be some, but I don't recall any off the top of my head. I ran into this the first baptism I ever tried to enter, saw that the usage on this website was to favor the Christening tag. Since the only external factor that would seem to constrain the website's designers from doing what they wanted is the need to interface with GEDOM, I looked up that standard, and as mentioned above, I could not find enough differentiation of their tag definitions to suggest things were being done wrong. So, I have contributed thousands of Baptisms in the Christening slot, as have, I believe, nearly all users. While the handling has (very) recently changed to make display (but not editing!) more similar for the two tags, that does not impact the fact that existing pages use Christening for things we would all agree are Baptisms. So in essence, the difference may mean something to you, but not to this website really. If we wanted the tags to be used in a more precise, differentiated manner, this would be hard to fix, because it would involve doing an analysis of all the (tens or hundreds of thousands) Christenings to see which tag each one should really be. The easiest way would be to change the display label from Christening or Baptism to both be Chr/Bap (or Bap/Chr if you prefer) so you can't tell the two tags apart. As with various other detailed issues, I think the answer is to take advantage of the narrative or the source citation. When the source citation says they are baptized on such-and-such a date, even if the date is displayed in the Christening slot, you can communicate the more detailed, more precise, point on the page that way. --Jrich 17:46, 3 October 2013 (UTC)--Frank 20:14, 19 October 2013 (UTC)

Ironically, as pkeegstra has pointed out, the answer to this is likely to be to remove the distinction, meaning your change is probably going to be lost anyway. The family of Remember Read is in need of good research, it seems pointless to argue about insignificant changes based on ambiguous definitions and moving data around on the page.
I removed the married name because it is not generally used on werelate pages. That seems to be a general convention, but I further feel that it should not be used. Since one can change marriage information on the Family page, and surname spellings on the spouse's page, without ever looking at, or editing, the woman's Person page, I feel putting the married name on the Person page adds excessive linkages that will not be properly maintained unless that maintenance is automated. In addition, my own experience is that for those women married 3, 4, or 5 times, it clutters up the screen. I find that it is basically one of those informationless data items, as it tells us nothing new that one doesn't know from other items on the page, so has nothing useful to communicate. It should be used when the married name is an unexpected value, not when it is exactly what one would expect. Functionally, it adds little value, as use of the married name in the Keyword spot will find the link to the family page on the person page, and return the desired search result (though searching for family pages is capable of more precise targeting than searching of person pages). --Jrich 21:22, 19 October 2013 (UTC)

New Amsterdam Place Pipes [24 October 2013]

n.b. there are WR contributors active in the New Amsterdam section who are quite vocal in defense of their place pipes. Wholesale deletion of place pipes is likely to attract their attention. (Although I must admit that a 1748 New York place pipe which mentions USA seems to miss the point.) --Pkeegstra 21:29, 24 October 2013 (UTC)


Thanks for the heads up - I was caught up in a make-it-consistent mode. Will tread more lightly in the future...--Frank 21:43, 24 October 2013 (UTC)


Next step: Review your GEDCOM [31 October 2013]

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 William W. Johnson Family GEDCOM.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 01:55, 1 November 2013 (UTC)

William W. Johnson Family GEDCOM.ged Imported Successfully [4 November 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 13:30, 4 November 2013 (UTC)

Next step: Review your GEDCOM [7 November 2013]

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 John Foote Family GEDCOM.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 15:00, 7 November 2013 (UTC)

John Foote Family GEDCOM.ged Imported Successfully [8 November 2013]

The pages from your GEDCOM have been generated successfully. You may now:

For questions or problems, leave a message for Dallan or send an email to dallan@WeRelate.org.


--WeRelate agent 13:35, 8 November 2013 (UTC)

Thanks! [11 November 2013]

Thanks for your help on the Moses Foote and Mary Byington pages! -- Jdfoote1 01:43, 10 November 2013 (UTC)


Thanks for the kind words. Was going to contact you about Moses' children. Seems his 1st wife, Mary Byinton, died Jan 1740 -- before Ebenezer, Obed, Isaac, and Dorathy were born. Records I have say these last four were Mary's children, but wonder if they may be from Moses' 2nd marriage to Ruth Butler on 5 Nov 1740. Looked like you may be connected to Ebenezer and wondered if you had any insights. Hope to input the remaining children tomorrow. Let's stay in touch?--Frank 02:18, 10 November 2013 (UTC)

Foote is my surname, so I should be most familiar with this line, but I have to admit that I haven't done much original research on them. I have only seen Mary as Ebenezer's mother. -- Jdfoote1 15:43, 11 November 2013 (UTC)

Baptism vs Christening. [23 December 2013]

Was it really necessary to change a couple of instances of Sherman related Christenings to baptisms? Christening is the more common term both on WR and genealogy in general. It's not a big deal, but I am curious why you make those changes EDIT: Nevermind. I just noticed the above discussion and the further discussion on the talk pages of jrich and Data. --Daniel Maxwell 18:29, 23 December 2013 (UTC)


Image:Andrew Ford (1721-1790).jpg [26 December 2013]

From Source:Find A Grave in the section entitled "Photographs": "Photographs on Find A Grave are not in the public domain. Do not download a photograph from there and post it here." --Jrich 23:25, 26 December 2013 (UTC)


Marker Inscriptions from Find A Grave [29 December 2013]

Example: Isaac Curtis (16).

I was wondering why add the marker inscription to the person page when we've already linked to the Find A Grave Memeorial. I personally think it's redundant, but am willing to be convinced to the contrary. It seems kind of similar to adding married names to a female's person page. - Bill Carr a.k.a--jaques1724 17:33, 29 December 2013 (UTC)

For one reason, because some users are so ready to cite Find A Grave even when they have no image attached and are little better than an unsourced website, adding the inscription demonstrates when the source is credible as opposed to when it is not. Personally, I also find it reassuring to see the actual writing without the haze of abstraction and assumption that comes with secondary sources, as well. But that's just my two cents. --Jrich 18:37, 29 December 2013 (UTC)

Oops, should have checked the memorial before I sent the above. In this case, the memorial did not include the inscription so the addition is not redundant. First mistake of the day, but probably not the last. Thanks Jrich for the input. I hope there's more from others who are interested.--jaques1724 18:43, 29 December 2013 (UTC)

Afternoon Bill, In this case I added the information because it wasn't particularly legible on Isaac's grave marker. Also thought it would be nice to let someone read it without clicking thru to the other web site. And lastly, it added his Revolutionary War service that was missing from his Facts and Events section. I don't always add inscriptions, just when I think it's of benefit. That decision, though, like most on WeRelate, is subjective. Why don't I leave it to you as to whether is stays or goes? I have no dog in the fight - just trying to make the record accurate and complete. :-)--Frank 18:58, 29 December 2013 (UTC)


wheelwright's pond [21 January 2014]

Depend's where you look: [1]. --Jrich 23:51, 21 January 2014 (UTC)


Thanks for the new information. Not sure what the best course of action is for Gershom's page -- delete the Wikipedia link? delete the reference to Wheelwright completely? change it to your source (which I prefer)? or some other alternative I've not thought of?--Frank 00:10, 22 January 2014 (UTC)

I doubt it's important. Just explaining the spelling. Probably called Wheelwright Pond now, undoubtedly was called Wheelwright's Pond originally. Either works for me. --Jrich 00:49, 22 January 2014 (UTC)

narratives [25 February 2014]

Sorry to complain, but I am not sure why you are turning all narratives into sources. Two objections: The narratives are there because someone (not necessarily me) like that presentation and it is a community page, meaning not just yours. If you are going to write a more integrated narrative, that would be one thing, but simply to change the narrative into a long list of source citations is too much ownership, not enough working with the community. Second: sources may be embedded in narrative with ref tag, so you can still have scholarship with narratives - meaning, I am not sure why you are doing this anyway.

On Experience Mitchell in particular, the narrative was written long ago. But the links in the second paragraph, which I added much more recently, were added just to justify the information in that paragraph, because I think it is a good thing for people to see primary information and not just take the word of secondary sources all the time. But the information in the first paragraph did not come from the sources cited in the second paragraph, it was somebody else's (probably Amelia's) abstraction of some key points in his life. Meaning the change you made was an invalid source citation and nobody would find the information from the first paragraph in the source cited. And also I worked hard on the URLs in the second paragraph to get them to highlight his name on the page, so didn't exactly appreciate them being thrown away. --Jrich 00:52, 25 February 2014 (UTC)


Jrich, appreciate your input. Understand better now the thinking behind the introductory narratives. Having said that, the narrative for Experience - while well written - appeared inconsistent across the sources I was looking at. In this instance I figured laying out the details individually would let readers see the differences without putting emphasis on one version over another. Certainly didn't mean to mess up that source citation!

Bottom line is I like how the page looks now better than it was when I left it earlier this evening. Thanks for your last revisions. On a related matter, I've noticed that narratives on some pages - but not consistently so - are organized by topic. I'm not aware of any WR standard headings, though.?

In the future I'll try harder to repress my OCD-like desire to organize everything in front of me, floating any ideas I have out for comment before making wholesale changes. Good feedback... :-)--Frank 03:18, 25 February 2014 (UTC)

JRich may be hard on you, but I think you are improving from the early days when you were hairsplitting Christening/Baptism events. Always good to see a WRer learn as he goes along, just as I did. Daniel Maxwell 03:21, 25 February 2014 (UTC)

Now, now, now. Don't get me started on that again! :-) Appreciate your supportive comments...--Frank 03:52, 25 February 2014 (UTC)

I agree with DMaxwell, I like a lot of your recent sources much more than Henry Bond, too. Which is about as positive as I generally get :-), sorry! I don't know if the following makes sense, but I certainly don't want to be consulted on each change you want to make, so here's where I'm coming from:
I have once suggested in a post, and other times hinted, that it would be nice to have some standard narrative layouts, but I don't think there is much support for that. There is more of a lets-see-what-people-do-with-it attitude. I want things to be more objective, rather than reflecting the personality of the last person who edited the page, but there's no policy to support much of anything specific. Further, I really don't know how it should be done, other than thinking something is needed. And some pages on WeRelate are very nice because they are allowed to be creative (though others are not so nice because they are allowed to be creative).
There is a fine line in a collaborative environment between improving things, and simply stamping them with our own personality. Unfortunately the way commercial websites attract customers is to let them have as much personality as they like because each is compartmentalized into their own little tree. We have a single tree that all users share, so I think it requires looking at things differently. It is easy to rationalize what we want to do, but I try to always bring in some new information or new sources when I change a page, so I am hopefully contributing something of value to offset the intrusion of my personality when I edit a page. I have made several comments in posts about people who edit a page merely to change Abt to abt, or add periods, or similar meaningless changes to a page, on the grounds that if the page communicates what it means, why are people changing it? Simply rearranging things that are already on the page may not be the most productive behavior in a community database because not everybody likes the same way of doing things. Not to mention how annoying it can be interrupted by a change notification that really adds no new information to a page, but merely rearranges my own past contribution!
The biggest problem I had, all jokes about working hard on links aside, was that the source citation you created was not appropriate for about half that stuff in the narrative. Having, in the old days (5-10 years ago, basically before books.google.com and archive.org), driven hundreds of miles to locate various books in a library that ended up not saying what they were purported to say, I have a thing about accurate citations. Since it didn't appear you looked at the source to recognize that it only addressed the second paragraph, it appeared to just be moving things around into a format you liked better. Perhaps not, and please forgive me if I am wrong. But in the name of collaboration, personal preference shouldn't be the sole motivation for a change?? It should be because the item is wrong, or confusing, or misleading, etc.
What could have happened, I think, given the pre-existing format, to make it look more scholarly and documented, was to add footnotes with the ref tag (e.g., <ref name="S1"/>) to show where each fact came from. For example, NEHGR (Vol. 3?) has, I believe, lists of when people were made freeman, and undoubtedly most of the little factoids in that first paragraph come from somewhere like that, be it another page in PCR, or some article in some magazine. So these should be cited, and then footnotes added to the narrative. Also, the {{cn}} template is always good for marking facts we find dubious. And if the narrative is wrong it should be corrected, with the correct information and proof presented. But as a general rule, when things are not provably wrong, perhaps it is necessary to try to accept them as somebody else presented them? Undoubtedly, I'm not perfect at this, either (sheepish :-) , but hopefully mostly on issues where I think using certain features creates difficulties maintaining data consistency, like married name). I monitor my watchlist closely, so I end up complaining a lot, even to people who are contributing good work. Which may not be good in a collaborative environment either, but it seems like each new user comes along and wants to change pages so they are most comfortable for that user, without regard for the people that have worked on it before, or will work on it after this.
Hopefully that makes some small amount of sense even if it's not exactly what you think? --Jrich 06:28, 25 February 2014 (UTC)

Everything you said makes perfect sense. In the spirit of full disclosure, though, there are a couple items I should clarify. Re: married names -- conversations with another WR user have convinced me that they are a positive addition only when the wife's maiden name is unknown because they provide better identification and easier searching. And all joking aside, I still believe for certain religions there is a real difference between baptism and christening. But, how WR handles that is for someone with a higher pay-grade than me to solve! So the status quo is my path forward for now.

I'm sure there are other things here and there we will discuss over time, but in the end, they are all balanced out through collaboration. I like how our back-and-forth has evolved. I value your input. Let's keep it up!--Frank 14:58, 25 February 2014 (UTC)


citation needed [20 March 2014]

The protocol is not to slap {{cn}} on every fact that has no source. The red question mark does that. Nor is it to question the sources that may be supplied, since clearly it is the belief of many people that if it appears in print, it must be true. It is to mark facts with no sources that you have searched for and cannot find, especially if you feel the fact is questionable or unlikely. Of course, if you have a different answer with a good source, you are going to change the fact, so this further suggests the use is only when you can't disprove something. It's real purpose is to warn future readers the fact is questionable, since it gets very little response from the original posters. --Jrich 16:26, 20 March 2014 (UTC)


Niagra and Niagra-on-the-Lake [7 May 2014]

I have just re-directed these places that you added last September to the respective pages that already covered the same places. Has the spelling of Niagara been officially changed?

WeRelate likes to describe places within the municipal structure they were in 1900. This matches the lives of more ancestors than if we were to use, say, the year 2000. I sorted out Ontario on this basis two years ago and, at the same time, attempted to bring in links to the new municipal structure invented since 1970. As you may know some municipalities have re-structured their organization again since this time.

In 1900 Niagara-on-the-Lake was in Lincoln County. The town should also have been linked to Niagara in the "Also located in" box. Perhaps it wasn't.

Unfortunately, the writers of Wikipedia do not always see the necessity of looking at the past as well as the present when writing their pages. Although it is the encyclopedia nearest to hand, it does not always provide the whole information needed by genealogists.

Regards --Goldenoldie 07:02, 7 May 2014 (UTC)


Appreciate the input and your work to correct the record. I was not aware of the "year 1900" naming protocol - haven't seen it discussed in the WR Style Guide or elsewhere. It's good to know of it, though, because I wrestle with naming almost daily -- for example, areas in and around New Amsterdam and Plymouth Colony are especially confusing and frustrating for me. Thanks again for the help...--Frank 12:30, 7 May 2014 (UTC)


Emigration/Immigration [10 June 2014]

Don't think there's a clear answer here. "Emigrated to New England on the Elizabeth and Ann in 1635" If from the perspective of leaving his previous existence, as in went to New England on the Elizabeth and Ann, then perhaps emigrated is the right word, is it not? If from the perspective of beginning his life afterwards, as in came to New England on the Elizabeth and Ann, then perhaps immigrated is the right word. You can look at the trip from both perspectives. --Jrich 00:51, 11 June 2014 (UTC)


Yes, it certainly can be a conundrum. One of the best worded explanations I've found is here [2]. To steal their words:

"Emigrate means to leave one country to settle in another. Immigrate means to settle in a country where one isn't a native. Emigrate stresses leaving; immigrate stresses arriving."

So when I saw the sentence as it was worded: "Emigrate to New England..." using this formula would change to "Immigrate to New England..." Or they could have said "Emigrate from London..."

All for what it's worth...

Best,--Frank 01:10, 11 June 2014 (UTC)


Minor/Miner [30 June 2014]

I can think of one arguable reason to systematically enumerate both the "Minor" and "Miner" variants for the early Connecticut family where that is ambiguous, and that is to ensure the Google searches succeed both ways. (WR searches definitely work without the alt name, but I'm pretty sure Google searches are more literalistic.) --pkeegstra 21:39, 29 June 2014 (UTC)


I'm really struggling with this Minor-Miner-Mynor naming convention as you can tell. My latest thinking was to simplify the pages by removing the extra names because it's such a moving target and because the more streamlined pages are more aesthetically pleasing to me. However, I'd be glad to leave them (or add them) as I go if it would help on web searches. Looking for some direction. As I read your note, you would leave (or add) them?

And while I have you, may I ask your opinion on married names? Originally, I put them in, but as of late have only been doing so when the wife's maiden name is unknown - this to facilitate web searches. Looking for logic for going one way or the other. --Frank 13:31, 30 June 2014 (UTC)

Yes, I would have a fully qualified name with the other variant on each page where the name is ambiguous. e.g. on the page for "Mary Miner" the alt name would be "Mary Minor". (Which leads to the interesting question of how many generations down the name remains ambiguous....) I suppose one could make the same argument for married names in general (i.e. that they're useful for Google searches from e.g. census records) but I would not push that particular argument. The few times I've used married names was for immigrants with Americanized first names and no attestation for their maiden name being used in the US. (FWIW, I also always provide a name prefix of "Mrs." for married names in the US.) --pkeegstra 14:37, 30 June 2014 (UTC)

Thanks. You've been very helpful...--Frank 15:24, 30 June 2014 (UTC)


Date qualifiers [15 July 2014]

FYI: "say abt", "on or bef" are not approved qualifiers. See Help:Date Conventions. The conventions were based on the GEDCOM spec. Bef, Aft, Abt, Est, Cal, Bet is the list. Bef is necessarily inclusive so "on or" is not necessary. "Say" gets used sometimes, as does "ca", but technically neither is a legal value. So obviously people do deviate from the guidelines, but it is very possible the next person to edit the page may change it to follow the conventions. --Jrich 22:10, 15 July 2014 (UTC)


Question [19 July 2014]

Most of those images you're uploading of graves seem to come off of Findagrave. Are you getting permission for all of them?--Daniel Maxwell 02:59, 20 July 2014 (UTC)


Yes, ever since I got feedback from Jrich about copyrights. There may be a couple left over from early on that I haven't found and that don't have the requisite oks. If you see them, please let me know and I'll either remove them or contact the owner...--Frank 03:15, 20 July 2014 (UTC)

Alright. Just be sure to note that on the image page, and credit everyone by name for their copyright. I am normally very flexible and open with copyrights personally (I favor expansion of the public domain), I had some people rip off an image I scanned of my grandfather off of findagrave and then had the nerve to watermark it as 'theirs' on Ancestry, I sympathize with people who find their grave pics on Ancestry or elsewhere all of a sudden. Daniel Maxwell 03:21, 20 July 2014 (UTC)

Will do. With only a couple exceptions, I've found most everyone on FindAGrave amenable to having their photos used on WeRelate. Thanks for the input.--Frank 03:38, 20 July 2014 (UTC)