User talk:GrapeBunch

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:

• Take the WeRelate tour to see what you can do
• Watch the "Getting Started" tutorial videos and learn how to make wiki pages for your ancestors
• Explore the Step by step Tutorials, if needed
• Create a User Profile page to tell other people about yourself and the families you are researching
• Read the etiquette page to learn expected behavior on a wiki
• Find other ways to get involved on the community portal
• Ask questions on our Support page

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 07:01, 29 January 2016 (UTC)

Next step: Review your GEDCOM [29 January 2016]

You're not done yet!

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

Now that you have uploaded BerryTree05_2016-01-26.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:12, 29 January 2016 (UTC)

Next step: Review your GEDCOM [7 February 2016]

You're not done yet!

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

Now that you have uploaded BerryPass2.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 00:01, 8 February 2016 (UTC)

Next step: Review your GEDCOM [19 February 2016]

You're not done yet!

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

Now that you have uploaded BerryThursday.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:16, 19 February 2016 (UTC)

Legacy and gedcoms [22 February 2016]

Hi

I'm not Dallan but messages to him can be read by a lot of us on WR. I'm another Legacy user, but I brought my family in one by one--it's not large and I don't really trust GEDCOMs to transfer data tidily. Your note reminded me:-

There's one thing that Legacy likes to do which looks clumsy in a different website like WR--that is, adding forward commas in the name of a place. I am sure there is a way of removing them all at once. They do have a "find and replace" tool in there much like you find in Microsoft Office. If the contributor doesn't know precisely where someone was born or died, "Illinois, United States" looks much better to another family historian than ",,Illinois, United States" or ", , Illinois, United States". And, street addresses go in our Description box.

We have a huge worldwide places database, but preceding commas and street addresses don't need to be in it.

Hope you don't have too much trouble with the GEDCOM transfer.

/cheers

--Goldenoldie 19:19, 19 February 2016 (UTC)

Hello, Goldenoldie

I knew that the Location leading comma was a potential problem in Legacy reports, but Legacy 8 has options to suppress single and double leading commas in such reports. I was not aware that leading commas continued to be a problem in GEDCOMs exported by Legacy. I don't see it in the GEDCOM that I uploaded. There are no extra commas, and a goodly number of my Locations will have a Matched Page here, when I find a GEDCOM standard that will properly carry over the Living status of each individual.

Your answer to my GEDCOM question is M: None of the above. Hah!

I think that data should be entered with care, and if possible only once. My notion that errors should not be created, nor should they be propagated, is unrealistic and too idealistic for the Real World. Sigh.--GrapeBunch 22:35, 19 February 2016 (UTC)

I do not use Legacy, but you should be OK with Gedcom 5.5.1. I agree data should only need to be entered once and without errors propagating, I do not feel that is unrealistic to expect, but many researchers are family historians more than genealogists. I prefer less data if it is accurate.

As for the gedcom bringing the correct living status with it, it is much better if you do not allow living people into the gedcom at the time you create it, they are not allowed into WeRelate anyway and several of the admins spend hours each day deleting living people and possibly living people pages, if there is any doubt about whether someone in your tree is alive then do not add them. I see your currently in review gedcom has over half the people excluded as they are living which only makes your review harder. The way I imported most of my research was to add ancestors of a known dead person in my maternal line, then a separate ancestors of a known dead person in my maternal line and I now add small family groups of perhaps a dozen people at a time, these are the siblings of my direct line which will eventually join my cousins lines. I am not entering data twice and small imports allow me to check and update sources as I go.

I noticed there were no sources at all in your gedcom, is that a function of the way Legacy exports? = Rhian 15:48, 20 February 2016 (UTC)

Hello, Rhian:

I was disturbed to read that others have access to my tree before I import it. I'm assuming that it would only be tree statistics and not specifics relating to the individuals in the tree. But just in case, I deleted the pending tree.

There are no sources because the person who input the original data in their software did not use sources, or that software did not allow sources, or the person did not bother to include them in the GEDCOM sent to me. In adding 25% new individuals to the tree, I didn't see a point in adding sources to my data, and in any case mostly there were not any sources more reliable than "hearsay". You know, internet sites that claim to be transcribed from the original birth records, that sort of thing. As reliable as hearsay.

If WeRelate volunteers are wasting time culling living persons out of posted family trees, wouldn't time be well spent to make the filtering software work properly? I would be mortified if specifics related to living persons became public due to it being imported by me.

