Oracle Help for the WebContentsSearchView Topic


Skip Headers
Previous
Previous
 
Next
Next

Basic Search

Use this page to perform a search with a single query box. You can reorder the way results are presented using the Group by and Sort by lists.

This topic describes all of the elements that you might find on the basic search page. However, your administrator may not have configured all of them for your use.

See Also: Search Results

Query Box

Enter a search string in the query box, then click Search. A search string consists of one or more words, which are case insensitive. See the Search Rules for information about expanding and restricting the search criteria using wildcard characters, special characters, and so forth.

Login Button

Displays the Search Login page. Depending on your system, you may need to log in to search any content or just to search secure content.

Customize Button

Displays the Subscribed Sources page, where you can subscribe to e-mail and secure Web sources. This link is visible only when you are logged in.

Source Groups Links

Source groups are groups of documents created by the search administrator that can be searched together. Clicking a source group restricts the search to that group. One of the links is All, so that you can revert to searching all sources.

Advanced Search Link

Displays the Advanced Search page. An Attribute Filters Link may appear instead of, or in addition to, this link, depending on the configuration of the Search application.

Attribute Filters Link

Displays a table that enables you to filter the query results by the values of various document attributes, such as the author, date, or file format. See Attribute Selection. When the attribute filters are hidden, a number in the link indicates how many attributes are filtering the search results.

An Advanced Search Link may appear instead of, or in addition to, this link, depending on the configuration of the Search application.

Browse Link

Clicking the Browse link opens a separate search window to search within source groups. Source groups are groups of sources, created by the search administrator, that can be searched together.

Click a source group name to see the subgroups under it. You can drill down further into the hierarchy by clicking a subgroup name. Select one or multiple groups within tree and click Search to limit your results to that group.

To view all the documents under a particular group, click the View All link or the number next to the source group name. This is the number of documents in the group. You can also perform a restricted search within the source group from this page.

Search Rules

The following table describes the search rules. Square brackets enclose characters entered in the query box.


Notes:

Oracle Text Query Syntax provides an alternative to the Oracle SES search rules.

The results do not include "Do you mean..." suggestions when you use thesaurus-based search, proximity search, fuzzy search, phrase search, compulsory exclusion search, and similar constructs.


Rule Description
Single term search Enter a term to find documents that contain that term. For example, [oracle] finds all documents that contain the word Oracle anywhere in that document.

The AND operator applies to any two searchable items in a query with a white space in between. For example, [oracle text] has two searchable items, and it returns documents containing oracle and text.

The operator [&] explicitly denotes an AND relationship. The query [oracle & text] also returns documents containing oracle and text.

Phrase search ["..."] Put quotes around a set of words to find documents that contain that exact phrase.

Oracle SES does not apply implicit stemming expansion to a query phrase, but it can apply explicit term expansion to terms in a phrase. All operators except term expansion operators in a phrase are not treated as valid operators but as normal special characters.

For example, [oracle "RAC performance"] returns documents containing oracle and the phrase "RAC performance". Documents containing the stemming form "RAC performances" are not returned. The query ["sec^re search"] returns documents with the phrase "sec re search".

Attribute search Attribute search is also supported on the Basic Search page, the Advanced Search page, or both, depending on the configuration of the Search application.

Search on attributes with an attribute name, a colon (:), and then the value to be searched. Implicit stemming is applied to the attribute value term. You can specify operators as options. When no operator is specified, Oracle SES uses Contains for STRING attributes and Equals for NUMBER and DATE attributes.

For example, [DocVersion:>1] returns documents that have number attribute DocVersion where attribute value is larger than 1. The query [title:"oracle text"] returns documents with the phrase "oracle text" in the title attribute. The query [oracle | title:S*S] returns documents with the term oracle or SES in the title attribute. The query [title:^oracle] has the same effect as [title:oracle]. The contains [^] operator applies only to the STRING attribute.

  • Equals [=] returns documents with an attribute equaling the query with case-insensitivity. For example, [title:="oracle text"] returns documents whose title equals "oracle text". It applies to all three attributes.

  • Less than and narrower terms [<] return documents with an attribute value less than or earlier than the query value. For example, [DocVersion:<2] returns documents that have number attribute Docversion and where the attribute value is less than 2. They apply to all three attributes.

  • Less than equals [<=] applies to NUMBER and DATE attributes.

  • Greater than and broader terms [>] return documents with an attribute value greater than or later than the query value. They apply to all three attributes.

  • Greater than equals [>=] applies to NUMBER and DATE attributes. For example, [price:>=10] returns documents whose price attribute value is larger than or equal to 10. The query [LastModifiedDate:>=12/23/2010] returns documents whose LastModifiedDate attribute value is on or after December 23, 2010.

