Search Bar usage & results are inconsistent across portlets.

• Type: Feature Request
• Status: Won't Do
• Priority: Minor
• Resolution: Discarded
• Affects Version/s: 6.2.0 CE M2
• Fix Version/s: None
• Component/s: Bookmarks, Documents & Media, Search Infrastructure, Search Infrastructure > Framework
• Labels:
  • search
  • ui
  • usability
• Environment: Tomcat 7.0.23 + hsql + Chrome 19

Different Portlets' Search features behave differently.

There are 40+ Search Bars in various portlets in Portal, plus any others in Plugins. I didn't take the time to test all of these. I would guess that most are using the pattern of the Bookmarks portlet.

I wouldn't be the one to say which way is correct. There are aspects of the examples below that are useful. I'm unsure if there are other search behaviors.

• Bookmarks: Appears to NOT support "like" searches by default, and instead requires the use of a wildcard ( * ). But the wildcard is only supported on the right, not the left. Also it appears that it's using a [word OR word] search.

• Document Library (Documents & Media) > Document Types: Appears TO support "like" searches by default, but not the usage of wildcards ( * ). Also it appears that it's using a [whole phrase] search.

Examples

Bookmarks:

• Test One
• Test Two
• New One
• New Two
• Newer Three

Bookmarks Portlet Search:

• new = 2 results
• ne = 0 results
• ne* = 3 results
• t* = 4 results
• t = 0 results
• *t = 0 results
• new three = 3 results
• new t* = 5 results
• n* three = 3 results

Document Types:

• Test One
• Test Two
• New One
• New Two
• Newer Three

Document Library (Documents & Media) Portlet > Document Types Search:

• new = 3 results
• ne = 4 results
• ne* = 0 results
• t* = 0 results
• t = 4 results
• *t = 0 results
• new three = 0 results
• new t* = 0 results
• n* three = 0 results