SharePoint Search and the Inconvenient MetadataExtractorTitle Crawled Property


References:

I recently came across a problem in SharePoint Search which had me flumuxed for a while, looking at the search results below is displayed the results of 2 list items, 1 with a PowerPoint attachment and 1 without any attachment. The 1 with an attachment is showing an extracted document property as the Title managed property value rather than using the listitem’s Title column value;

spsearch01

Removing all of the document properties from the attached file had no effect, as the search result Title text shown is the text of PowerPoint documents first slide.

Managed Property Mappings

Looking at the managed property mappings for the Title managed property shows the following crawled property mappings;

spsearch02

As you can see the MetadataExtractorTitle crawled property is further up the list than the (SharePoint listitem) ows_Title crawled property, so I then tried moving the ows_Title crawled property right to the top of the list which you’d expect to work given the description of crawled property mappings;

Include content from the first crawled property that is not empty, based on the specified order.

This, however, didn’t work either and the search results showed the same.

I then tried moving the ows_Title crawled property to the top and the MetadataExtractorTitle crawled property right to the bottom of the list of crawled property mappings for the Title managed property and this did work, search results showed the Title value from the list item’s Title column;

spsearch03

The search results now show the correct Title value;

spsearch04

The reason as far as I can understand is that, when considering the crawled property to use as the source of the value for a managed property, the crawled property should have a non-empty value, and then when multiple crawled properties have a value, the weight of the crawled property is taken into consideration to determine the final crawled property to use. It would seem that the MetadataExtractorTitle property has a higher weight than ows_Title in this case.

Published by

Phil Harding

SharePoint Consultant, Developer, Father, Husband and Climber.

7 thoughts on “SharePoint Search and the Inconvenient MetadataExtractorTitle Crawled Property

  1. Hi, we are having same issue. However, we changed the schema to use ows_title first ( column title ) , then title ( docuemnt tile ? ) , the metadataextractor title. However, it is still not showing ows_title. Any ideas ?

  2. According to the MS documentation on this ows_Title is not the list item title. It is the SharePoint Page Title. I think what made this work for you is that the managed property “Title” was now higher than the MetadataExtractorTitle once it was moved to the bottom. In either case, the search results will show the value for the first crawled property that is not null based on the order of the mapping.

    https://blogs.msdn.microsoft.com/spses/2013/10/30/show-more-relevant-titles-in-search-results-in-sharepoint-2013-plus-some-other-improvements/

  3. Nice inputs! We had also the same Issue and for us it was enough to set the Title who is in the 7th Position to the 2nd Position.
    I know it looks strange with 2x Title but I think that the first one dont take any impact

  4. Hi Phil,
    Quick question… When you change the order of metadataextractor to the bottom of the bottom of Mappings To Crawled Properties List….. Did you have to do a full crawl, or does changing the order of the list immediately take.
    Thanks!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.