This is a collection of questions and answers about Microsoft® Content Management Server (MCMS) gathered from the MCMS newsgroup. This content is provided "AS IS" with no warranties, and confers no rights. If you have feedback about one of these topics or would like to add information, please post your comments to the MCMS newsgroup.

 

Thank you,

Stefan Goßner Escalation Engineer

Steve Cawood Program Manager

MCMS 2002 - Search FAQ - Table of Contents

Excluding navigation menu text
SharePoint Portal Server search whitepaper
Supporting incremental searches

Topic: Excluding navigation menu text

I've got a MCMS 2002 Web site which is indexed by Microsoft SharePoint™ Portal Server 2001. It's all working fine but I have a problem that I've not been able to crack.

The navigation menus on the Web site are constructed as user controls with code behind them to read the channels and construct the menu. These user controls are simply dropped onto each template that I create. The problem is, if I search on a word that is in these menus then the search results contain every page in the Web site, as the menus are part of every page in the Web site. Does anyone know how I can get my search engine to look at everything in the Web page except the navigation menus?

An additional issue is that the page summaries generated by Microsoft SharePoint Portal Server always generate the same content for all pages because the navigation menu is placed in the HTML file before the real content.

Answer

This is a known issue. To bypass it you can do the following.

Within your navigation control perform the following test:

    if (Request.Headers["User-Agent"].IndexOf("MS Search") < 0)

Only render the navigation when this test is true. This means that the navigation control will not be rendered when Microsoft SharePoint Portal Server search requests the page.

However, only the start page will be indexed because no navigation exists. For this reason you have to include a second navigation control at the very end of your template (I have named my control RobotNavigation). It must be at the end to bypass the page summary issue.

This control needs to do a similar test :

    if (Request.Headers["User-Agent"].IndexOf("MS Search") >= 0)

This navigation control should use a unique word for the link text. This ensures that this word is never searched. If it was searched, you would get lots of hits on it. I use "RbtLnk" (short for RobotLink) as the link text.

[Back to Top]

Topic: SharePoint Portal Server search whitepaper

How can I integrate Microsoft® SharePoint™ Portal Server Search with MCMS 2002?

Answer

Search is discussed in this TechNet article about MCMS and Microsoft SharePoint Portal Server:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmscms02/html/mcmssrch.asp

[Back to Top]

Topic: Supporting incremental searches

How do I configure MCMS pages/templates to support incremental searches (assuming that the crawler determines what has been changed using the "Last-Modified" header)?

Answer

Use the following code in the Page_Load event of the template to emit the last modified date stored in MCMS:

private void Page_Load(object sender, System.EventArgs e)
  {
   // Add last modified date to http response
   Response.AppendHeader("Last-Modified",
                 CmsHttpContext.Current.Posting.LastModifiedDate.ToString("r"));
  }

[Back to Top]

The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2004 Microsoft Corporation. All rights reserved.

Microsoft, ActiveX, Visual Studio, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.