Friday, May 29, 2020

how to enable ancestor matches during record search for Hierarchical Dimension?

Search interface is generally used to do record search and searchable attributes needs to be added. In a ATG/Endeca integration, By Defaul... thumbnail 1 summary
Search interface is generally used to do record search and searchable attributes needs to be added.

In a ATG/Endeca integration, By Default product.category dimension is searchable but match against all ancestors of a hierarchical dimension is disabled.

For example, if "Women > shoes" and "Men > Clothing >Jeans" are product.category values for a product 'Product-123', searching with term "shoes" and "jeans" returns the product 'Product-123'  but searching with the term "women" , "Clothing" and "Mens" does not return the product 'Product-123'.  The business needs the Product-123 record to be returned for all the record search terms :  Women , Clothing, Men, Jeans and Shoes ancestor values in the hierarchical dimension.

This can be enabled in two ways for 11.x CAS based indexing:-

1. Update CRS.recsearch_indexes.xml xml under Endeca_app/config/mdex and update as below :-

  <RECSEARCH_INDEX NAME="product.category" RECSEARCH_HIERARCHY="TRUE">
    <SEARCH_INDEX/>
  </RECSEARCH_INDEX>

2. AllAncestor.diaplyName propety contains complete hierarchy of attributes but this property is not searchable OOTB. Make it searchable using product-sku-output-config.xml.

Note : For Forge based Indexing, above file available under /config/pipeline folder


Above functioanly can be tested using DGraph.WhyMatch flag in endeca jsp ref.

No comments

Post a Comment

Note: Only a member of this blog may post a comment.

Text Widget