CBR queries using Enterprise Manager

Content Based Retrieval (CBR) allows you to easily find documents and annotations based on the indexed words they contain. For example, you can request a list of all documents that contain the words “structural stability.”

You can run CBR queries using any of four applications:

Enterprise Manager allows CBR queries to be run on only one object store at a time. The Content Engine API and Search Designer allow CBR queries to be run on multiple object stores at the same time.

Enterprise Manager’s Content Engine Query Builder allows you to create CBR queries. The results returned from CBR queries depend on which components of an object store have been indexed. You can index content elements of documents and annotations, which are stored by the Verity engine, You can also index the relational string-valued properties of documents, annotations, folders, and custom objects, which are stored in a separate database. For example, the author’s names may be indexed, even if the names don’t appear in the content of the documents themselves.

CBR queries use a combination of SQL and Verity Query Language syntax. Refer to the Developer’s Guide and the SQL Syntax Reference page for additional information on building queries.

Row limitations

You can set three types of row limits that can help you limit the time and resources consumed by a given query. However, if you set your row limit too low, you may stop the query before all matches are found. For example, if you are querying for documents that include the phrase “structural stability,” written by Lee Lindz, the object store may contain more documents that contain the phrase “structural stability” than your row limit allows. If the row limit stops the query before all “structural stability” documents have been found, the query may not yet have reached the Lindz document.

FULLTEXTROWLIMIT is a SQL statement option that you can include in your query.

FullTextRowDefault is a property of the object store and specifies the default number of rows that can be returned from the indexing data during a search. You can exceed the FullTextRowDefault by using a larger value in FULLTEXTROWLIMIT option in your query. If you do not specify a value for FULLTEXTROWLIMIT, the value stored in the FullTextRowDefault property is used for your query.

FullTextRowMax is a property of the object store and specifies the maximum number of rows that can be returned from the indexing data during a search. If you specify a value for the FULLTEXTROWLIMIT option in your SQL statement, the lesser of the FullTextRowMax and the FILLTEXTROWLIMIT values is used as the maximum number of rows that can be returned.

Refer to the Developer’s Guide and the SQL Syntax Reference page for additional information on row limits.

List of class definitions changed

This dialog box displays a list of all the Class Definitions that have changed in the current session of Enterprise Manager. To create an index job to re-index those classes enter an Index Job Description, select all the Class Definitions in the list that you wish to re-index, then click Create Index Job.The list is automatically cleared if you create an index job. If you just close the dialog without creating and index job, the list remains in memory until you exit Enterprise Manager. You can create the index job at a later time if you return to this dialog box before exiting Enterprise Manager.

The dialog box has the following controls:

Select Class Definitions that you wish to re-index
Displays a list of all the class definitions that are available for re-indexing.
Enter a job description
Use this field to enter a description for the index job you wish to create.
Create Index Job
Click to create a new index job which re-indexes the selected class definitions.
Clear Class Definitions Changed List
Click to remove all class definitions from the list control.