|
| Databases, Other Fielded Data, Data Classification Objects and Faceted Search |
|
| Related
article: Crossing the Full-Text Search
/ Fielded Data Divide from a Development Perspective |
|
| In
addition to full-text search options, dtSearch offers
extensive fielded data support. These include: |
 |
indexing and searching of all popular database
formats |
|
special
XML and SQL search features |
|
| indexing
and searching of BLOB data |
|
|
indexing
and searching of fields in all supported file
types |
|
extensive
developer support for adding on-the-fly classification
information and other fields to documents
during indexing |
|
| Additional
information: |
|
dtSearch automatically detects fields (including
document summary information fields) in a
wide range of supported
file types. |
|
In
addition to full-text searching, dtSearch
can also search by field name: (Author
contains John Smith) and (Subject contains
turbine generators). |
|
| Variable
term weighting can also apply to fields: (description:5 contains (apple and
pear)) or (author:2 contains smith) |
|
|
dtSearch
supports hierarchical field structures in
XML data, including both fields and attributes,
enabling highly refined nested field queries. |
|
The dtSearch Engine supports SQL-type databases through developer APIs (.NET, Java, C++ and COM). |
|
dtSearch Engine APIs also support faceted search. |
|
| API options for data classification: |
|
A wide range of API filters and objects support categorization via document full-text contents, document fielded data, database content, or data attributes attached during document indexing. |
|
For example, search filter objects work in conjunction with end-user query dialects to allow multiple users with different security classifications to search the same document collection, without having to maintain separate indexes corresponding to each classification level. |
|
| A single query can include an “exact phrase” full-text end-user search request; second-level Boolean search expressions (such as one or more field or metadata search criteria); and developer-added filtering expressions (such as a filtering expression to filter out documents that do not match a user’s security classification). |
|
|
For additional information on database indexing, adding fields to documents during indexing, sorting search results, generating a synopsis to display in search results, and faceted search, please see the Databases and Field Searching topic and the Displaying Search Results topics on the FAQ Selected Articles by Subject page. |
| See Also: Relevancy-Ranking |
|
| |
|
|
|
 |
| Instantly Search Terabytes of Text |
| dtSearch document filters support a broad range of data |
 |
| • |
Supports MS Office through current versions (Word, Excel, PowerPoint, Access), OpenOffice, ZIP, HTML, XML/XSL, PDF and more |
|
|
| • |
Supports Exchange, Outlook, Thunderbird and other popular email types, including nested and ZIP attachments |
|
|
| • |
Spider supports public and secure, static and dynamic (ASP.NET, SharePoint, CMS, PHP, etc.) web data |
|
|
| • |
APIs for SQL-type data, including BLOB data |
|
|
| • |
Highlights hits in all supported data types |
|
|
| 25+ full-text and fielded data search options |
|
|
| • |
Special forensics search options |
|
| • |
Advanced data classification objects |
|
|
| APIs for C++, Java and .NET through current versions |
|
| • |
64-bit and 32-bit Win / Linux APIs; .NET Spider API |
|
| • |
Document filters also available for separate licensing |
|
|
|
|
|
|