While on the subject of suggestions to computer programmers, the filters now throw an "alert" when a note for an alternative birthdate is earlier than the actual birthdate. Also when an alternative death date is later than the actual death date. There was one other silly warning, but I seem to have deleted the pending tree. Hah!

Legacy 8 does not provide the ability to produce a GEDCOM consisting of only living persons from the database. Legacy 8 *does* provide the ability to filter living people out of *Reports*, but this is not working for me, despite some attempts to help by their staff.

If researchers are maintaining separate databases for living versus deceased individuals, they are creating work for themselves and asking for errors to propagate. Such measures should not be necessary as every individual record has a flag to indicate whether the person is living or not. You can see that flag every time you access the record, in Legacy at least. I'm a newbie to genealogy, but doesn't GEDCOM allow representation of this one-bit of data?--GrapeBunch 02:36, 21 February 2016 (UTC)

Well, shut my mouth. Legacy *does* have the option to export only the records of dead individuals to GEDCOM (it's just not in the place I was looking). Even better, it seems to work where the same option for Reports did not work for me. Legacy's tally is 190 individuals, 82 families. Of course, it's following Legacy's strictures ("Exclude living people totally (as if they did not exist)") rather than WeRelate's. Tomorrow might be a good day to finally run the gauntlet on the tree.--GrapeBunch 06:22, 21 February 2016 (UTC)

To put your mind at rest, before it is imported your tree is not publicly viewable, some admins do have the ability to check uploaded but not imported trees so they can assist members getting their data imported and the final check before importing is always done by an admin. The filter system for living people does work better than it did 5 years ago but some people are very creative in posting details of living people. The alerts you mention are just warnings, there can be cases where a birth date and a baptism date were swapped in error, these warning are just to ensure there is not a silly mistake getting in, they will not prevent import but you do need to check them.

My own research database is about 20k people, including living and speculative family members, my WeRelate imports are about 10% of that and will probably not get above 20%, I do not see this as creating work, it is more a case of controlling that what is published to be as accurate as possible. I try never to add anything without at least one source, but not having sources will not prevent a gedcom import. I am not sure why you think Legacies policy of treating living people as if they did not exist is any different to WeRealte's, that is how WeRelate treats them.

Good luck with your import and your future research.Rhian 09:00, 21 February 2016 (UTC)

I assume you are happy to accept the warning on the gedcom, from previous discussions I do not see a problem, some will automatically get corrected if we can find sources. Your gedcom is importing now, you should be informed of it's progress soon, I hope you have fun working on WeRelate, any problems please feel free to contact me or any other admin, or post questions on the water cooler page.Rhian 08:43, 22 February 2016 (UTC)

Next step: Review your GEDCOM [21 February 2016]

You're not done yet!

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

Now that you have uploaded GenericDead.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:21, 21 February 2016 (UTC)

GenericDead.ged Imported Successfully [22 February 2016]

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

• launch the Family Tree Explorer to navigate your tree
• view your network -- If you matched families in your GEDCOM to existing families, find out to which other WeRelate users you are related.
• view related pages not in your tree -- If you matched families in your GEDCOM to existing families, find out which people you are now related to that you can add to your tree (takes awhile to display for large trees).
• view a searchable list of the pages in your tree -- The searchable list will be available about an hour after your tree has been imported.

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

--WeRelate agent 08:48, 22 February 2016 (UTC)

GEDCOM Export Ready [24 February 2016]

The GEDCOM for tree Berry is ready to download. Click here.

Re-corrections [10 May 2016]

I would not have messed up your family if you had put a note about the unusual given names under the family tree.

I look at an awful lot of improbable family trees in the course of improving WR's places database--a job I do 8 hours a day.

You are probably more capable than I in putting them back the way they ought to be.

Regards --Goldenoldie 21:59, 7 May 2016 (UTC)

So, it does not seem to be a community norm that the person who makes a mess in the kitchen, then cleans it up. This cannot turn out well. Actually, I don't know how to reverse (or delete) changes. When one clicks on edit the change, one is taken to a page where one may edit the record. Nor do I know how to ban certain users from changing the tree I uploaded. I'm a newbie.--GrapeBunch 15:56, 9 May 2016 (UTC)

As you do not 'own' any pages you cannot prevent anyone from editing them. The easiest way to undo edits is to use the history button, go back to where you think the page was more correct and save it. As to who made the mess in the first place that is another matter, with this families strange naming conventions perhaps creative use of the alterbative name possibilities would work better, if you need advice please ask.--Rhian 07:23, 10 May 2016 (UTC)