Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
admin:indexing:powersearch:optimization [2011/01/24 15:53]
els
admin:indexing:powersearch:optimization [2016/06/28 22:38] (current)
Line 11: Line 11:
 [[admin:​indexing:​powersearch:​sql|SQL]] | [[admin:​indexing:​powersearch:​sql|SQL]] |
 **[[admin:​indexing:​powersearch:​optimization|Optimization]]** | **[[admin:​indexing:​powersearch:​optimization|Optimization]]** |
 +[[admin:​indexing:​powersearch:​custom|Customization]] |
 [[admin:​indexing:​powersearch:​tips|Tips]] [[admin:​indexing:​powersearch:​tips|Tips]]
  
Line 17: Line 18:
 ==== The Optimization Behind PowerSearch ==== ==== The Optimization Behind PowerSearch ====
  
-Generally there is no additional optimization needed for PowerSearch. PowerSearch generally consists of increasing the number of search terms used in a query. ​ For example, a query that would search for a given name of '​William' ​who be expanded to include "​William,​ Bill, Billy, Will, Williams, Willie, Willis, Wilson"​. ​ Presuming that Omnidex indexing has already been established to optimize the original search, it will also optimize the expanded search.+Generally there is no additional optimization needed for PowerSearch. PowerSearch generally consists of increasing the number of search terms used in a query. ​ For example, a query that would search for a given name of '​William' ​can be expanded to include "​William,​ Bill, Billy, Will, Williams, Willie, Willis, Wilson"​. ​ Presuming that Omnidex indexing has already been established to optimize the original search, it will also optimize the expanded search.
  
 === Enabling MISSPELLINGS === === Enabling MISSPELLINGS ===
  
-Applications that wish to use the MISSPELLINGS feature (which also encompasses transposition and typographical errors) will need to perform an [[dev:​sql:​statements:​update_text:​home|UPDATE TEXT]] ​command ​on their database after indexing. ​ This command will evaluate the data in the database and create custom dictionaries used to identify the misspelled entries in the database.+Applications that wish to use the MISSPELLINGS feature (which also encompasses transposition and typographical errors) will need to perform an [[dev:​sql:​statements:​update_text:​home|UPDATE TEXT]] ​statement ​on their database after indexing. ​ This command will evaluate the data in the database and create custom dictionaries used to identify the misspelled entries in the database.
  
 === Enabling PHONETIC === === Enabling PHONETIC ===
Line 36: Line 37:
  
 **[[admin:​indexing:​powersearch:​sql|Prev]]** | **[[admin:​indexing:​powersearch:​sql|Prev]]** |
-**[[admin:​indexing:​powersearch:​tips|Next]]**+**[[admin:​indexing:​powersearch:​custom|Next]]**
  
 ====== Additional Resources ====== ====== Additional Resources ======
 
Back to top
admin/indexing/powersearch/optimization.1295884401.txt.gz ยท Last modified: 2016/06/28 22:38 (external edit)