Handling of special characters and multi word queries in global/simple search

[ReneRanzinger]

Problem

• Search in global search for "Dmel\Indy" ==> 0 results
• Search in global search for Dmel\Indy ==> tons of results
• Search in protein simple search for "Dmel\Indy" ==> tons of results
• Search in protein simple search for Dmel\Indy ==> 0 results

There are two problems here:

• Inconsistency between simple and global search
• Handling of special characters like "\"

Inconsistency between simple and global search The logic below needs to be implemented in global and local search the same

Handling of special characters In simple search Dmel\Indy is seen as one string an no results are found. Similar to "Dmel\Indy" in global search. And that is the expected behavior. Global search treats Dmel\Indy as two words Dmel and Indy and finds false positives. Not sure what simple search does with "Dmel\Indy" but results here are also false positive.

This is the logic how simple AND global search input should be treated:

• If the user quoted the input (starts with " and ends with ") treat it as one string and try to find a match for this string, ELSE
• Treat any white space as separators between multiple search words
• Quote the individual search words (that will make sure things like |.<>? etc are treated as part of the string)
• Or combine the search words

This would mean a search for Dmel\Indy means to search for "Dmel\Indy". A search for Dmel\Indy Gal means to search for "Dmel\Indy" OR "Gal".

[rykahsay]

I have tried to implement this on tst