Skip to main content

ATG Search - how to define the search configuration rules

ATG Search configuration rules are specified through the ATG BCC Merchandising UI. Over here you could specify the below set of rules
  1. Redirection rules --> If you want to redirect to another page other than the search result page for a search keyword
  2. Property Prioritization rules  --> Prioritize certain set of properties and give weightage
  3. Result exclusion rules  --> Exclude certain search results
  4. Result positioning rules  --> Position / Sort the search result data




1.  To create the search configuration tree, you need to log-in to the ATG BCC Merchandising UI and select the Search Configuration Tree in the Browse tab drop down. Now need to click the Create button and first you need to create the Search Configuration Folder.


2.  When you create the folder, give the name of the folder and select whether the contents vary by Language or Segment. If your ecommerce site need to support more than one language and you need to configure different locale specific rules, please select the contents vary by Language option.


3.  After you create the folder, you could click the create the Search Configuration button and specify the Name and the Locale. These locale values are populated in the drop down from the component /atg/search/config/LanguageDimensionService



4. Once you create the Search Configuration,  you can add different rules like Redirection, Result Exclusion,...


Below you could find the screen shot of a sample Result Exclusion rule for the searches with search keyword contains all of the words baby.


Below you could find the screen shot of a sample Result Positioning rule for the searches with search keyword contains all of the words tv.





Labels:

Comments

  1. Anonymous13 July 2012 at 00:16

    Sony kindly post some more example on Result Positioning rule to understand How it works.

    ReplyDelete
  2. Sony Thomas21 July 2012 at 09:58

    Sorry, I don't have the Search set up now. The result positioning is pretty straight forward and all the matching results will be positioned at the top. If you have any specific queries, please ask.

    ReplyDelete
  3. Vishal9 April 2013 at 15:20

    Hi Sony,

    Need some help. I have successfully configured search rules in /atg/bcc and deployed.
    But on commerce site if I search with that keyword it is not redirecting.
    Any specific reasons.
    Please refer this link to understand the problem better...
    https://kr.forums.oracle.com/forums/thread.jspa?threadID=2423279


    Thanks in Advance.

    ReplyDelete
  4. Sony Thomas5 July 2013 at 21:52

    ATG out of box SearchFormHandler and droplets have an autoRedirect property that specifies whether the form handler should check the search results for a redirect URL or not. Check this

    ReplyDelete
  5. Aayush26 July 2013 at 23:07

    How do I add another keyword that associates with the same one for example "Sharkbite" pull up search results but when entered in "shark bite" separately no results found. I would like to know how to add a word differentiation and make it live.

    ReplyDelete
  6. Sony Thomas29 July 2013 at 15:48

    If you want to get the results of some other word, you can use the dictionary and give some synonyms. Also give "mode=AND" in the request attributes.

    ReplyDelete

Post a Comment

Popular posts from this blog

ATG - more about Forms and Form Handlers

An ATG form is defined by the dsp:form tag, which typically encloses DSP tags that specify form elements, such as dsp:input that provide direct access to Nucleus component properties. Find below a sample dsp:form tag.    <dsp:form action="/testPages/showPersonProperties.jsp" method="post" target="_top">      <p>Name: <dsp:input bean="/samples/Person.name" type="text"/>      <p>Age: <dsp:input bean="/samples/Person.age" type="text" value="30"/>      <p><dsp:input type="submit" bean="/samples/Person.submit"/> value="Click to submit"/>    </dsp:form>   When the user submits the form, the /samples/Person.name property is set to the value entered in the input field.Unlike standard HTML, which requires the name attribute for most input tags; the name attribute is optional for DSP form element tags. If an input tag omits the n...
11 comments
Read more

Google Chrome shortcut keys

If you are a Google Chromey guy, please find below the list of shortcut keys for some of the most used features  :-) Find more shortcut keys @  http://www.google.com/support/chrome/bin/static.py?page=guide.cs&guide=25799&topic=28650
4 comments
Read more

Basic design decisions for a commerce search setup ( with an ATG Search view)

In this blog I would like to explain the basic set of configuration/design decisions needed to setup an ATG search project. Most of these design decisions are common for all Enterprise search applications. 1. Decide the searchable properties :   This means the properties that the business want the user to search in the ecommerce platform. In ATG search these are configured as the text properties in the product-catalog-output-config.xml ( the definitionFile of the \atg\commerce\search\ProductCatalogOutputConfig). Usually the displayName of product/sku, displayName of department/category/sub-category, skuId, brandName are the properties configured as searchable. 2. Decide the search refinement properties or the faceted properties :   After a user search for a keyword, search refinement is the next step done to filter his results. ATG supports the search refinement using the Faceted Search concept. Read more about facted search @...
6 comments
Read more

Search Facets - how to create a new search facets in ATG Search

A Facet is a search refinement element that corresponds to a property of a commerce item type. ATG supports the search result refinement using the Faceted Search concept. Read more about facted search @  http://en.wikipedia.org/wiki/Faceted_search . Facet can either be ranges or specific values. Each facet is stored in the RefinementRepository as a separate refineElement repository item. Facets are divided into Global and Local facets. Global facets apply to all the categories and local facets only to the category in which they are created. For example Price/Brand can be considered as the facets that are common for all skus and New Release/Coming Soon can be considered as the facets that are specific to Physical Media products like Vidoe/DVD/Blue-ray/Books. We can use the ATG BCC - Merchandising UI to create facets. The Faceting Property depends on the meta-properties defined in the \atg\commerce\search\product-catalog-output-config.xml ( the def...
4 comments
Read more

ATG search installation and search engine log files

Here I would like to explain how your ATG search folder structure looks like after you do the ATG search installation and also about the search engine log files. To get the ATG search, you need to install the ATGSearch<version>Windows.exe after you do the ATG installation. When you install ATG search, the generated folders include an OS dependant folder. In the below screen shot, you could see the "i686-win32-vc71" folder and this is generated since the ATG search ins installed in a windows machine. The ATG search engine is actually an exe file inside this "i686-win32-vc71" folder. Below screen shot give you an idea about the "atgsearch.exe", which is the search engine application. This search engine application (atgsearch.exe) is started by a remote launcher call from the BCC search administration UI.  The log files like "atgsearch_20120106112413_568.log" are the search engine log files where you could see the engine ...
2 comments
Read more