Gene, What you seem to be suggesting is that users should be able to change the data supplied by other users. Who is expected to say that that so called "correction" is accurate?
Personally I would take strong exception to anyone changing my data without my explicit consent. I know the odd persons who disagrees with some of my data, but then I disagree with their's. So who is correct? Ron Ferguson http://www.fergys.co.uk/ From: Gene Adams Sent: Wednesday, January 19, 2011 5:02 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: Slight OT: [LegacyUG] It's official - Legacy 7.5 is now available Deb & others I agree with the main part of your soapbox, but for one comment at the end. " The IGI is merely a "pointing" tool to help you identify a place or person to who you might look further." That was the main argument I had...the "tool" was definitely pointed in the wrong direction...by at least 1000 miles...and no possibility of correcting the mistake even with valid supporting documentation. Since Legacy is tying into these databases, and we as users are trying to pull together accurate information and documentation for our ancestors...it needs to be accurate as possible. And when non-existent people are found or major duplication of in "different branches" of the trees we are building...This should have some means for correction or review. Years ago, the AFN system was set-up to allow for corrections, then that disappeared as that system of unique identifiers went down the tube [Many of us have ancestors with at least 3 or more "unique" ID's (I have found one with at least 10)]. So where can we get these corrected and eliminate corrupt data that is continues to be proliferated? Now I will get off my soapbox. Gene A From: Deb <lds...@bellsouth.net> To: LegacyUserGroup@LegacyUsers.com Sent: Tue, January 18, 2011 9:55:21 PM Subject: Slight OT: [LegacyUG] It's official - Legacy 7.5 is now available Gene & others. The IGI can not be edited. It is an index of individuals (real or not) for whom an ordinance was performed at a specified Temple on a specified date. The information given in the index which is claimed to be wrong merely identifies the individual/individuals (existing or not) for whom these ordinances were performed. Yes there are persons identified who never existed. (John Doe married Jane Smith on 12 januvember 1429 ss 12 Jun 1993 Atlan.) On Jun 12 1993, someone requested and had performed a spousal sealing of a John Doe and Jane Smith who were married on the 12th of Januvember 1429).. If there never was a john doe and Jane Smith who were married, or if the date or place of a factual marriage was different, then the ordinance was not for them.... Our family has been blessed to have an uncle who wrote a letter about his family and their whereabouts in 1895. He goes back to some ancient history (1790-1820), and makes an innocent comment about "his uncle John Weaver", and because of that one comment, there have been about 20 people misidentified in the family. Many of these show up in the IGI. There are an additional 7 of his nieces misnamed and given incorrect spouses. I have found many similar errors in Census Indices, marriage transcriptions, cemetery records etc. Regardless of the source, or the informant, all data should be carefully evaluated. The IGI is merely a "pointing" tool to help you identify a place or person to who you might look further. Stepping off my soapbox now.. Deb -------Original Message------- From: Gene Adams Date: 1/18/2011 7:31:50 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] It's official - Legacy 7.5 is now available The problem is that there is a repetitive mistake in records that have no capability of being changed. I have asked at the desk in Salt Lake how to correct massive errors on an entire family that is listed in the IGI. Not possible. So anyone tracing the family will be looking for records in "MD" [Maryland], when it should be MO [Missouri], or worse yet repeating the bad information. Stubby fingers entering data should be correctable...as well as the middle name of my grandmother. Gene A From: Eliz Hanebury <elizhg...@gmail.com> To: LegacyUserGroup@LegacyUsers.com Sent: Tue, January 18, 2011 3:11:32 PM Subject: Re: [LegacyUG] It's official - Legacy 7.5 is now available They do each record twice and then it goes to an arbitrator. I have family where the year changed by 3 seemingly at random. Eliz On Tue, Jan 18, 2011 at 6:01 PM, Jennifer Crockett <jcrock...@optusnet.com.au> wrote: > Well it doesn't give me much faith that any of the records can be taken at > face value. Instead of a mad rush to index everything, surely cross > checking, or having at least one other person verify correct recording > should have taken place. If the image was available it wouldn't matter so > much. > > Regards, > > Jennifer > http://colston-wenck.com > > -----Original Message----- > From: Eliz Hanebury [mailto:elizhg...@gmail.com] > Sent: Wednesday, 19 January 2011 9:47 AM > To: LegacyUserGroup@legacyusers.com > Subject: Re: [LegacyUG] It's official - Legacy 7.5 is now available > > I have to say, the errors are often of the people giving and taking > down information. There is currently no way to correct errors, they > [Support at familysearch] say some day there will be, but they are > concentrating on making a site that will work. > > > Eliz > > On Tue, Jan 18, 2011 at 5:44 PM, Jennifer Crockett > <jcrock...@optusnet.com.au> wrote: >> I am not LDS. I have accessed one of the new collections recently and >> found errors. What can one do about this? See below. The bride's date of >> birth should be 6 July 1837 not 6 Dec 1837. The place of marriage was not >> Karby, but Redsted. I know this from the online Danish Archives which >> show original images. I verified the correct details with the image of >> the marriage record and the death record for Else Anderson. >> >> Denmark Marriages, 1635-1916 >> >> Groom's Name: Peter Villadsen >> Groom's Age: 24 >> Bride's Name: Else Andersen >> Bride's Birth Date: 06 Dec 1837 >> Bride's Age: 29 >> Marriage Date: 12 Oct 1866 >> Marriage Place: Karby, Thisted, Denmark >> >> Indexing Project (Batch) Number: M01212-8 >> System Origin: Denmark-EASy >> Source Film Number: 410117 >> Reference Number: 5-185-6 >> >> There was no image associated with this LDS record. I just want to warn >> people that not all these types of records are error free. >> >> Regards, >> >> Jennifer > > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages after Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > > Archived messages from old mail server - before Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
