本文為機器翻譯文章。如需檢視英文版,請選取 [原文] 核取方塊。您也可以將滑鼠指標移到文字上,即可在快顯視窗顯示英文原文。
譯文
原文

Search driven publishing features are now available in SharePoint Online

 

上次修改主題的時間: 2014-06-07

Summary:Learn about the search-driven publishing features available in SharePoint Online.

Microsoft recently announced that search-driven publishing features are available in SharePoint Online. For more information, see Search innovations for site and portal design in SharePoint Online. To understand the significance of search-driven publishing features, the following analogy might be useful.

While watching a TV show, sometimes we may not be happy with the direction the producers are taking. We tell our friends "If I were a producer, I would never…", or "What were they thinking when…". For search-driven publishing, think of the various features as actors, and think of yourself as the producer. By using the SharePoint features (actors), you (the producer) can create a website (TV show) of your own.

As you know, every TV show has its stars. The two mega stars of search-driven publishing are the Content Search Web Part (CSWP) and Cross-Site Collection Publishing features. The CSWP uses search technology to display content on a page. When visitors browse to a page that contains a CSWP, the CSWP automatically issues a query. The search results are displayed within the Web Part. The Cross-Site Collection Publishing feature enables you to create and maintain content in one site collection, and publish this content across other site collections.

Just as TV stars need supporting actors and cast members to be successful, these two features need other SharePoint features to really shine. This article will briefly introduce "the entire cast" of search-driven publishing, and provide links to documentation that describes how you can "put yourself in the producer’s chair," and use these features to create your SharePoint Online site.

sdp Poster

In this article, you will learn:

The search-driven publishing features are available in the following SharePoint Online plans:

重要事項 重要事項:
Search-driven publishing features are only available for private site collections.
site collections


Cross-site publishing is a publishing method that lets you create and maintain content in one or more authoring site collections, and publish this content across one or more publishing site collections by using Search Web Parts. Cross-site publishing will help make life easy as it:

  • Can be used across site collections.

  • Separates content authoring from branding and rendering, meaning how you author content has nothing to do with how it is displayed to users.

  • Allows you to mix pages and catalog content.

Cross-site publishing uses search technology to retrieve content. Here's how it works in five simple steps:

xsp explained
  1. You create content in lists and libraries. Site columns are used to store values, or in other words information, about each item in a list or library. On these lists and libraries, you select a setting that enables them as catalogs.

  2. The content in your catalogs is crawled. During crawl, site columns and the site column values are added to the search index.

  3. In the search index, site columns are "transformed" into managed properties. Site column values are "transformed" into managed property values.

  4. You add one or more Search Web Parts to the site collections where you want to display your catalog content. The Search Web Parts use display templates that specify which managed property values should be displayed.

  5. When visitors view a page, the Search Web Parts automatically issue queries to the search index. Query results are returned from the search index, and shown in the Search Web Parts.

When you change content in a catalog on the authoring site collection, the changes are shown across all publishing site collections that are using that content.


When you use cross-site publishing, you will often use one or more site collections to author and store content, and one or more site collections to show this content. For information about how to create site collections, see Create or delete a site collection.


When you have created the site collections that you need, the next step is to activate a few site collection features.

Here’s an overview of the site collection features you will need:

Authoring site

Feature Why you need this feature How you can activate it

Cross-Site Collection Publishing

To enable libraries and lists as catalogs

Activate the Cross-Site Publishing feature in SharePoint

SharePoint Server Publishing Infrastructure

To create and share term sets in the site collection

Enable publishing features

注意事項 附註:
This feature is activated on the site collection level.

Publishing site

Feature Why you need this feature How you can activate it

SharePoint Server Publishing Infrastructure

To be able to activate the SharePoint Server Publishing feature

Enable publishing features

注意事項 附註:
This feature is activated on the site collection level.

SharePoint Server Publishing

To connect to a catalog

Enable publishing features

注意事項 附註:
This feature is activated on the site level.


When you create catalog content in SharePoint lists or libraries, you should use site columns. This is because during crawl, managed properties are automatically created for site columns.

重要事項 重要事項:
Columns that you create directly from a library or list will not automatically become managed properties during crawl. For more information, see 從 managed 屬性集的網站欄什麼是使用?.

Later, when you configure Content Search Web Parts, you can use these automatically generated managed properties to define queries and show catalog content on a publishing site. For information on how to create site columns, see Create a site column.

If you have several lists or libraries, you should create a site content type for each list or library, and then associate the appropriate site columns to this site content type. For information on how to create a site content type, see Create or customize a site content type.

If you want to use managed navigation (see How to enable managed navigation for a site) to display catalog content on a publishing site, you have to create at least one term set that is associated with a site column of type Managed Metadata. You should use this term set to tag the items in your lists or libraries. For information see:


To enable a library or list as a catalog, you need to select a setting on the library or list. For information on how to do this, see Enable a library or list as a catalog in SharePoint.

The reason why you want to enable a library or list as a catalog, is that this will later enable you to use the Managed catalog connections feature (for more information, see How to connect a publishing site to a catalog). By using the Managed catalog connection feature, you can create friendly URLs for your publishing site.


