Story #2004: Finalize Mercury for release
Disable leading wildcard search in mercury ui
NOTE-Updating this story to instead reflect effort to disable leading wildcard searching in mercury.
Update help text indicating leading * usage.
Update query string processing to remove leading wildcards.
Mercury definitely supports leading wildcard searches in other implementations - ornl daac for instance
#3 Updated by Skye Roseboom almost 10 years ago
looks to be two options:
N-gram configuration to index variations of text strings.
N-gram looks to trade longer indexing time and larger storage requirements for query speed.
Reverse wildcard used trailing wildcard searching on the normally stored text strings just reversed. Indexing time and storage not effected - seems to indicate slight query overhead to search strings in reverse but uses default trailing wildcard searching.
#7 Updated by Skye Roseboom almost 10 years ago
- Status changed from In Progress to Closed
Restricting text input fields from containing wildcard character using M3.handleWildcard js event listener method on html class 'noWildcard'.
Stripping wildcard character out of search terms in default.js using M3.stripWildcard.js