Endeca | Configure stop words

What is meaning of stop word in Endeca ?

Stop words are words that are ignored if an application user includes them as part of a search.Typically, common words like the, and, a and so on are included in the stop word list.

How to add stop words in CAS based application ?

Step 1 : Open application specific stop word configuration file.

This file is located at <Application Directory>/config/mdex/<Application_Name>.stop_words.xml

For example : For store application installed at /opt/app/endeca/apps/ location file will be /opt/app/endeca/apps/Store/config/mdex/Store.stop_words.xml  

Step 2 : Add stop words.

By Default there is no stop word configured.

============================================================

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<!DOCTYPE STOP_WORDS SYSTEM "stop_words.dtd">
<STOP_WORDS>
  <STOP_WORD>of</STOP_WORD>
  <STOP_WORD>the</STOP_WORD>
  <STOP_WORD>how</STOP_WORD>
  <STOP_WORD>when</STOP_WORD>

</STOP_WORDS> 

============================================================

Step 3 : Run baseline. 

Important Points :

1. Words added to the stop word list are not expanded by other Endeca features like stemming and thesaurus. That means that if you set the word item as a stop word, its plural form items will not be marked automatically as a stop word. If you want both forms to be on the stop word list, you must add them individually. 

2. Stop words must be single words only, and cannot contain any non-searchable characters. If more than one word is entered as a stop word, neither the individual words nor the combined phrase will act as a stop word. Non-searchable characters within a stop word will also cause this behavior. Entering “full-book” as a stop word acts just as if you had entered “full book”, and does not have any effect on searches.

Endeca | Workbench configure keyword redirects

You can add keyword redirects to your application in the Keyword Redirects page in Workbench.
 

Steps to create a keyword redirect :

1. Log in to Workbench.
2. Select Keyword Redirects.
3. Click Add Redirect.The Add Keyword Redirect panel appears.

Keyword Redirect Pop Up

4. Enter an absolute or relative link in the Redirect Link field.
5. Enter a search term or terms in the User Search Terms field.
6. Select a match mode from the drop-down : 

Match Phrase - Default. A search query triggers a redirect if the search terms match in the specified
trigger terms in the same order. The search query may include additional terms before or after the
trigger terms.
Match All - A search query triggers a redirect if the search terms include all of the specified trigger
terms, but not necessarily in the same order.
Match Exact - A search query triggers a redirect only if the search terms exactly match the specified
trigger terms, in the same order, with no additional terms.
7. (Optional) Click the Add Another button and repeat Steps 5-6 to create additional search term triggers for the specified URI.

Keyword Redirect Pop Up

8. Click Save.

Each search term trigger appears in its own row in the Keyword Redirects table.

Keyword Page

You can configure multiple keywords that trigger a redirect to the same location.

Check Endeca Workbench publishing activities status

Whenever you publish changes to an application using Workbench tools such as Experience Manager, Keyword Redirects. You can check the status of these changes using Publishing Status console.

An update can have a status of Running, Success, or Failure.

Steps to open the Publishing Status console :

1. On any page in Workbench, click the status bar at the bottom of the page.The Publishing Status console appears.
2. In the Choose Application field, click a specific application or All Applications.This selection shows the status when an administrator runs the promote_content script to promote content from the authoring to the live environment.

4. Click a status line in the console to show details about the publishing action that triggered the status.
5. To toggle between ascending and descending order for the contents of that column, click a column
heading.

Publishing Status Console

MDEX Search query processing order

The MDEX Engine uses the following high-level steps to process record search queries :
 

1. Record filtering
2. Oracle Commerce Query Language (EQL) filtering
3. Tokenization
4. Auto correction (spelling correction and automatic phrasing)
5. Thesaurus expansion
6. Stemming
7. Primitive term and phrase lookup
8. Did you mean
9. Range filtering
10. Navigation filtering
11. Business rules and keyword redirects
12. Analytics
13. Relevance ranking

Note : For Boolean search queries, tokenization, auto correction, and thesaurus expansion are replaced
with a separate parsing phase.