ViewsWatchers |
[add comment] [edit] WelcomeWelcome 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 02:28, 22 September 2022 (UTC) [add comment] [edit] Next step: Review your GEDCOM [21 September 2022]You're not done yet! Now that you have uploaded George Family Tree (20minimum).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:
Click here to enter the review program 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.
[add comment] [edit] Next step: Review your GEDCOM [22 September 2022]You're not done yet! Now that you have uploaded George Family Tree (22mini).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:
Click here to enter the review program 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.
[add comment] [edit] Next step: Review your GEDCOM [23 September 2022]You're not done yet! Now that you have uploaded George Family Tree (31).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:
Click here to enter the review program 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.
[add comment] [edit] Next step: Review your GEDCOM [23 September 2022]You're not done yet! Now that you have uploaded George Family Tree (35).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:
Click here to enter the review program 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.
[add comment] [edit] Next step: Review your GEDCOM [24 September 2022]You're not done yet! Now that you have uploaded George Family Tree (38).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:
Click here to enter the review program 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.
[add comment] [edit] Next step: Review your GEDCOM [24 September 2022]You're not done yet! Now that you have uploaded George Family Tree (39).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:
Click here to enter the review program 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.
[add comment] [edit] Gedcom import review [26 September 2022]Hello, Pauloz, I've been been reviewing your import submittal of "George Family Tree (39).ged". From the above messages, I gather you have been making revisions to your data to get it ready for inclusion here, which I don't doubt took a good deal of effort. Your file is very large (2,800 people) and it's difficult to get all the problems ironed out for so much data. It's also hard to find all the problems during review, and so although I'm returning the Gedcom to you for further adjustment, with such a large file it's somewhat unlikely that I have found all the issues that might block acceptance and import of the data. I will say that I found fewer serious problems than I expected to find with a file of this size. One issue that has to be fixed is that there are people entries which have emoji (picture characters) in their surnames, and these need to be removed. The only form I'm currently aware of is people who have a "DNA" emoji ("🧬", Unicode "U+1F9EC = Dna Double Helix Emoji") after the letters of their surname. A search showed there were 70 such persons, and the emoji need to be removed from their names. (I've never used AncestryDNA, but I'd guess that it may have been the source of these "helpful" markers.) A few other Person entries have different surname problems needing to be fixed. One type is where alternative spellings have been included in the surname separated by a backslash ("\"). One case is "Thomas Combellack\Carnbullack\Carnbellack". He should have one of the spellings chosen for the primary surname version. The alternative spellings can be simply listed in the textual notes for the person, or, for more thorough indexing, can be included in separate "alternate name" fields in the Gedcom, which whatever software you are using hopefully supports in a reasonable manner. If you want more detail on alt names, I see there's a lot more information on another site's older page. There are other entries which put alternate surnames in parentheses following the primary name spelling. These could be handled similarly to the "\" case, but it seems like the WeRelate software handles these better and I'm guessing changing them is not strictly necessary. There's also "Carroline Hogben Nee Gower", who should be changed to "Carroline Gower" as birth name is the standard on WeRelate; the married name isn't normally explicit (although it can be, in an "alternate name") because searches take into account the possibility that the wife may have used the surname of the husband. That's all I noticed in this review that requires changing. No guarantees that there's not more, though. You might find it easier to submit in smaller pieces, but that's up to you. If need further help or want to discuss things, you can reply below (I'll have this page on my "watchlist"), or post on my "talk" page, or on the Support page, which is linked under "Help" at the upper right of every page. --robert.shaw 21:17, 24 September 2022 (UTC) Hi Robert, Thanks for your comments. You said that you were returning my GEDCOM to me for further adjustment. I was presuming that I could delete that one and replace it with a new GEDCOM that had fixed all the issues you raised. However I am unable to remove the current GEDCOM as it appears that I have to wait for an administrator to finalize the import. And I cannot import the corrected GEDCOM as the current one is waiting. I am confused about what to do next! My preference would be to delete the current GEDCOM and import a new one. Cheers, Paul--Pauloz 02:12, 26 September 2022 (UTC)
[add comment] [edit] Next step: Review your GEDCOM [26 September 2022]You're not done yet! Now that you have uploaded George Family Tree (45).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:
Click here to enter the review program 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.
[add comment] [edit] Next step: Review your GEDCOM [26 September 2022]You're not done yet! Now that you have uploaded George Family Tree (46).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:
Click here to enter the review program 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.
[add comment] [edit] George Family Tree (46).ged Imported Successfully [27 September 2022]Congratulations! The pages from your GEDCOM have been generated successfully. Now you can:
For questions or problems, leave a message for the volunteers on our GEDCOM review team.
[add comment] [edit] Please help us improve data quality [28 September 2022]Hi Welcome to WeRelate! We have recently begun a (currently low-key) data quality improvement initiative, and I invite you to take part by addressing the outstanding issues in your new tree. To do so, select the menu item My Relate > My Trees (top menu) and then select the link labeled Check beside your default tree. Once you see the list of issues (which may take as long as 10 seconds to show up), click on the link Help:Monitoring Data Quality and read the instructions carefully. My cursory check of some of the "anomalies" indicates that they are in fact errors (e.g., Mary Dunstan, born more than 2 years before the marriage of the parents she is linked to, was the daughter of William Dunstane, not Wearne Dunstan). Also, note that the issue of multiple sets of parents should really be considered an Error, not an Anomaly - please don't mark any of these as verified. Please don't feel rushed to address the issues - the goal is to ensure high quality data and sometimes that takes a while to discover. If you need help, please ask on my Talk page. Thanks--DataAnalyst 15:37, 28 September 2022 (UTC) (Janet Bjorndahl, Volunteer WeRelate administrator) [add comment] [edit] Hello [15 August 2024]Hi Pauloz. It looks like you have done some amazing work on John Lewis (1806-1866) and wife Elizabeth Mason (1810-1851). I am a descendent of theirs via John Thomas Lewis, who's daughter Alice Harriet Lewis is my great grandmother. Would it be possible to contact you? My email is stackee@gmail.com. I live in Castlemaine Victoria. I have found John Lewis's grave at Chewton Cemetery and wonder if i could ask you about it. Thanks Leon--Stacky 11:42, 15 August 2024 (UTC) |