none
IMS Flow, Search Query and Context Object, how do we pass qtf_teaser=hithighlight at query time.? RRS feed

  • Question

  • we can set dynamic-type="teasermarkup" on body in index profile which will return the marksup every time, but we do not need this. we want to request the teasermarkups case by case basis in an IMS Flow, Fast ESP documentation allows this by adding qtf_teaser:hithighlight, in case of IMS Flow which parameter do we add to the contextobject to enable this functionality? 

    we tried, <linkhits>true</linkhits><qtf_teaser>hithighlight</qtf_teaser>, but with no success.

    Is this functionality supported in an IMS Flow/Query?

    Friday, January 13, 2012 4:42 AM

All replies

  • I am not sure if this will work for you, but we had a somewhat similar requirement of disabling and enabling lemmatization on a per query basis via IMS. In ESP QR engine this is done by passing a parameter qtf_lemmatize = 0/1.

    IMS context object has a node called '_additionalParameters' (Property 'ImsSearch.AdditionalParameters' if you are using .NET IMS classes directly). What we ended up doing is including a new additional parameter with name = "qtf_lemmatize" and value = "1" and this actually worked.

    You could try a similar thing, creating an additional parameter with name="qtf_teaser" and value="hithighlight".

    Good luck!

    Friday, January 13, 2012 3:13 PM
  • Thanks a lot, we had syntax issues with the qtf_teaser, when we passed data to additional params before, we get results now.

    new

     

    Ims.Search.AdditionalParameter("qtf_teaser:view", "hithighlight", "ESPLookup");

    Or in XML

     

    <_additionalParameters> <item> <name>qtf_teaser:view</name>   <value>hithighlight</value> <target>ESPLookup</target> </item> </_additionalParameters>

    We need to figure out the AJAX template errors handling the href's now.


    • Edited by mdate Friday, January 13, 2012 5:23 PM
    Friday, January 13, 2012 5:22 PM