Member Tree Searches - When Places don't match
By Geoffrey Slinker, Ancestry Employee The postings on this site are my own and do not reflect the views or opinions of Ancestry. The place for an Event may not be found in the "place system". This leads to what are known as "normalization" issues. Consider this normalization example where the user can enter any of these: Glasgow, Barren, Kentucky Glasgow, Barren County, Ky, USA Glasgow, Barren Co, Ky, USA All of those represent the same place. Therefore when the data is entered it is normalized into one representation. Glasgow, Barren, Kentucky, USA That is "normalizing". That way no matter which representation of the place you use it will convert to the normalized place and then any data that has that normalized value will be found in a search query. https://www.ancestry.com/search/collections/1030/?name=_Slinker&birth=_Glasgow+Kentucky&birth_x=_1-0&count=50&name_x=psi_1 https://www.ancestry.com/search/collections/1030/?name=_Slinker&am