Improve "Find" Search Capabilities
It seems like FamilySearch's "Find" feature is not always very dependable and at times struggles to find names that are similar but spelt a little different.
For example, I will sometimes use the "Find" feature to double check that there are not duplicates of individuals (I have often found that FamilySearch does not always catch duplicates, but if I do a quick search on Find, I can sometimes find duplicates myself). Recently, I checked for duplicates for Edward J Mushtare (G7V9-2HV). In "Find", I put in his name and birthplace (New York, between 1906-1908). Several search results came up, but none of them were duplicates. Later, when attaching a source to Edward J Mushtare, I found that the source was already attached to an Edward Mashtar (G441-3M5). Edward Mushtare and Edward Mashtar share the same parents, same birth location, and almost the same birthdate. They are almost certainly duplicates, but I was disappointed that FamilySearch's "Find" tool could not pull up Edward Mashtar from a search of Edward Mushtare.
I think it would be helpful (and likely reduce the amount of duplicate temple work) if the searching capabilities of FamilySearch were improved. I realize that that is not a trivial recommendation, but I have run into this problem several times before.
Comments
-
I agree that Find does not work as well as I would like. I often resort to searching for a record that might be attached to the profile I'm trying to find
0 -
Yesterday I was down a rabbit hole involving the (Hungarian) surname Toldalagi, also spelled Tholdalagi, Toldalaghy, and other variations along the same theme. It's nobility, so I expected to find multiple copies -- but instead, Find gave me an entire page of the surname Oldal. The multiple copies of Toldalagi-and-variants were also present in the Tree; Possible Duplicates eventually found several of them, and Search - Records turned up a few more, but they continued to be nowhere to be seen on Find's first page.
My conclusion is that both the matching algorithm and the sorting/weighting scheme are faulty. Some of the profiles that Find failed on had the surname misspelled as Tordalagi, which is one letter away from my search term, but it was not returned as a match. (Or not where I could see it, anyway.) Meanwhile, a name matching only half of my search term got the entire first page. That's basically a search-engine variation on the Scunthorpe problem, and I Did Not Appreciate It. (I'm curious whether the Community's nanny-bot will choke on that or not.)
1
