Differences

This shows you the differences between two versions of the page.

--- admin:indexing:text:home [2011/01/25 04:18]
els
+++ admin:indexing:text:home [2016/06/28 22:38] (current)
@@ Line 7: / Line 7: @@
 **[[admin:indexing:text:home|Overview]]** |
-[[admin:indexing:text:clob|Text Fields]] |
+[[admin:indexing:text:clob|Textual Datatypes]] |
 [[admin:indexing:text:retrieve|External Files]] |
 [[admin:indexing:text:proximity|Proximity Searches]] |
+[[admin:indexing:text:advanced|Advanced Searches]] |
 [[admin:indexing:text:results|Displaying Results]] |
 [[admin:indexing:text:relevancy|Relevancy]]
@@ Line 17: / Line 18: @@
 ==== Overview ====
-Omnidex allows applications to search for both textual and non-textual data using SQL statements.  For most textual data, a [[admin:indexing:indexes:types|QuickText]] index parses the individual keywords in the column and allows them to be individually qualified.  This feature is well suited for small textual fields, such as names, addresses, descriptions, comments and so forth.  When working with larger blocks of text, more powerful indexing is needed.
+Omnidex allows applications to search for both textual and non-textual data using SQL statements.  For most textual data, [[admin:indexing:indexes:types|QuickText]] indexes parse the individual keywords in the column and allows them to be individually qualified.  This feature is well suited for small textual fields, such as names, addresses, descriptions, comments and so forth.  QuickText indexes are simple and efficient, but when working with larger blocks of text, more powerful indexing is needed.
-Omnidex Text provides the ability to query large amounts of textual data in a database.  Omnidex Text also allows a table to reference external text files, and allows them to be indexed as part of the database.  This feature is well suited for large textual fields, such as articles, knowledgebases, forums, lengthy product descriptions and so forth.
+Omnidex Text provides more sophisticated indexes designed for large amounts of textual data stored in a database, such as articles, knowledgebase entries, forums, lengthy product descriptions and so forth.  Omnidex Text focuses on searching text in a database.  Omnidex Text is not a document management system and does not parse Microsoft Office, PDF, HTML or XML files.  Omnidex Text can index large textual files outside of the database, using a table as a catalog.
-Omnidex Text searches textual data in a database, but it is not designed to search external documents.  At present, Omnidex Text only indexes textual data and does not index Microsoft Word, PDF, HTML or XML files.
+Omnidex Text works seamlessly with the rest of Omnidex and allows large textual fields to be searched alongside regular columns in standard SQL statements, using standard ODBC and JDBC interfaces.  Queries can issue traditional queries with criteria, table joins, aggregations and ordering, while at the same time querying large blocks of text.
-Omnidex Text allows large textual fields to be searched alongside regular columns as well.  Omnidex SQL statements perform complex, multi-table searches, using advanced textual features for the textual areas, and using standard SQL for the non-textual areas.
+Omnidex Text provides additional features that allow excerpts to be extracted from the text, and allows sorting by relevancy, similar to an Internet search engine.  Omnidex Text also allows [[admin:indexing:powersearch:home|PowerSearch]] to be used against large textual data, providing features like misspellings, word forms and synonyms.
-Omnidex Text provides the ability to search large collections of textual data.
 =====  =====
-**[[admin:indexing:text:clob|Next]]** |
+**[[admin:indexing:text:clob|Next]]**
 ====== Additional Resources ======

Back to top

admin/indexing/text/home.1295929090.txt.gz · Last modified: 2016/06/28 22:38 (external edit)

Sitemap Recent Changes