none
Modifying/Adding values of managed properties for web crawls RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, I'm looking for the easiest way to solve my problem.

    We have a content source, let's call it "Web Source" crawled by the web crawler. We have a managed property, let's call it "Content type". These are not related, and the "Web Source" documents does not have any values of "Content type".

    I want to tell FAST that all documents coming from "Web Source" should get the value "Article" as the "content type" managed property.

    How can I achieve this?

    Monday, January 17, 2011 11:27 AM
    |

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    You would need to create a custom pipeline extensibility stage to do this. In theory you should be able to use the setting

    <CrawledProperty propertySet="012357BD-1113-171D-1F25-292BB0B0B0B0" varType="31" propertyName="315" />

    which is mapped to the managed property "ContentSource". But for some reason this property will not be exported to the custom pipeline stage even though it contains a value. It might be for a reason or a bug, which I'll ask myself in this forum.

    So, what are you left to do? You have to use some of the other crawled properties. For example if it's a web crawl you can use

    <CrawledProperty propertySet="11280615-f653-448f-8ed8-2915008789f2" varType="31" propertyName="url"/>

    and do string checking on the url, and then set your content type property in the output parameter of the stage. I posted a tutorial on creating and debugging custom stages on my blog post which will get you started.

    Regards,
    Mikael Svenson

    Search Enthusiast - MCTS SharePoint/WCF4/ASP.Net4
    http://techmikael.blogspot.com/ - http://www.comperiosearch.com/
    Monday, January 17, 2011 4:34 PM
    |
  • Question
    Sign in to vote
    2
    Sign in to vote

    Using propertyId instead of propertyName works for the numeric crawled properties. If you include this in your extensibility configuration you can see which content source the data came from, and apply appropriate logic:

    <CrawledProperty propertySet="012357BD-1113-171D-1F25-292BB0B0B0B0" varType="31" propertyId="315" />

    Regards,
    Mikael Svenson

    Search Enthusiast - MCTS SharePoint/WCF4/ASP.Net4
    http://techmikael.blogspot.com/ - http://www.comperiosearch.com/
    Friday, January 21, 2011 9:49 AM
    |