Home› Welcome to the FamilySearch Community!› FamilySearch Help› Family Tree

Family Tree "Search" engine has a couple of major bugs

Phillip Dunn - Sr Brit. Res. Specialist F.S. ret.
Phillip Dunn - Sr Brit. Res. Specialist F.S. ret. ✭
April 22, 2022 edited April 22, 2022 in Family Tree

I tried the following search parameters in Family Tree--in order to render search "results" on a search I ran today--to be as lean and clean as possible by using the "Exact" match box checked off. But instead, here's what I received--lots of 'fluff' and undesired hits:

To contrast this a bit, in the FamilySearch main (records) search engine, using the "Exact" match box almost always renders the search "results" as very relevent/clean by using the "Exact" match box checked off. But in the Family Tree when I checked-off the "Exact Match" box, I instead, still received--lots of 'fluff'--undesired hits, regardless, on 1) individuals' names AND 2) with place names. Here are the parameters and results on which I searched earlier today, in a Family Tree search on one of my ancestors:

https://www.familysearch.org/search/tree/results?count=100&q.birthLikeDate.from=1826&q.birthLikeDate.to=1858&q.birthLikePlace=Worcestershire%2C%20England&q.birthLikePlace.exact=on&q.fatherGivenName=Thomas&q.fatherGivenName.exact=on&q.fatherSurname=Git%2As&q.spouseGivenName=Mary&q.spouseGivenName.exact=on&q.surname=Git%2As

Please, is it possible to get the Family Tree "Exact match" box (when checked off) to function properly, like they do in the (main) FamilySearch main page "search" engine? If no, then why place them (Exact Match boxes) in the Family Tree "search" engine as a search filter/parameter option... All that I get in hits are mostly fluff or myriads of useless hits.

Thanks for any consideration given.

Phillip Dunn,

FamilySearch.org Sr British Research Specialist, ret./Volunteer

1

Answers

  • dontiknowyou
    dontiknowyou ✭✭✭✭✭
    April 22, 2022

    Yep, the Find exact search on Family Tree profiles is broken. When I made much the same report a few weeks ago I was told it is a known bug and engineers are working on it.

    0
Clear
No Groups Found

Categories

  • 29.9K All Categories
  • 24.1K FamilySearch Help
  • 122 Get Involved
  • 2.7K General Questions
  • 442 FamilySearch Center
  • 461 FamilySearch Account
  • 4.4K Family Tree
  • 3.4K Search
  • 4.7K Indexing
  • 634 Memories
  • 6.5K Temple
  • 321 Other Languages
  • 34 Community News
  • 6.6K Suggest an Idea
  • Groups