Tuesday Feb 16, 2010

Setting Substring back as default search operator

For customers that grew up using UCM (aka Content Server) on Verity, one of the default configurations for search was the metadata operator being defaulted to 'Substring'. But in moving to database searching, that default operator switched to 'Matches'. This means the entire word/phrase must be entered to be found.

To go back to the old way of having Substring be default, you can add this configuration entry:

DefaultSearchOperator=hasAsSubstring

Keep in mind that the reason this was changed is because this is an expensive query to make compared to 'Matches'. So depending on the repository size, this may have an impact on the speed of the search results. One other thing to note is it does only apply the default to the free text metadata fields and not the option list fields. They will still be 'Matches' assuming the user will be picking from the list.

UPDATE (07/09/2012):  For setting the default operator for an option list, you can set the configuration flag of:

DefaultNBFieldSearchOperator=beginsWith

In this case setting it to 'Starts' as the default. 

 

About

Kyle Hatlestad is a Solution Architect in the WebCenter Architecture group (A-Team) who works with WebCenter Content and other products in the WebCenter & Fusion Middleware portfolios. The WebCenter A-Team blog can be found at: https://blogs.oracle.com/ ateam_webcenter/

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today