none
FAST Search 2010 - Filtering out results RRS feed

  • Question

  • We have content with "DISABLED" suffixed to the doc title.   How can I stop these results from appearing in search results?

    Thought it would be simple!

    Any help greatly appreciated.

    Mike


    Mike Bennett
    Saturday, October 15, 2011 6:32 PM

All replies

  • Hi,

    There is no easy way of dropping these during indexing (unless you can omit entire document libraries).

    Your other option is to create a search scope using PowerShell so that you can use FQL in your scope. You would set the ExtendedSearchfilter property to something like this:

     

    not(title:ends-with("DISABLED"))
    

    Regards,
    Mikael Svenson 

     


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    Saturday, October 15, 2011 7:01 PM
  • Thanks Mikeal - I can see how this would help but...

    My client is huge and is one of the larget SP users in Canada - now deploying FAST across the farms. 

    Using the above approach will I have to create a scope for all of the 100+ content sources that are being scoped?   this is a huge amount of effort to simply exclude results with the word diasabled and test in them!

    There must be an easier way.   Is there anyway to add these words to the offensive dictionery??  Why on earth did they remove stopwords - this was so very, very useful.

    Hope you can advise

    Thank you

    Mike


    Mike Bennett
    Wednesday, October 19, 2011 8:57 PM
  • Hi Mike,

    Dropping documents (in a supported way) is something which it seems was forgotten for FS4SP. There are other threads on this forum on how to achieve this. Using the offensive filter could be a way, except you can't edit the dictionary.

    The only supported way is to have a customer extensibility stage log the id's of the items you want to remove into for example a text file, and then schedule a task to read this list and execute "docpush" with a delete operation per item. This will leave you a small window where the items actually can appear.

    Your other approach is to actually put a lot of bad words in a field for the items and enable the offensive content filter. This will also drop the documents.

    There are some information at http://msdn.microsoft.com/en-us/library/ff795826.aspx#optional-item-proc-offensive which mentions using the xmlmapper to map content into the "ocfcontribution" field which is scanned for bad words.

    Regards,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    Wednesday, October 19, 2011 9:06 PM
  • Hi Mikeal

    Thanks so much for the reply.   Pity there is nothing simple to this.

    Does the above also apply to sharepoint people searches found n the query ssa or is there a way to do something is SP (the non-fast area)

    Mike


    Mike Bennett
    Friday, October 21, 2011 1:36 PM
  • Hi Mike,

    As for people search (or built-in SharePoint search) there are no ways to exclude content except for what you can accomplish with crawler rules. Not sure if crawler rules apply to people search, as I think all user profiles will be indexed, and the only crawl rule I've seen mentioned for people search is to use one for authentication.

    Regards,
    Mikael Svenson 


    Search Enthusiast - SharePoint MVP/WCF4/ASP.Net4
    http://techmikael.blogspot.com/
    Friday, October 21, 2011 2:03 PM