User talk:WRadmin2

Sourcing Genebug2 William Black.ged Imported Successfully [7 February 2017]

Sourcing Genebug2 Hilda Erikse.ged Imported Successfully [8 February 2017]

Sourcing Genebug2 John Wilson.ged Imported Successfully [9 February 2017]

Sourcing Joevans3 Donald Wisme.ged Imported Successfully [9 February 2017]

Sourcing Joevans3 Jenkin Evans.ged Imported Successfully [11 February 2017]

Grandmapiggy Hackenberg patch.ged Imported Successfully [12 February 2017]

Grandmapiggy Hiram McLaughlin .ged Imported Successfully [14 February 2017]

Next step: Review your GEDCOM [24 May 2017]

You're not done yet!

Now that you have uploaded test tree 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 two 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 19:58, 24 May 2017 (UTC)

test tree 1.ged Imported Successfully [24 May 2017]

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

Now you can:

• Launch the Family Tree Explorer to navigate your tree
• 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 20:13, 24 May 2017 (UTC)

GEDCOM Export Ready [30 May 2017]

The GEDCOM for tree Indexing Christian Bell and Maria Baas is ready to download. Click here.

Samuel Wilson correction [10 August 2017]

Thank you for making the Montreal to Montréal correction. I was making the same kind of correction last night on people at the beginning of the alphabet.

The Wilsons (and the Gibsons) who went to Lanark, Ontario, from Colvend may or may not be part of my tree, but both surnames also appear in my family in Colvend. The main part of my Gibson family had a holding at Auchenlosh, north of the current church at Colvend.

Regards, --Goldenoldie 05:58, 10 August 2017 (UTC)

Even corrections take a little study [21 September 2017]

Person:Isaac Paul (1) Christening location: Dedham, Essex, England|Dedham, Massachusetts First Church. --Jrich 01:30, 21 September 2017 (UTC)

Well, there are a couple of things going on here. The change to which you refer was not one specified by this account, but rather the auto-match program for Places that Dallan added a long time ago. It is set to run whenever a page is opened for editing and therefore was called when WRadmin2 opened the page to perform a different task. It makes some blatant mistakes (ex. IN = India, instead of Indiana), so you will find the site is peppered with some of those. If you have complaints about that program, I refer you to Dallan.

WRadmin2's task was to move "Carpenter" from the Place field to the Description field, but it was not performed on this particular page, since it is case-sensitive, and this page had a lower-case "c". This is a safety check, so it is not a problem. WRadmin2 actually made zero active changes to the page - just opened and closed it (null edit). The changes are attributed to WRadmin2 only because it was the account that opened the page. Had you done the same thing, the same changes would have been attributed to you.

What you see now in the Place field is the result of another automatic edit, namely BobC's attempt to launch a large-scale correction effort last Spring as he was trying to figure out a way to best handle cases where inappropriate text is entered in the Place fields. I wish that he had discussed that plan with others before implementing it, but he did not, so it has added an extra step in the regular clean up process that I am slowly working through. This first pass enacted the redirect. The next one will complete the desired correction.

I hope this explains the changes that occurred on that particular page. These programs are not perfect, but they get it right far more often than they get it wrong. That is why we allow them to run. --cos1776 16:15, 21 September 2017 (UTC)