tag:blogger.com,1999:blog-5512311610334754148.post3478732182988874898..comments2023-04-20T12:46:11.858-06:00Comments on The Ancestry Insider: Answers to Indexing IllustrationThe Ancestry Insiderhttp://www.blogger.com/profile/02490682912125335188noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-5512311610334754148.post-62242986026189945402010-11-19T12:52:50.589-07:002010-11-19T12:52:50.589-07:00Really interesting exercise. I printed your column...Really interesting exercise. I printed your column to take the test in another room, and accidentally discovered -- if I hold the page almost flat at eye level, with bottom right corner pointed toward my nose, I could READ all the names except *3, and that one I guessed. (Yes, knowing they were presidents,helped.) No, I'm not suggesting indexers do something similar. AI, try this for fun. Your point, about indexing, is well taken, however. Cheers, Dolly in MarylandAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-13604186393615646132010-11-19T12:13:21.438-07:002010-11-19T12:13:21.438-07:00You have misspelled the name of Ronald Reagan.You have misspelled the name of Ronald Reagan.George L. Triggnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-50480834557488821222010-11-19T12:00:44.493-07:002010-11-19T12:00:44.493-07:00whoa! you mean I'm NOT from India? so much t...whoa! you mean I'm NOT from India? so much to change in the file now! (hee hee) Ancestry does allow you to suggest changes for a record where there is a transcription error, so that helps a little bit.Celtic Treehttps://www.blogger.com/profile/00722841959389221214noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-44163489855329644122010-11-19T09:39:16.113-07:002010-11-19T09:39:16.113-07:00And don't forget that spelling counts, too. H...And don't forget that spelling counts, too. His name was Ronald Wilson <b>REAGAN</b>.<br /><br /><i>Happy Dae·</i><br />http://ShoeStringGenealogy.comHappyDaehttps://www.blogger.com/profile/04960993272772122243noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-17564469440231237382010-11-18T17:38:19.419-07:002010-11-18T17:38:19.419-07:00It's absolutely true that cold indexing is ver...It's absolutely true that cold indexing is very difficult and error-prone, having done a lot of that myself (undoubtedly with lots of errors...). But I'm really glad that there is so much available out there, errors and all. Just means you have to be very smart, flexible and creative, when searching. And means you learn long lists of "likely errors" for different kinds of names, times and records. At least the info is *there* when you finally figure out where *there* is.LindaSnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-73168653322750797832010-11-18T17:24:05.232-07:002010-11-18T17:24:05.232-07:00Yes, but if we had to wait for someone in "ea...Yes, but if we had to wait for someone in "each county" "whose family has lived there for several generations" to create indexes for the genealogical records we need, we would be waiting for decades or longer. I would rather have millions of records available sooner with a marginally lower quality index than have to wait for the perfection that so many seem to be seeking.<br /><br />A good search engine (like the one on Ancestry.com) allows you to tweak searches looking, for example, for all males born between 1870-1880 in Ohio, living in Multnomah County, Oregon - without having to enter a name at all. I can browse through four or five pages of search results and find my people amost every time. In addition, light indexing allows images to be posted in smaller chunks of data that I can browse when I find other family members in the proximity - which I would hope most people do anyway.<br /><br />Lastly, I'm convinced that if all of our research really was as simple as the push of a search button to find perfectly indexed records, many of us would get bored very quickly. The challenge of it all is part of what keeps me engaged. And, I feel more connected to those I have had to struggle a bit to discover.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-57554787341100361652010-11-18T16:05:15.285-07:002010-11-18T16:05:15.285-07:00I have to admit to looking at other sources for th...I have to admit to looking at other sources for that "context" when I can't read something in a record. For example, if I'm indexing 1898 Illinois Marriages and can't figure out a name, I look for the couple in the 1900 census. I'm not sure if that's kosher, but it sure helps me transcribe unusual names. I also select indexing projects from locations where I have some research experience. It really does help.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-28937114323144537602010-11-18T09:09:41.210-07:002010-11-18T09:09:41.210-07:00I've become somewhat obsessed with correcting ...I've become somewhat obsessed with correcting my ancestors' indexing errors on Ancestry.com. Some of the French Canadian records I search were so far off that even quite experienced local genealogists could not find the records! It makes me feel good to know I'm helping the next generation of researchers looking for a common ancestor. <br /><br />My next question is: What to do about records that are not indexed at all?? I found one essential birth record by sheer time & persistance, because for some reason there was no indexing.AuntieSmedleyhttps://www.blogger.com/profile/01063390457149214868noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-40022846546193584522010-11-18T08:24:53.899-07:002010-11-18T08:24:53.899-07:00This is so true. I have done indexing and it is s...This is so true. I have done indexing and it is sometimes hard to read some of the names. I make corrections on Ancestry's index for my families that have been mis-indexed, but I can clearly see how the indexer came up with their view of the name.Lisa S. Gorrellhttps://www.blogger.com/profile/06086125812111254305noreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-26353982767181545092010-11-18T07:43:59.006-07:002010-11-18T07:43:59.006-07:00Indexing is even more difficult when the original ...Indexing is even more difficult when the original is spelled incorrectly. Presumably your third example was intended to illustrate this? :-)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-61889528303197016972010-11-18T06:09:33.243-07:002010-11-18T06:09:33.243-07:00Yeah, context is very helpful. I love how many pe...Yeah, context is very helpful. I love how many people in the census are from India in 1850-1880. When census enumerators wrote "Ind." and the person is named Charlotte Smith or something like that, and yet the birthplace is transcribed as India, I just have to laugh. I wonder where Ancestry's outsourcing the transcription to?Bradnoreply@blogger.comtag:blogger.com,1999:blog-5512311610334754148.post-45892859821446709102010-11-18T05:20:23.823-07:002010-11-18T05:20:23.823-07:00Your 'knowing the context' illustration wi...Your 'knowing the context' illustration with the presidents' names proves what I have always believed - each county should be indexed by people whose family has lived there for several generations. They will recognize the names in spite of the handwriting.Anonymousnoreply@blogger.com