Proximity search ["..."~] Specify the maximum distance within which multiple terms occur with proximity search. A proximity search must have the search terms in double quotes. When the maximum spanning distance is not specified, Oracle SES applies a default window of 100 terms. The maximum number is 100. When a value larger than 100 is specified, Oracle SES treats it as 100.

For example, ["ses performance"~10] returns documents with terms SES and performance within any 10 terms spanning windows. The query ["ses performance"~] returns documents containing the terms SES and performance within any 100 terms spanning windows.

Fuzzy [...~] search Put the operator (~) at the end of a single term to return documents that contain terms spelled similarly to the query term.

For example, [hallo~] returns documents containing term hello. The query [spacifi*tion~] returns documents containing the term specification.

If a single term enclosed in double quotes is followed by ~, then the query is not a proximity search but a fuzzy search. The query ["parformance"~] returns documents containing the term performance.

Thesaurus search:

Synonym [~...] search

Narrower term [<] search

Broader term [>] search

Thesaurus-based operators require that a thesaurus be loaded into Oracle SES.

Put the operator [~] at the beginning of a term to return documents that contain the original query term or a synonym for it. For example, [~"RAC"] returns documents with RAC or the thesaurus-defined synonym real application clusters. A synonym relationship is symmetric: real application clusters is a synonym of RAC, and RAC is a synonym of real application clusters. In attribute search, it applies only to the STRING attribute.

The query [<"Northern California"] returns documents with the thesaurus-defined narrower term San Francisco or the original phrase Northern California. The query [product:>chair] returns documents whose product attributes contain the broader term furniture or the original term chair. Broader and narrower terms are symmetric. Specifying that furniture is a broader term of chair also implicitly specifies that chair is a narrower term of furniture.

OR [ | ] search Use the OR [ | ] operator to connect any two searchable items.

For example, [oracle | "RAC performance"~ ] returns documents with the term oracle or with the terms RAC and performance in any 100 terms spanning windows. The query [oracle | title:SES] returns documents with the term oracle or SES in the title attribute.

Grouping ( ) search Use parentheses [( )] to group search components together to change precedence of the AND and OR operators. The grouped query components must form a valid query. If the query string inside the parentheses is not a valid query, then Oracle SES implicitly rewrites it to the closest valid query.

For example, [(oracle | database) sales] returns documents containing sales and containing either oracle or database. The query [(oracle |) sales] returns documents containing oracle and sales, because [oracle |] is not a valid query.

The order of precedence for operators is the following, from highest to lowest: [()], [+] and [-], [& including implicit AND], [ | ]. Other operators have no sense of precedence. The operators [+] and [-] have equal precedence. They are applied in the order of the query from left to right.

Wildcard matching [*] for multiple characters Put the operator [*] at the middle or end of a term for wildcard matching. It can be applied multiple times in one term. A wildcard operator at the beginning of a search term is ignored.

For example, [ora*] finds documents that contain all words beginning with ora, such as Oracle and Orator. The query [title:a*e] returns documents with the title containing words such as apple or ape.

Multiple character wildcard expansion could result in too many terms. For example, [a*] could find too many terms that start with a. Oracle SES throws an error to refine the queries.

The wildcard operator [*] is ineffective with the escape character [\] just before it. For example [Pro\*c].

Wildcard matching cannot be used with Chinese or Japanese native characters.

Wildcard matching [?] for single characters Put the operator (?) at the middle or end of a term for wildcard matching for a single character. It can be applied multiple times in one term. A wildcard operator at the beginning of a search term is ignored.

For example, [orac?e] and [or?CL?] both return documents containing terms that replace ? with a single character, such as Oracle.

The wildcard operator [?] is ineffective with the escape character [\] just before it.

Wildcard matching cannot be used with Chinese or Japanese native characters.

Compulsory inclusion [+] search Put the operator [+] in front of any searchable item (term, phrase, attribute shortcut, or proximity search) to require that the word be found in all matching documents.

