Comment 2 for bug 1152863

Hey Dan,

Speaking to your last point, our expectation is that the user who clicks on the Boolean search tab would be a person more knowledgeable of search strategy than the typical user who is entering searches on the Basic or Advanced search pages. If they know enough about search to use those Boolean operators, I would expect they know enough to enclose a phrase like "to be or not to be" in quotation marks. When the final coding is complete, those quoted searches will continue to search as a phrase without any conversion of "or" to ||

I would never suggest replacing Evergreen's handling of those search terms in our current search interfaces. The ability to use "and," "or", "not" as search terms is something we value and would not want to lose.