Ignore Suffixes on Searches
The system now ignores prefixes when specifying a search, which is great. So Mr. John Doe can be found by entering Doe, John. However, suffixes aren’t ignored. So Mr. John Doe Sr. has to be entered as Doe Sr., John. It would be great if suffixes could also be ignored on searches.
Joel Schwartz
shared this idea
Released 4/25/2024:
From Summit 2024 Idea Lab Live - Profiles: Enhanced the search of profiles to not require the suffix when searching for profiles. This will allow users more search capabilities on profiles.
-
Madison Leighty
commented
This function of the global search is confusing for nearly all users on our staff. I end up suggesting to most of my colleagues that they search only by the last name (with no comma or first name afterward) and scroll through the list to find the profile they are looking for -- but it would really be much better if the global search worked in a way that is more "intuitive" for the average user.
-
Carrie Miller
commented
Example: When searching common names like - Johnson, Don - It brings up one Don Johnson but the wrong one. The one I am looking for is a Jr. (If you do not know they are a Jr. you can overlook and create a duplicate.) It would be great if it would show both of the Don Johnson’s together, to be able to determine if you need the Jr. or the other Don Johnson.
-
Bryant Phillips
commented
When searching for an individual who has a suffix, that suffix needs to be typed in after the last name to be able to find that profile. Not all staff are aware that a suffix is found on the profile to know to include it in the search. It would be more helpful if we didn't have to type in the suffix and instead just the last name, comma, and first name.
For example, searching "Smith, Joe" would return "Smith Jr., Mr. Joe W.". Right now, it doesn't.