Endeca ResultsList Boost and Bury or Endeca Record Spotlight cartridge editor grayed out - Endeca Boost and Bury

Problem Statement:
A common problem developers run into with the ResultsList editor's Boost and Bury controls or the Record Spotlight cartridge is the record selection editor being grayed out. 

Solution:
This happens when your Endeca application's dataservice.json file is not configured with the correct hostname - i.e. one that matches the URL used to access Workbench.

To properly configure and fix this, you need to do two things:
  1. Update the hostname and port in the /opt/app/endeca/APPN_NAME/config/editors_config/services/dataservice.json file with the correct authoring MDEX hostname
  2. Run the set_editors_config.sh script under /opt/app/endeca/APPN_NAME/control directory to push out the update to Experience Manager.

3 comments:

  1. Currently I am working on one scenario.I have to display the search results with the relevance according to some below criteria:

    1. If the results contains products which having some special offers or deals associated with them, those products will be available at the top in the results display section.
    2. If the results contains the type of items which user has purchased previously (It will be on the basis of the product brand and some other parameters tracked from the user's purchase history). Then those products will be shown at the top in the results display section.
    3. If the results contains products which having enough inventory available, then those products will be available at the top in the results display section.

    Which ever condition from above cases gets satisfied those products should be boosted.

    So where I have to concentrate? at ResultsListHandler level or through Boost and Burry tweaks it can be achievable.

    Thanks in advance,
    Shailesh Mane

    ReplyDelete
    Replies
    1. Hi Shailesh,

      There are various ways to achieve it:

      1) Use Endeca Relevancy Ranking Modules
      - Create Static Modules for Each of the above mentioned scenario and get it adjusted as per requirement

      2) Create Index based Sort on multiple keys
      - For Each scenario create endeca property and make it sort-enabled
      - Configure the --sort parameter in dgidx component for multiple properties so that results can be sorted using tie breaking logic
      Ex:
      --sort product.specialOffers|1||product.purcahseHistory|1||product.investoryStat|1

      These are the few things I can think at this moment. Hope it helps.

      Regards,
      Ravi Honakamble

      Delete
  2. Hi Ravi,

    I have a question about Endeca Boosting. When boosting products, we are currently entering and selecting their list of products individually. Do you think it would be possible to override OOTB Endeca and allow a string of products to be entered at once?

    i.e. instead of entering one product at a time into the “search for:” field, they could enter: 10011575, 10011765, 10011770,….etc and all 3 items would be pulled up and selected.

    For a little more context, we are boosting 60 products on each category page, so that’s 60 individual products they have to input, enter, and select. It’s taking nearly an hour to complete just this part of it. we have 8+ category pages, that’s nearly an entire day or two we are spending on boosting products alone – a task that should take an hour max to update all 8 category pages.

    Let me know if you think this is something we can customize. Thank you!

    Regards,
    Rajesh GR

    ReplyDelete