Determining Fields to Optimize Modifying the Fields Displayed on Search Results

Managing Search Tools 7-7

7.1.4.1 Determining Fields to Optimize

Consider the following when determining the fields to optimize: ■ Do you want an exact match in a query? ■ Do you want that match to work faster in a search? ■ Do you want to sort search results by field? By default the OracleTextSearch feature optimizes the Content ID and Document Title metadata fields. A maximum number of 32 fields can be defined as Optimized Fields with the OracleTextSearch feature. The Oracle Content Server instance can have up to 32 Optimized Fields, which includes data, integer, standard Oracle Content Server fields like dInDate, dOutDate, and fields selected to be optimized. All Optimized Fields are SDATA fields, which by default include dDocName, dDocTitle, dDocType, and dSecurityGroup. The display of integer fields is dynamic and depends on the Oracle Content Server system configuration.

7.1.4.2 AssigningEditing Optimized Fields

You can select metadata Non-Optimized Fields and assign them to be Optimized Fields for search purposes, or edit Optimized Fields and make them Non-Optimized. To assign or edit Optimized fields: 1. Log in to the Oracle Content Server instance as system administrator.

2. Click Administration in the navigation bar.

3. Click Admin Applets.

4. Click Configuration Manager, then the Information Fields tab, then Advanced

Search Design . For more information on the Configuration Manager applet, see Oracle Fusion Middleware Application Administrators Guide for Content Server.

5. To make a metadata field Optimized, click Edit Fields. In the Advanced Options

for metadata_field screen, select Is Optimized. 6. To edit an Optimized Field and make it Non-Optimized, click Edit Fields. In the Advanced Options for metadata_field screen, deselect Is Optimized. 7. When you have completed moving fields, use Index Fast Rebuild in Repository Manager to update the search collection to use the new and modified fields. Note: The Fast Rebuild does not function if a search collection rebuild is in progress. 7-8 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server

7.1.4.3 Performing a Fast Rebuild

The Fast Rebuild feature allows the search engine to add new information to the search collection without requiring a full collection rebuild. A Fast Rebuild is required in the following cases: ■ Adding or removing information fields ■ Changing any Optimized Field ■ Changing an information field to be an Optimized Field To perform a Fast Rebuild: 1. Log in to the Oracle Content Server instance as system administrator.

2. Click Administration in the navigation bar.

3. Click Admin Applets, then Repository Manager, then the Indexer tab.

The Repository Manager: Indexer Tab is displayed. 4. On the Collection Rebuild Cycle Screen , click Start. The Indexer Rebuild Screen is displayed with a warning that rebuilding the search index is a time-consuming process. If you do not want to start a rebuild now, click Cancel ; otherwise, continue with this procedure. 5. On the Indexer Rebuild Screen , click OK. A Fast Rebuild of the search collection is performed.

7.1.4.4 Modifying the Fields Displayed on Search Results

The OracleTextSearch feature provides default menu options on the Search Results page set by the Oracle Database configuration script: DrillDownFields=dDocType, dSecurityGroup Administrators can add one more option from the list of Optimized Fields to further customize the search results. Edit the configuration to add the option to the list of DrillDownFields. Note: A Fast Rebuild is not performed if a rebuild of the search collection is in progress. Note: The Fast Rebuild process does not create indexer counter values for Full Text, Meta Only, and Delete. To obtain indexer count statistics, you must perform a full collection rebuild. Note: This function does not support multi-value option lists. Note: A Fast Rebuild must be performed after making any change in the DrillDownfields setting. Managing Search Tools 7-9

7.1.5 Searching with OracleTextSearch

Performing a search with OracleTextSearch is generally the same except there are no visible changes in the Search: Expanded Form other than removal of Substring as a search operator option. The default search operator is CONTAINS. Substring-based queries still work. For details on performing searches, see Oracle Fusion Middleware Users Guide for Oracle Content Server. The following table describes the default search operators.

7.1.6 Metadata Wildcards

The following wildcards can be used in metadata search fields, even when using the Quick Search field. ■ An asterisk indicates zero or many alphanumeric characters. For example: – form matches form and formula – orm matches form and reform – form matches form, formula, reform, and performance Operator Description Example CONTAINS Finds content items with the specified whole word or phrase in the metadata field. This is available only for OracleTextSearch, or for Oracle Database and Microsoft SQL Server database with the optional DBSearchContainsOpSupport component enabled. When form is entered in the Title field, the search returns items with the word form in their title, but does not return items with the word performance or reform. MATCHES Finds items with the exact specified value in the metadata field. When address change form is entered in the Title field, the search returns items with the exact title of address change form. A query that uses the MATCHES operator on a nonoptimized field behaves the same as a query that uses the CONTAINS operator. For example, if the xDepartment field is not optimized, then the query xDepartment MATCHES Marketing behaves like xDepartment CONTAINS Marketing, returning hits on documents that have an xDepartment value of Marketing Services or Product Marketing. HAS WORD PREFIX Finds all content items with the specified word at the beginning of the metadata field. No wildcard character is placed before or after the specified value. When form is entered in the Title field, the search returns all items with the word form at the beginning of their title, but does not return an item whose title begins with the word performance or reform.