What's more, there is a strong warning before adding gedcom to check for any record already in the nFS. David Samuelsen Sahara346@aol.com wrote: > In Nebraska, we heard within DAYS of going on line not to add a GEDCOM > unless we had checked first to make sure all the individuals on the GEDCOM > weren't on NFS first. For some converts, it works out ok to add a small > GEDCOM, but many find they have ancestry already in NFS before they go very far > at all. > > Karen > > PS: Does anybody know a JSBerry, or someone whose name could be shortened > to that? They've got my friend's grandparents on reserve and not doing a > thing with the names for over a year now. Whoever it is, they're not as > closely related as she is...and nobody had contacted her about permission to > do the work, as we've been reminded strongly of in the last few days. > Whoever he/she is, they did not have the information quite correct, but it is > the same person, nonetheless. Katherine has now gone through the Temple and > could do all of her Grandmother's ordinances, but we can't find out who > submitted the work. > > > > > In a message dated 6/16/2009 7:21:53 P.M. Central Daylight Time, > sjkelsey@msn.com writes: > > I noted today on some records on my namesake 1847 Utah Pioneer ancestor > that > Someone had added a complete gedcom on his family which added duplicates to > ALL of many children and their husbands and wives--what a mess when just > 3 weeks ago I had it nearly all fixed and good. If the people that come > on line from Utah and Idaho add gedcoms of their pioneer ancestry,then > the duplication and combining effort must all be done again. > Perhaps adding gedcoms should be suspended for a while while they come on > line > To prevent the rush to "do something." > > Stephen Kelsey > > > -----Original Message----- > From: lds-ward-consultant-bounces@rootsweb.com > [mailto:lds-ward-consultant-bounces@rootsweb.com] On Behalf Of Nancy Scott > Sent: Tuesday, June 16, 2009 4:05 PM > To: lds-ward-consultant@rootsweb.com > Subject: Re: [LDS-WC] When to stop combining > > Jill, > > I agree that it is important to test. If John Vilburn tested it as he says > he has and he says that it is untrue, I am happy to believe that. > > It was a true disappointment to have Dave Vickers, who is known as a > computer guru, say that the duplications are only combining for our own > lines. > > I am going to take a break and fix dinner but I would like to see it for > myself. > > Nancy > > > > -----Original Message----- > From: lds-ward-consultant-bounces@rootsweb.com > [mailto:lds-ward-consultant-bounces@rootsweb.com] On Behalf Of Jill N. > Crandell > Sent: Tuesday, June 16, 2009 05:56 PM > To: lds-ward-consultant@rootsweb.com > Subject: Re: [LDS-WC] When to stop combining > > Nancy wrote: > I did not intend to mean that we would permanently not combine large > records > when I posted the "Instruction for Members with Pioneer Ancestry". I was > trying to say that now is perhaps not the time to attempt to start > combining > while Utah and Idaho are coming on. While the pioneer ancestors probably > win > hands down for duplication of work, I do have early lines that have the > same > issues. > > Nancy, I was pretty sure you knew that this was not a permanent > instruction. > However, I started seeing people misunderstanding what you were saying, so > I > thought I would try to clarify. The bottom line is that we currently have > to > work with IOUSs, which I agree is also a problem with Mayflower people and > lots of New England ancestors in addition to the pioneers, but once that > problem is solved, the end goal is to combine all duplicate records of the > same person. Any that can be combined now, do it. Any that can't, wait for > the resolution of the IOUS problem and then go at it again. > > As for the combining for our own tree only, please see the email I just > sent > and let's test it! That's something important that we need to know. > > Jill Crandell > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to > LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to > LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' > without > the quotes in the subject and the body of the message > > > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to > LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to > LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' > without > the quotes in the subject and the body of the message > > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to > LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to > LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the > subject and the body of the message > > > **************An Excellent Credit Score is 750. See Yours in Just 2 Easy > Steps! > (http://pr.atwola.com/promoclk/100126575x1221823265x1201398681/aol?redir=http://www.freecreditreport.com/pm/default.aspx?sc=668072&hmpgID=62&bcd=Jun > eExcfooterNO62) > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message > >