basic name fields are implicitly what advanced search calls 'includes', i.e., mean 'have as a substring'. advanced search adds generally =, <=, and >= operators.
make 'includes' explicit and that option selected by default
this leaves the new interface as easy as before, with basic user simply ignoring the select pulldown
add =, <=, and >= operators to unified search interface (or change to or add <, >)
regularize and tighten interface by including 'sounds like' among these options and so not as a separate control; this also allows selective use of sounds-like with some but not all name fields specified in the search
include sql 'like' and 'rlike' (regular expression match)
include also a range option which
displays a second field only when user selects range from operator ui select
server logic will impose that either of begin- / end- fields in a pair can be left blank, meaning that this limit is open-ended and without that condition
so >= and <= logic is provided also in this 'between' range ui
consider then that these may be redundant as single-field operators
basic name fields are implicitly what advanced search calls 'includes', i.e., mean 'have as a substring'. advanced search adds generally =, <=, and >= operators.