none
Custom Property Extraction (Entity Extraction) RRS feed

  • Question

  • Hi All,
           We all know that by custom property extraction, we can create a custom crawl property and add the word into that property if suppose it is there in custom dictionary. 

    http://msdn.microsoft.com/en-us/library/ff795797(v=office.14).aspx

    Eg:

    I have a page with 6 columns namely Title, Body, url, caption, med, imag.

    If suppose the keyword "abcd" is there in the page in any of the above 6 column and same keyword is there in custom dictionary key, then corresponding dictionary value will get mapped to the custom crawl property field for that page.

    But can we restrict in such a way that only if the keyword "abcd" is there in any of the three columns alone (eg: Title, Body, caption), then only that keyword should get mapped to custom field.


    Sharath Kumar R

    Thursday, August 1, 2013 2:01 PM

All replies

  • Hi,

    Unfortunately not with the dictionary extractors (although I think you can change the internal config for the stage unsupported but don't have system to check on right now).

    The other way would be to use a custom extensibility stage in order to match against only some properties. Then you have complete control over the matching.

    Thanks,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/MCT/MCPD - If you find an answer useful, please up-vote it.
    http://techmikael.blogspot.com/
    Author of Working with FAST Search Server 2010 for SharePoint

    Friday, August 2, 2013 8:14 PM
  • Hi Svenson,

                Thanks for your reply. I understood the second point where we can do this through pipeline stage. But there are totally more than 50 k articles and all those articles has more than 10 columns. So it may increase crawl time and degarde performance. Please correct me if I am wrong.

             Regarding first point, 

    Unfortunately not with the dictionary extractors (although I think you can change the internal config for the stage unsupported but don't have system to check on right now).

     Can you please elaborate it. Thanks!


    Sharath Kumar R


    Monday, August 5, 2013 6:05 AM
  • Hi,

    50K articles is not that many imo, unless you have to process them multiple times. I wouldn't worry too much about the impact of an extra stage for first time indexing. It's usually worth it. but again, if you have to process all items multiple times, then it might be too much of an impact.

    I suggest you try it an measure it before you decide on the impact.

    Thanks,
    Mikael Svenson


    Search Enthusiast - SharePoint MVP/MCT/MCPD - If you find an answer useful, please up-vote it.
    http://techmikael.blogspot.com/
    Author of Working with FAST Search Server 2010 for SharePoint

    Monday, August 5, 2013 7:37 AM