1 / 16

Branding SharePoint Search Results

Branding SharePoint Search Results. Cory Peters – Solutions Architect Eastridge Technology www.corypeters.net. Why do we need search?. Cost of gathering the information can outweigh it’s value Employees need access to internal information in order to make good, timely decisions

merritt-baldwin
Télécharger la présentation

Branding SharePoint Search Results

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Branding SharePoint Search Results Cory Peters – Solutions Architect Eastridge Technology www.corypeters.net

  2. Why do we need search? • Cost of gathering the information can outweigh it’s value • Employees need access to internal information in order to make good, timely decisions • Fill in the knowledge gaps

  3. How do we search?

  4. What do we expect? • Requires confidence in the search engine • SharePoint 2007 • 100% better on all queries • 500% better on common queries • New ways to visualize search results Compared to SharePoint 2003

  5. Visual is better

  6. With SharePoint we have control • Document Libraries with known metadata schemes • Picture Libraries • Wikis • Blogs • Calendar Events • Tasks, etc.

  7. What does SharePoint give us?

  8. ContentClass

  9. Managed Properties Site / List Column Incremental Crawl Create Managed Property Crawled Property Full Crawl Managed Property No Data Managed Property With Data

  10. Search Core Results Web Part • Selected Columns • Raw Output • Data View XSL

  11. Selected Columns

  12. Raw Output <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/> <xsl:template match="/"> <xmp><xsl:copy-of select="*"/></xmp> </xsl:template> </xsl:stylesheet>

  13. Data View XSL

  14. Demo

  15. Best Practices • Use “Include values from a single crawled property based on the order specified” when creating your Managed Properties • Break your main logic up into an xsl:choose statement and use an xsl:when test for each ContentClass • Store any supporting files in either the 12 hive or the Style Library to avoid permission issues • Use the ows_ version of the crawled property • Keep any CSS / Javascript in global files using master pages

  16. Questions

More Related