rethink search functions

[kwkroll32]

Problem: Detailed search inequalities in string-based (or mixed string/numeric) database columns doesn't make sense. You shouldn't be able to say, "show me all samples with a study >= 100"

Suggestions:

1. only show numeric options in the detailed search, but how do we identify "numeric"?

• dynamically interpret the column type based on its value. ambiguous for mixed types.
• force users to abide by a particular schema where each value is spelled-out as numeric or not. throw warnings at database input step if it doesn't match.

2. strip strings from the column values when running a detailed search

• then you could say, "show me all samples with sample ID > 200" and it would return TDIMI201 and TDIMI202, but not TDIMI199 etc.

3. force numeric-only in the detailed search and run the plain search bar simultaneously for string match

• then you could search "TDIMI" in the search bar AND make a detailed search for any numeric term
• limits users to a single string match at any given time.

[GeekLogan]

The current search API/Schema would need to be rewritten for #2 or #3 because it would require relational operators (i.e. LIKE) which are not currently able to be encoded in the request format.