How do I point out an error in a result of a Search for "Genealogies" ?

PeterBrown84

I just did a search for Genealogies, for Peter Boyle, Carlingford County Louth Ireland, 1876

The top result as was for information I submitted some time back to Ancestral File.

The search result shows place of death as Doncaster, Victoria, Australia, and buried in Doncaster, South Yorkshire, England, United Kingdom.

When I click on Peter Boyle (shown in red on my Mac) the record shows correctly death in Doncaster, and burial in Doncaster, England.

I fully understand that the information in Ancestral File may not be changed.

But somehow the search result has decided that Doncaster, Victoria, Australia was the place where the death occurred.

Julia Szent-Györgyi

It looks like they're applying autostandardization-on-the-fly to Genealogies now.

Russ Test

I just did a search for Peter Boyle, with Death place of Doncaster, England, and found the what may be your Peter Boyle.  

Some times the FamilySearch Records search engine will include Cities from other countries. 

We just have to research a little to rule out the wrong ones. Please try this again. If you are still seeing the wrong locations, please include more details, i.e. the link, film number, etc. 

Thanks for using FamilySearch. 

PeterBrown84

Thanks for taking the time to respond.

I did do another search. I may have erred in the details in my initial comment.

I appreciate that one might have to research a little to rule out the wrong ones.

It is likely I was the original source with my Ancestral File submission.

This search came up with my uncle Peter Boyle who was born in Doncaster England - same address as my mother who was born in 1915.

I've edited the Family Tree entry to reflect his birth in Doncaster Yorkshire England.

Maybe in time the search engine will catch up

https://www.familysearch.org/search/tree/results?q.anyDate.from=1939&q.anyPlace=Doncaster&q.givenName=Peter&q.surname=Boyle

PeterBrown84

If one uses the 'Genealogies' option, given it seems based on Ancestral File, it may for ever reflect Doncaster Australia.

Maile L

@russellwaltgeorge1 I think Peter is referring to Search>Genealogies https://www.familysearch.org/search/genealogies/results?q.anyDate.from=1939&q.anyPlace=doncaster&q.givenName=Peter&q.surname=Boyle

https://www.familysearch.org/ark:/61903/2:1:MCBF-2KB

Maile L

It appears this cannot be fixed right now. Do you have the original gedcom that this was loaded from? I wonder if replacing it with a version that has fully stardardized place names would be the best solution.

Gordon Collett

@Maile L do you have any information as to whether this unfortunate design decision for the search results list is actively being working on or is at least high on the priority list for being fixed? This is the same problem seen when searching historical records in which the search result list displays a wrong place because the program attempts to "standardize" the place name when the actual record has insufficient information to do this anywhere near correctly. In these cases the record's place name has not been modified at all from the original indexing:

I still have not come up with a single situation where I would prefer that the results list makes up a place name rather than just show me what the record will say when I open it.

Since the problem reported in the starting post for this discussion is in the Ancestral File, it cannot be updated and I doubt uploading a new GEDCOM into the Pedigree Resource File would help beyond doubling the number of search results with one showing the wrong place and one showing the right place.