User Guide

Refining your searches with zones and fields 603
Note: As with other operators, IN might be uppercase or lowercase. Unlike AND, OR, or NOT, you
must enclose IN within brackets.
Thus, the following explicit search retrieves files in which Pete is the lead guitarist:
(Pete) <in> Lead_Guitar
This is expressed in CFML as follows:
<cfsearch name = "band_search"
collection="my_collection"
type = "explicit"
criteria="(Pete) <in> Lead_Guitar">
To retrieve files in which Pete plays either lead or rhythm guitar, use the following explicit search:
(Pete) <in> (Lead_Guitar,Rhythm_Guitar)
This is expressed in CFML as follows:
<cfsearch name = "band_search"
collection="bbb"
type = "explicit"
criteria="(Pete) <in> (Lead_Guitar,Rhythm_Guitar)">
Field searches
Fields are extracted from the document and stored in the collection for retrieval and searching,
and can be returned on a results list. Zones, on the other hand, are merely the definitions of
“regions” of a document for searching purposes, and are not physically extracted from the
document in the same way that fields are extracted.
You must define a region of text as a zone before it can be a field. Therefore, it can be only a zone,
or it can be both a field and a zone. Whether you define a region of text as a zone only or as both
a field and a zone depends on your particular requirements.
A field must be defined in the style file, style.ufl, before you create the collection. To map zones to
fields (to display field data), you must define and add these extra fields to style.ufl.
You can specify the values for the
cfindex attributes TITLE, KEY, and URL as document fields
for use with relational operators in the
criteria attribute. (The SCORE and SUMMARY
attributes are automatically returned by a
cfsearch; these attributes are different for each record
of a collection as the search criteria changes.) Text comparison operators can reference the
following document fields:
• cf_title
• cf_key
• cf_url
• cf_custom1
• cf_custom2
• cf_custom3
• cf_custom4