User talk:Rwbdragon

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:

1. Take the WeRelate tour to see what you can do.
2. Watch the Wiki basics tutorial video to learn how to make ancestor web pages.
3. Explore the Tutorials, if needed.

If you need any help, I will be glad to answer your questions. Just click on my signature link below and then click on the “Leave a message” link under my name in the upper left corner of my profile page. Thanks for participating and see you around! --Ronni 15:52, 13 September 2007 (EDT)

Staton-Rowe.GED Imported Successfully [14 September 2007]

The pages from your GEDCOM, "Staton-Rowe.GED" have been generated successfully. You may view them by launching the Family Tree Explorer and opening the family tree into which this GEDCOM was imported.

-WeRelate agent 21:37, 14 September 2007 (EDT)

Staton-Rowe.GED appears to overlap a previously-imported GEDCOM [26 September 2007]

The pages from this GEDCOM have not yet been generated because they appear to match pages from a GEDCOM you have previously imported to WeRelate.

If you have already imported a GEDCOM containing people in this GEDCOM and you want to replace that tree with this GEDCOM, you need to delete that tree first so duplicates aren't created when you import this GEDCOM. Go to the Family Tree page, scroll down to the bottom of the page, and click on the "delete" link next to that tree. Please be aware that any pages in that tree that are being watched by others won't get deleted. Once that tree is deleted you can create a new tree and re-upload this GEDCOM into it. (We're planning to make re-uploading GEDCOM files much simpler later this Fall.)

If you don't think you have already imported a GEDCOM containing people in this GEDCOM, or if the two GEDCOM's don't overlap that much, leave a message for Dallan or send an email to dallan@WeRelate.org and we'll go ahead with the import.

--WeRelate agent 23:53, 26 September 2007 (EDT)

Staton-Rowe.GED Imported Successfully [26 September 2007]

The pages from your GEDCOM have been generated successfully. You may view them by launching the Family Tree Explorer and opening the family tree into which this GEDCOM was imported.

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

--WeRelate agent 00:17, 27 September 2007 (EDT)

Nicknames, etc. [27 September 2007]

Hi,

I'm Mary, one of the volunteer administrators for WeRelate. I noticed that you had the full name of Jefferson Rowe as "Jefferson D (J D) Rowe." Since we have the ability to add alternate names very easily, I left the primary name as "Jefferson D. Rowe" and added "J D Rowe" as an alternate name. If someone is searching for "J D Rowe," they will find it more easily on WeRelate that way.

Thanks for joining WeRelate!

Mary--Kittydoc 09:19, 27 September 2007 (EDT)

Staton-Rowe.GED appears to overlap a previously-imported GEDCOM [29 September 2007]

The pages from this GEDCOM have not yet been generated because they appear to match pages from a GEDCOM you have previously imported to WeRelate.

If you have already imported a GEDCOM containing people in this GEDCOM and you want to replace that tree with this GEDCOM, you need to delete that tree first so duplicates aren't created when you import this GEDCOM. Go to the Family Tree page, scroll down to the bottom of the page, and click on the "delete" link next to that tree. Please be aware that any pages in that tree that are being watched by others won't get deleted. Once that tree is deleted you can create a new tree and re-upload this GEDCOM into it. (We're planning to make re-uploading GEDCOM files much simpler later this Fall.)

If you don't think you have already imported a GEDCOM containing people in this GEDCOM, or if the two GEDCOM's don't overlap that much, leave a message for Dallan or send an email to dallan@WeRelate.org and we'll go ahead with the import.

--WeRelate agent 00:24, 30 September 2007 (EDT)

GEDCOM Export Ready [26 May 2016]

The GEDCOM for tree Staton-Rowe is ready to download. Click here.

GEDCOM Export Ready [23 December 2020]

The GEDCOM for tree Staton-Rowe is ready to download. Click here.

Hey, Cuz! [18 July 2022]

=

Just wondering if you still work at this website.

Let me know!

=

--Kymokyvash 02:00, 18 July 2022 (UTC)

=

I'm still here, Cuz!

Tough break for you!

=

--Rwbdragon 20:07, 18 July 2022 (UTC)

Next step: Review your GEDCOM [18 July 2022]

You're not done yet!

Now that you have uploaded Spriggs-1.ged into our review program, it is time for you to match your data to ours. Your next step is to review and resolve any potential warnings that your file might be showing and to match place names, source names and families to pages that may already exist in our database.

Notes:

• You must complete all the steps before your GEDCOM can be considered for import. - We will keep your file in the queue for three months to give you time to finish, and you do not have to finish all at once.
• If you did not follow the instructions for preparing your data before uploading your file or if your file does not contain at least one date and place for each person with sources, it is likely that your file will be rejected.
• Volunteers are here to help. Please read the instructions first, but if you get stuck or have any questions, you can leave a message on the page for the GEDCOM review team. One of our volunteers will respond shortly.
• Once you have completed the review and marked your GEDCOM Ready to import on the last screen, one of our volunteer administrators will review the file again and finalize the import. This usually happens within 24-48 hours. Please allow a little extra time around the holidays. When the import is finalized, you will receive a follow up message here on your Talk page.

Click here to enter the review program
You will see more instructions once you are in.

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

--WeRelate agent 21:20, 18 July 2022 (UTC)

Spriggs-1.ged Imported Successfully [19 July 2022]

Congratulations! The pages from your GEDCOM have been generated successfully.

Now you can:

• Explore your tree -- available about an hour after your file has been imported
• View a searchable list of the wiki pages generated from your tree -- available about an hour after your file has been imported
• View your network to see which other WeRelate users are watching pages you have in common. This works if you matched families during your review. You might find a relative here!
• View related pages which are not currently attached to your tree -- may take some time to display for large files. If you matched families in your GEDCOM to existing families in our database, this will show you pages which are also connected, but not currently in your GEDCOM. You can add these pages to your tree.

For questions or problems, leave a message for the volunteers on our GEDCOM review team.

--WeRelate agent 16:45, 19 July 2022 (UTC)

GEDCOM Export Ready [19 July 2022]

The GEDCOM for tree Staton-Rowe is ready to download. Click here.

GEDCOM Export Ready [19 July 2022]

The GEDCOM for tree Spriggs-Twigs is ready to download. Click here.

Next step: Review your GEDCOM [21 July 2022]

You're not done yet!

Now that you have uploaded Fuhs-1.ged into our review program, it is time for you to match your data to ours. Your next step is to review and resolve any potential warnings that your file might be showing and to match place names, source names and families to pages that may already exist in our database.

Notes:

• You must complete all the steps before your GEDCOM can be considered for import. - We will keep your file in the queue for three months to give you time to finish, and you do not have to finish all at once.
• If you did not follow the instructions for preparing your data before uploading your file or if your file does not contain at least one date and place for each person with sources, it is likely that your file will be rejected.
• Volunteers are here to help. Please read the instructions first, but if you get stuck or have any questions, you can leave a message on the page for the GEDCOM review team. One of our volunteers will respond shortly.
• Once you have completed the review and marked your GEDCOM Ready to import on the last screen, one of our volunteer administrators will review the file again and finalize the import. This usually happens within 24-48 hours. Please allow a little extra time around the holidays. When the import is finalized, you will receive a follow up message here on your Talk page.

Click here to enter the review program
You will see more instructions once you are in.

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

--WeRelate agent 20:55, 21 July 2022 (UTC)

GEDCOM Export Ready [21 July 2022]

The GEDCOM for tree Fuhs-1 is ready to download. Click here.

Fuhs-1.ged Imported Successfully [22 July 2022]

Congratulations! The pages from your GEDCOM have been generated successfully.

Now you can:

• Explore your tree -- available about an hour after your file has been imported
• View a searchable list of the wiki pages generated from your tree -- available about an hour after your file has been imported
• View your network to see which other WeRelate users are watching pages you have in common. This works if you matched families during your review. You might find a relative here!
• View related pages which are not currently attached to your tree -- may take some time to display for large files. If you matched families in your GEDCOM to existing families in our database, this will show you pages which are also connected, but not currently in your GEDCOM. You can add these pages to your tree.

For questions or problems, leave a message for the volunteers on our GEDCOM review team.

--WeRelate agent 17:21, 22 July 2022 (UTC)

Recent edits [31 July 2022]

Hello Rwbdragon,

Over the years a number of system administrators have been removing RIN, UID, etc. numbers from WeRelate pages. These were common in the very early years of GEDCOM uploads. So without noticing that you had recently uploaded your GEDCOM I started deleting these numbers that I found on some of your webpages. Actually, I am surprised you were not asked to remove them during the GEDCOM Review process.

On WeRelate it is preferred to use full names of states, etc. such as Kentucky and not Ky or KY. So various people will make small edits to reflect this change on any page they notice still has abbreviations.

I did delete a few Alt. birth lines when it appeared the text was duplicated in the Birth line. Also a few pages had some strange text beginning with the underscore, such as "_xxx".

The fact that a person in your GEDCOM is also listed in a family tree somewhere else on the internet is really irrelevant. WeRelate and Wikitree, for example, are really quite different. Contributors to WeRelate are attempting to provide the best possible PRIMARY source material for the individual whose page they have created. For example some contributors may type out the contents of a person's will, other may upload an image of the will, still others will add a link to the document at familysearch, ancestry, or elsewhere on the internet. Also, since Ancestry documents are not free to view, a link to the ancestry document is acceptable with the hope that you at a later date or someone else will come along and replace the ancestry link with a link to view the document for free.

So far I have not seen any reason to put any of your page on my watch list. Our ancestries come from different areas of USA. My primary reason for viewing your pages is to get rid of RIN's so no future GEDCOM users feel the need to use them on WeRelate.

Thank you for joining and contributing to WeRelate.

Regards, --Susan Irish 20:56, 30 July 2022 (UTC)

-

Thanks for your prompt reply, Susan.

My main concern is whether or not WeRelate.com has any stated policies on these matters.

Please let me know if you know of any such stated policies.

Thanks again.

-

--Rwbdragon 21:19, 30 July 2022 (UTC)

Hi. I'm just going to jump in here because I also make the kinds of changes that Susan does (and I have been in conversation with Julie Kelts). WeRelate Help pages do provide some conventions. See, for example, the style guide, which says not to use abbreviations and acronyms in data fields. Conventions are not hard-and-fast rules, but they are in place (in part) to facilitate matching, which is very important when the goal is to have one page per person. They also help to resolve situations where different people have different preferences on how data is entered or might look. For example, the naming conventions, which state that the first name on the page is to be the name at birth, would be cited if there was a dispute from someone putting a married name in the first entry and someone else changing it to the name at birth. The same convention has also been cited when people argued about putting surnames all in capital letters.

As I've mentioned to Julie, the Help pages are in need of an overhaul, which will likely happen in a few years, and I expect that some conventions may be elaborated in more detail, as was done with date conventions last year. Dates are a rare case where a software change was made to enforce date formatting according to standards, but there is still user judgement in whether to use "abt" vs "est" vs "bef", for example, and we tend to be pretty tolerant of the preferences of other contributors.

On a slightly different note, I noticed that at least one of the pages you are planning to show other people (Person:Louisa Sword (1) was originally uploaded in 2007, which is why it had RIN's. I believe that the GEDCOM upload no longer copies RIN's into WeRelate. Several other changes have been made as well (such as recognizing some tags that previously weren't recognized). If you want to show people what an uploaded page looks like, it really would be best to do a new upload as an example (noting that if you upload the same pages again, the new data doesn't replace the old - instead it requires you to do a merge, which doesn't get rid of stuff such as RIN's unless you choose to do so). If you would prefer to do a fresh upload in the WeRelate Sandbox (test environment), please let me know, as you will need support from either me or Dallan to complete that.

I hope you find WeRelate a good place to work.--DataAnalyst 17:51, 31 July 2022 (UTC) (Janet Bjorndahl, volunteer administrator and programmer)

Source matching during gedcom import [8 August 2022]

Hello - I recently came across the page for Person:Charles Stemshorn (2) which was created during a recent gedcom import, but none of the sources had been matched (linked) to the internal WeRelate source database (i.e., our Source pages). I added the linking for his page, but source-matching is usually part of the import process, so I wanted to check with you to make sure that the instructions were still in place during your import and to ask if you had encountered problems that prevented the source-matching from being completed? Some of the processes here are being updated, so it would be good to know if there has been any impact on other areas. Thank you, --cos1776 17:04, 8 August 2022 (UTC)

-

This profile was from a GEDCOM that I downloaded from WikiTree.com. As such, all the source citations were contained in the profile biographies, so I presume that no matching was possible at import to WeRelate.org.

Regardless, is matching these citations a site requirement? If so, please direct me to the specific guideline pages so that I can learn the relevant requirements.

Thanks!

--Rwbdragon 19:23, 8 August 2022 (UTC)

Thank you for the quick response. When you say "all the source citations were contained in the profile biographies", are you referring to the in-line citation format that WT prefers? I have not imported a WT-specific gedcom before, so I am not sure what exactly you were seeing on the source matching tab, but I would think (hope) that matching is still possible.

Source matching is not required, but it is preferred, since it can be part of the benefit of working in a wiki. We try to follow the one-page-per-source rule for the Source database as well, but it can be difficult to monitor and maintain with all of the different programs and formats in use, not to mention the use of derivative, secondary, etc. sources. --cos1776 21:05, 8 August 2022 (UTC)

-

I should have said the text box, which contains the biography and all source citations at WikiTree, whether they are inline or listed separately. WikiTree does not have separate entry boxes for citations like WeRelate has. The biography and citations are all contained in the text box, thus the citations apparently import into the text box here. I don't recall if I was prompted to separate the citations before importing my GEDCOM here.

I am currently trying different methods as I edit the profiles from my GEDCOM. I do feel that cleaning up my GEDCOM in stages will work better for me, so I am leaving any source matching for later. Obviously, other members are free to collaborate on these profiles.

Thanks for your input!

-

--Rwbdragon 22:07, 8 August 2022 (UTC)

GEDCOM Export Ready [12 October 2022]

The GEDCOM for tree Spriggs-Twigs is ready to download. Click here.

GEDCOM Export Ready [12 October 2022]

The GEDCOM for tree Fuhs-1 is ready to download. Click here.

GEDCOM Export Ready [12 October 2022]

The GEDCOM for tree Staton-Rowe is ready to download. Click here.

Recent Edits [30 July 2023]

Hello Rwbdragon,

As I look back at some of the edits to your webpages it appears that I was standardizing place names. Also RIN, etc. have no place on WeRelate and are routinely deleted when found. I see that you added a great Kentucky marriage source.

Thank you for choosing to participate on WeRelate. --Susan Irish 19:59, 30 July 2023 (UTC)