Home› Welcome to the FamilySearch Community!› FamilySearch Help› Search

Improve/Correct 'exact' search engine matching

LDS Search Test
LDS Search Test ✭✭✭
October 19, 2021 edited December 31, 2021 in Search

Searching for persons born in Louisiana, using the location "United States" "Louisiana", I am presented with results from persons in Califiornia born in "L.A."

This is probably because Louisiana has an alternate name 'LA' to match its abbreviation,

However, the results are not valid, and this exemplifies a problem with the search engine which is apparently stripping non-alphabetical characters from source data before comparison.

Hence "Louisiana" has an alternate name "LA" and thus = "L.A." even in an exact search.

This is not correct.

If the user chooses an exact match, then the query matching process should be comparing the raw untouched source data with the criterion.

If I want to taste wines, I want to taste what is in the bottle, not some filtered and processed version that has had all the distinguishing characteristics removed,

Tagged:
  • New
1

Answers

  • dontiknowyou
    dontiknowyou ✭✭✭✭✭
    October 22, 2021

    Searching for persons born in Louisiana, using the location "United States" "Louisiana", I am presented with results from persons in Califiornia born in "L.A."

    This is Historical Records Search, not Find, correct?

    How are you searching on United States, then Louisiana? Or are you using Filters?

    0
  • LDS Search Test
    LDS Search Test ✭✭✭
    October 22, 2021

    @dontiknowyou Nothing special. "New Search" More Options, Location: Set Country and State. Then under Birth Event enter Louisiana as well. Results will show records from places other than Louisiana.

    0
  • dontiknowyou
    dontiknowyou ✭✭✭✭✭
    October 22, 2021

    Right. That's an historical records search.

    First observation: As far as I have seen, the exact matching feature does not apply to filters, only to initial search terms.

    Second observation: FamilySearch often severely annoys me in that exact matching usually (but not always?!) matches on records with ambiguous or missing data, rather than excluding those records. Exact isn't very exact.

    As I have mentioned before in other topics, these issues are why I have increasingly stopped using historical record searches except for very preliminary scouting. I now work primarily from within FamilyTree.

    Kind of an aside: Check the collection those "L.A." records are in; should they have been unambiguously indexed as Los Angeles, or is there legitimate room for uncertainty about what "L.A." refers to?

    0
  • Paul W
    Paul W ✭✭✭✭✭
    October 23, 2021 edited October 23, 2021

    @LDS Search Test

    I just tried "test"search and found all the results I received do appear to relate to individuals born in Louisiana, even where the birthplace has been abbreviated to "La".

    See https://www.familysearch.org/search/record/results?exactSearching=true&q.birthLikeDate.from=1890&q.birthLikeDate.to=1895&q.birthLikePlace=louisiana&q.birthLikePlace.exact=on&q.givenName=william&q.givenName.exact=on&q.surname=turner&q.surname.exact=on.

    Of course, I'm not denying other "test" searches (or "real" ones!) will include L.A., California results - just that this was not my experience here, using the criteria I applied.

    0
  • LDS Search Test
    LDS Search Test ✭✭✭
    October 23, 2021

    @Paul W Perhaps the changes in the wind have already blown through ...

    0
Clear
No Groups Found

Categories

  • 28.7K All Categories
  • 23K FamilySearch Help
  • 115 Get Involved
  • 2.6K General Questions
  • 428 FamilySearch Center
  • 436 FamilySearch Account
  • 4.2K Family Tree
  • 3.2K Search
  • 4.5K Indexing
  • 596 Memories
  • 6.2K Temple
  • 311 Other Languages
  • 34 Community News
  • 6.4K Suggest an Idea
  • Groups