After you have enabled a library or list as a catalog, you must crawl the catalog so that the content is added to the search index. SharePoint will automatically start a crawl at a set interval. However, if you don’t want to wait for the automatic crawl, you can initiate a re-indexing of the catalog. There are also some types of changes (for example, if you have changed the settings of a managed property) that require you to do a re-indexing of the catalog.

For more information, see Manually request crawling and re-indexing of a site, a library or a list.


If you want to integrate the catalog tagging term set into the publishing site navigation term set (you can do this by using the How to connect a publishing site to a catalog), the catalog tagging term set must be available to the publishing site collection.

Global term sets are by default available to all site collections within your tenant. However, if your catalog tagging term set is a local term set, that is, it was created on a site collection level, you have to make it available to the publishing site collection.

For information on how to do that, see Make a term set available to other site collections in SharePoint.


Managed navigation is a navigation method that lets you define and maintain your site navigation by using term sets.

One of the benefits of using managed navigation is that it is independent from where you store your content. With managed navigation, it's not where you store your content that defines where in the navigation it’ll will appear, but how you tag your content with terms from a term set. For example, in previous versions of SharePoint, if you wanted to add a new page under "About our company," you had to add that new page under the "About our company" page in your content hierarchy. With managed navigation, you can add a page anywhere in your content hierarchy. By tagging that page with a term, and using Search Web Parts, the page will appear in the correct place in the navigation.

Another benefit of managed navigation is that it creates friendly URLs. In previous versions of SharePoint, the URL to a page contained a reference to the Pages library and included the .aspx file extension, for example: http://www.contoso.com/pages/cameras/camera-accessories.aspx. With managed navigation, URLs are based on the terms in the term set that drives your site navigation, for example: http://www.contoso.com/cameras/camera-accessories.

For more information about managed navigation, see Enable managed navigation for a site in SharePoint.


To connect a publishing site to a catalog, you can use the Managed catalog connections feature. By using this feature, you can configure friendly URLs for you catalog item pages. However, this feature can do much more than that. It can also:

  • Integrate catalog content into the publishing site collection.

  • Integrate the tagging term set used by the catalog into the navigation term set of the publishing site collection.

  • Create a category page and an item details page.

  • Create a result source for the catalog.

For information on how to use the Managed catalog connections feature, see Connect and disconnect a publishing site to a catalog in SharePoint.


Category pages and catalog item pages are page layouts that you can use to show catalog content on a site. By using these pages in combination with managed navigation, you can save yourself the work of having to create many individual pages for content that you want to display in a consistent manner across your site. To be able to display content with a category page and a catalog item page, you will have to assign the pages to a term in the term set that drives managed navigation.

For information on how to do that, see Assign a category page and a catalog item page to a term in SharePoint.


The Content Search Web Part (CSWP) uses, as its name implies, search technology to display content.

Most of us use search technology on a daily basis. Think about how many times a day you enter query terms in a search box, for example on bing.com; how after pressing Enter, you scan search results that are almost immediately displayed on a search results page.

When visitors browse to a page that contains a CSWP, they're actually issuing a query. However, the thing that differs with CSWPs is that instead of entering query terms in a search box, the query is contained within the Web Part itself. This means that when a visitor browses to a page that contains a CSWP, this query is automatically issued.

Another thing that is different from the bing.com search scenario is that search results aren't displayed on a separate search results page, but within the CSWP. In most cases, visitors won't even know that search technology is being used to display the content they're viewing. To them, it'll look and feel like any other webpage.

By configuring the query in the CSWP, you define which content visitors will see when they browse to a page that contains a CSWP. By default, the query in the CSWP is configured to show the three last recently changed items within the site. By configuring the query, you can change both the number of items that are shown in the CSWP, and also which content is shown. For example, you can configure the query so that the CSWP will show nine list items from a particular list, or the last six documents the visitor created in a document library

For information on how to configure the CSWP, see Configure a Content Search Web Part in SharePoint.


Continuing our TV show analogy, you know that some actors appear in a variety of shows, whereas others appear only in one or two. The same goes for search driven publishing features: some are available in both SharePoint Online and SharePoint on-premise, whereas others are only available in SharePoint on-premises.

The features we have discussed in this article are available both in SharePoint Online and SharePoint on-premises. The following features are only available in SharePoint on-premises:

  • Anonymous access

  • The Product Catalog Site Collection template

  • Refiners for faceted navigation

  • The Taxonomy Refinement Panel Web Part


As mentioned at the beginning of this article, the features discussed in this article are available in SharePoint Server 2013. To continue with the TV series analogy, even though you have actors at your disposal, the actors themselves will not create the TV show. That is the job of the producer.

So, you (the producer) will have to have a plan for what you want the TV show (website) to be all about.

如何設定 SharePoint Server 2013 中的產品中心網站 walks through an example of how to use search-driven publishing features to set up a website for "Contoso Electronics."

重要事項 重要事項:
Not all features described in this series are available in SharePoint Online. Also, the configuration steps described in this series might vary a bit from how you configure the features in SharePoint Online. However, the series includes many screenshots that might give you a better understanding of how the features work together.


https://technet.microsoft.com/zh-tw/library/dn794246.aspx
顯示: