-
Sub-task
-
Resolution: Done
-
Medium
-
None
-
None
-
None
-
SIMPLY S9 April 27 - May 11, SIMPLY S10 May 11 - May 25, SIMPLY S13 June 22 - July 6, SIMPLY S14 July 6 - July 20, SIMPLY S15 July 20 - Aug 3, SIMPLY S20 Sep 28 - Oct 12
Users performing a search are allowed to supply strings that the registry needs to parse according to the search algorithm described in the TAD. In order to convert a user-supplied string into a meaningful search, the application should convert it to single- or multi-word, normalized tokens of specific types.
For example, a search string including a five or nine digit number which is separated from other words probably indicates a US postal code. During the parsing and tokenization process, that portion of the string should be classified as a postal code, so that the higher-level search function can make decisions based on which types of token appear in the user's search string.