For example, [oracle +applications] only finds documents that contain the words Oracle and applications. There should be no space between the + operator and the search term.

When compulsory inclusion is used with the OR [ | ] operator, the compulsory inclusion operator has no effect. For example, the query [text | +database] returns documents containing the term text or database.

Compulsory exclusion [-] search Put the operator [-] at the beginning of any searchable item (including term, phrase, attribute shortcut, and proximity search) to require that the searchable item not be found in all matching documents. There should be no space between the [-] and the search term.

For example, [oracle –applications] returns documents containing oracle but not containing applications. The query [oracle –"application server"] returns documents containing oracle but not containing the phrase "application server". The query [oracle –title:oracle] returns documents containing oracle but with the title not containing oracle. The query [oracle –"application server"~] returns documents containing oracle but not containing application and server in any 100 terms spanning window.

The compulsory exclusion query cannot be the only query. For example, [-oracle] raises an error. Also, the compulsory exclusion query cannot be connected with the OR [ | ] operator. For example, [oracle | -database] raises an error.

File type filtering [filetype:filetype] Attaching [filetype:filetype] after the search term limits results to that particular file type. For example, [documentation filetype:pdf] returns PDF format documents for the term documentation. The "filetype" shortcut must be lowercase, but the file type name is case-insensitive; that is, [documentation filetype:PDF] returns the same documents.

A query can have only one file type. The following file type extensions are supported: doc, htm, html, xml, ps, pdf, txt, rtf, ppt, xls.

Site search [site:host] Attaching [site:host] limits results to that particular site. For example, [site:www.example.com filetype:pdf] returns documents from www.example.com in PDF format. The "site" shortcut must be lowercase, but the host name is case-insensitive; that is, [site:www.Example.com filetype:pdf] returns the same documents.

A query can have only one site for exact host matching. The query [site:*.example.com] does not work.

Group search [SG:source group] Group searches are also supported on the Basic Search page, the Advanced Search page, or both, depending on the configuration of the Search application.

Attaching [SG:source group] limits results to that particular source group. All other search restrictions are valid in a group search.

For example, [sg:intranet] returns documents in the intranet source group. The "SG" shortcut must be lowercase, but the source group name is case-insensitive; that is, [sg:IntraNet] returns the same documents.

In federated search, the source group names are the source groups in the local (broker) node. If the local source groups contain federated sources, then Oracle SES translates the local source group name to the federated source group name by changing the query, which is then sent to federated source for results.


Notes:

Oracle Text Query Syntax

When a query is prefixed with 'otext::', Oracle SES identifies it as an Oracle Text syntax query. Oracle Text query syntax and Oracle SES query syntax cannot be used in the same query.

To use the Oracle Text query syntax, note the following: 

Table: Syntax Comparison Between Oracle Text and Oracle SES compares the syntax of Oracle Text and Oracle SES.

Syntax Comparison Between Oracle Text and Oracle SES

Query Oracle Text Oracle SES

Term

otext::secure

secure

Phrase

otext::secure search

otext::{secure search}

"secure search"

Proximity search

otext::secure ; search

otext::near((secure, search),10)

"secure search"~

"secure search"~10

Attribute search

otext::oracle within "title"

otext::(oracle & text) within "title"

N/A for numeric and date attribute

title:oracle

title:oracle & title:text

lastmodifieddate:10/20/2006

AND operator

otext::secure & search

secure search

OR operator

otext::secure | search

secure | search

ACCUM and Weight

otext::secure*10, search *5

N/A

Compulsory exclusion

otext::oracle ~apps

oracle -apps

Compulsory inclusion

N/A

oracle +apps

Grouping operator

otext::(rac | {real application clusters}) & whitepaper

(rac | "real application clusters") whitepaper

Stemming operator

otext::$feature

N/A (implicit stemming, turned off by using double quotes)

Multiple character wildcard

Single character wildcard

Fuzzy expansion

otext::feat%e

otext::featu_e

otext::?hallo

feat*e

featu?e

hallo~

Soundex

otext::!smythe

N/A

Theme search

otext::about(dogs)

N/A

Synonym search

Narrower term search

Broader term search

otext::syn(dog)

otext::NT(dog)

otext::BT(dog)

~dog

<dog

>dog

Highlight

otext::oracle highlight:search

N/A (implicitly done)