MAIN B-20447 Customer Search Sorting Fixes

[brooklyn-welsh]

Agility ticket

INT PRs

#13381
#13403

Summary

This branch fixes two problems that existed on the "Customer Search" tab (as well as other places where customer search was allowed):

1. Names weren't sorted by closest match, i.e. a search for "Ted" would have a user with the last name, first name of "Submitted, HHG" appear at the top, several spots above a user with the name "Marine, Ted". Exact matches now appear at the top of the search results.
2. Sorting on the customer name field was a combination of last name and first name, which led to changing the sort from ascending to descending not actually doing much. For example if you were to have this list in an descending sort:

• Submitted, HHG
• Submitted, PPM
• Unsubmitted, PPM

Instead of "Unsubmitted" going to the top like you might expect when you change to ascending sort, it would instead reverse the sort inside of the last name groups like this:

• Submitted, PPM
• Submitted, HHG
• Unsubmitted, PPM

Now, first name has been removed from the sort consideration, and the expected sort result occurs.

Also, matches were originally calculating match between first and last name separately, which led to some incorrect results. Now, it takes the similarity of the search string with both fields and gets the sum, ensuring that the closest match is always at the top.

Finally, sorting by Branch, phone, etc, would override the exact name matches in the name column, i.e.; results with Air Force branch would always come first regardless of match similarity with the given name search string. PO clarified that exact matches should still take precedent even when sorting via another column.

So, the search SQL query has been edited to always take match similarity into account first, i.e. if a result from the "Navy" branch is a closer match than a result from "Air Force", the "Navy" one should show up at the top anyway. The sort will instead affect the groups where match similarity is the same.

How to test

Instructions available in both INT PRs for the relevant changes in each.

[KonstanceH]

LGTM

[taeJungCaci]

LGTM