|
In
addition to full-text
searching dtSearch provides an option
for limiting an indexed or unindexed search
to a specific field,
for example the Boolean search query:
visual
basic and (name contains (Smith or Jones))
Alternative field searching
syntax
An
alternative syntax for field searches is
to add the field name and :: in front of
each word, like this:
(City::Portland
or City::Seattle) and (Address::Washington)
The
alternative syntax can be used where the
boolean syntax is not possible, such as
an "all words" or "any words"
search and file conditions.
Pre-Defined Fields
dtSearch
supports field searching in word processor,
spreadsheet, database, PDF and HTML documents.
 |
For
a list of defined fields in indexed
documents, click the Fields
button in the dtSearch Desktop or
Network Search dialog box. |
| |
Field
searching supports the complete range
of full-text
search options. |
On-The-Fly Fields
In
addition to fields that are predefined in
databases and documents, dtSearch also supports
a number of "on the fly" field
options:
| |
Find
an expression between a beginning
field marker and an end field marker
that you name. For example, you could
search for:
dear
to sincerely contains divorce settlement |
| |
dtSearch
automatically inserts field markers
at the beginning (xfirstword) and
end (xlastword) of all documents.
You can use the markers to limit a
search to the beginning or the end
of a document, for example: confidential
w/10 xfirstword |
| |
File
segmentation rules can break up long
text files into multiple sub-documents,
effectively treating each multiple
sub-document as a field. |
XML Fields
As
with any other document or database containing
fields, dtSearch can perform indexed and
unindexed searches using the full range
of dtSearch search features across an entire
XML database, or limited to specific fields.
For example, visual basic and (name contains
(Smith or Jones)) works just as well
on an XML database as an Access database,
a Word document, an HTML document, a PDF
document, etc.
Because
of the special nature of hierarchical XML
data, dtSearch also supports searches limited
to precise combinations of fields and subfields.
For example, in the Shakespeare
XML demo you could search for:
| |
persona
contains Henry |
| |
scene/stagedir
contains exeunt citizens |
 |
scene/speech/line
contains publius |
| |
/play/title
contains Henry the Fifth |
| |
scene//line
contains publius |
| |
|
The
first example would look for any field entitled
persona that contains Henry.
The second search containing the / as a
field separator would look for a field called
stagedir containing exeunt citizens,
with the stagedir field directly
nested in a field called scene.
The
third example would look for a triple-nested
hierarchical scene/speech/line field
sequence that contained publius.
The fourth example, starting with /, would
look for the play field at the top
of the hierarchy, with a title field
just beneath it containing Henry the
Fifth.
The
last example, with //, would look for a
field called line containing publius.
In contrast to the other examples, which
specify precise hierarchical sequences,
in this last example, the line field
could be anywhere from directly beneath
the scene field, to nested at multiple
levels of depth.
With
an XML database you can, as with any other
fielded document or database, combine full-text
searching and nested field searching, for
example:
(henry
the fifth) and (scene/speech/line contains
publius)
|
