SharePoint Server 的跨網站發佈概觀Overview of cross-site publishing in SharePoint Server

摘要: 了解如何使用跨網站發佈與搜尋網頁組件,建立調適型 SharePoint Server 網際網路、內部網路及外部網路網站。Summary: Learn how you can use cross-site publishing and Search Web Parts to create adaptive SharePoint Server Internet, intranet, and extranet sites.

SharePoint Server 中的跨網站集合發佈功能運作方式如下:使用一或多個製作網站集合來編輯和儲存內容,以及使用一或多個發佈網站集合,來控制網站的設計和顯示內容。此項功能稱為跨網站發佈。製作網站集合包含像是頁面庫與清單等目錄,以中繼資料標記其中所含的內容。搜尋系統會為這些目錄編製索引並提供給發佈網站集合。發佈網站集合可查詢已編製索引的資料,以及使用運用搜尋技術的網頁組件 (在本文中稱為搜尋網頁組件) 顯示在網頁上。使用主版頁面、頁面配置及顯示範本,塑造發佈網站上的內容品牌。The Cross-Site Collection Publishing feature in SharePoint Server works in the following way: you use one or more authoring site collections to author and store content, and one or more publishing site collections to control the design of the site and to show the content. The functionality provided by this feature is referred to as cross-site publishing. The authoring site collection contains catalogs, such as Pages libraries and lists, which contain content that is tagged with metadata. These catalogs are indexed by the search system and made available to the publishing site collection. The publishing site collection issues queries for data that has been indexed and shows it on web pages by using Web Parts that use search technology (referred to in this article as Search Web Parts). You brand content on the publishing site by using master pages, page layouts, and display templates.

下圖顯示如何在製作網站集合中儲存由搜尋系統編製索引的內容,以及在三個不同的發佈網站集合 (1 : n) 間重複使用。The following illustration shows how content is stored in an authoring site collection, indexed by the search system, and then reused across three separate publishing site collections (1 : n).

跨網站發佈圖表

  1. 以文件庫與清單的形式建立的內容,會視為目錄在製作網站集合中共用。Content is created in libraries and lists that are shared as catalogs in the authoring site collection.

  2. 搜尋系統將內容編目,並建立搜尋索引。The search system crawls the content and builds the search index.

  3. 使用者檢視發佈網站的頁面時,會觸發搜尋網頁組件執行查詢。A user views a page on a publishing site, which triggers queries from Search Web Parts.

  4. 搜尋索引會回傳結果並顯示在該頁面的「搜尋網頁組件」。Results are returned from the search index, and shown in Search Web Parts on the page.

本文說明跨網站發佈功能的用途與優點、說明編輯與發佈網站集合,以及說明搜尋系統如何將內容與中繼資料編目和編製索引。最後,本文會討論跨網站發佈功能的重要限制。在您閱讀本文之後,請務必閱讀下一篇文章<規劃 SharePoint Server 跨網站發佈的邏輯架構>。如需其他發佈方法以及如何決定是否要使用跨網站發佈功能的資訊,請參閱<在 SharePoint Server 中發佈至網際網路、內部網路及外部網路網站的功能概觀>與<規劃 SharePoint Server 的網際網路、內部網路及外部網路發佈網站>。This article describes the use and benefits of cross-site publishing, describes the authoring and publishing site collections, and describes how the search system crawls and indexes content and metadata. Finally, this article discusses important limitations of cross-site publishing. After you read this article, make sure that you read the next article, Plan the logical architecture for cross-site publishing in SharePoint Server. For information about other publishing methods, and how to decide whether to use cross-site publishing, see Overview of publishing to Internet, intranet, and extranet sites in SharePoint Server and Plan for Internet, intranet, and extranet publishing sites in SharePoint Server.

SharePoint 跨網站發佈功能的用途與優點Use and benefits of SharePoint cross-site publishing

您可以使用跨網站發佈功能,以數種不同的方式來重複使用內容。您可以從單一製作網站集合製作內容,提供給單一發佈網站集合 (1:1)、從單一製作網站集合製作內容,提供給一或多個發佈網站集合 (1: n)、從多個製作網站集合製作內容,提供給單一發佈網站集合 (n: 1),或是從多個製作網站集合製作內容,提供給多個發佈網站集合 (n:n)。使用跨網站發佈功能的方式取決於您想要建立的發佈解決方案類型。下表說明可能會使用跨網站發佈功能的狀況。You can use cross-site publishing to reuse content in several different ways. You can use it to make content from a single authoring site collection available to a single publishing site collection (1:1), to make content from a single authoring site collection available to one or more publishing site collections (1: n), to make content from more than one authoring site collection available to a single publishing site collection (n: 1), or to make content from more than one authoring site collection available to more than one publishing site collection (n:n). How you use cross-site publishing is determined by the type of publishing solution that you want to create. The following table describes possible scenarios in which you might use cross-site publishing.

SharePoint 跨網站發佈案例SharePoint cross-site publishing scenarios

案例Scenario 描述Description
網際網路網站Internet site
您可以使用跨網站發佈功能,根據中繼資料來建立網際網路網站,其中包含向客戶展示產品的目錄。使用者可檢視根據功能窗格而動態建立的頁面,以及根據其他精簡搜尋來篩選結果。網站也可以顯示像是公司連絡人頁面、運送與處理費率以及工作機會等內容。內容是在內部編輯,然後才提供給防火牆外部的匿名使用者。You can use cross-site publishing to create an Internet business site that contains a catalog that shows products to customers, based on metadata. Users view pages that are created dynamically based on navigation, and filter results based on additional refinements. The site may also show content such as a company contact page, shipping and handling rates, and job openings. Content is authored internally, and is made available to anonymous users outside the firewall.
內部網路網站Intranet site
您可以使用跨網站發佈功能,建立內部的人力資源 (HR) 網站,使用受到嚴密管理的導覽結構,來顯示編寫的內容。內容是由一小群的人員編輯,並供一大群具有「讀取」權限層級的人員使用。You can use cross-site publishing to create an internal Human Resources (HR) website that uses a tightly managed navigation structure to show authored content. Content is authored by a small group of people, and consumed by a large group of people with the Read permission level.
外部網路網站Extranet site
您可以使用跨網站發佈功能來建立知識庫,以外部網路網站提供給內部與外部使用者使用。內容作者會以中繼資料標記頁面,對文章進行分類,讓使用者可以搜尋或瀏覽特定資訊,例如疑難排解文章、支援議題以及 Service Pack。You can use cross-site publishing to create a knowledge base that is available to internal and external users in an extranet site. Content authors tag pages with metadata to categorize articles so that users can search or browse for specific information, such as troubleshooting articles, support issues, and service packs.
多語系網站Multilingual sites
您可以搭配變化與翻譯功能來使用跨網站發佈功能,建立多個可針對特定語言或地區設定顯示翻譯內容的網站。例如,您可以在位址為 .com、.fr 及 .de 的網站上,分別顯示英文、法文及德文內容。網際網路、內部網路及外部網路網站全都可以是多語系網站。You can use cross-site publishing together with the variations and translation features to create multiple sites that show translated content for specific languages or locales. For example, you can have English, French, and German content that is shown on sites that have .com, .fr, and .de addresses. Internet, intranet, and extranet sites can all be multilingual sites.

在 SharePoint Server 中,跨網站發佈功能可提供下列優點:In SharePoint Server, cross-site publishing provides the following benefits:

  • 提供廣泛的可行網站架構。Provides a broad range of possible site architectures.

  • 從品牌塑造和轉譯中區隔出內容編輯。Separates content authoring from branding and rendering.

  • 可以和發佈網站上的使用者匿名共用內容。Allows content to be shared anonymously with users on the publishing site.

  • 可以跨網站集合、Web 應用程式使用,還可以跨伺服器陣列使用。Can be used across site collections, web applications, and also across farms.

  • 允許混合編寫的頁面與清單內容。Allows for a mix of authored pages and list content.

適用於 SharePoint 跨網站發佈功能的製作網站集合Authoring site collections for SharePoint cross-site publishing

使用跨網站發佈功能時,建立和儲存內容的網站集合,可以和使用者檢視內容的網站集合不同。製作網站集合包含以目錄的形式共用的頁面庫與清單。本節說明在針對可跨發佈網站集合重複使用的內容,設定製作網站集合時所涉及的功能。When you use cross-site publishing, you create and store content in a different site collection than the site collections where users view the content. The authoring site collection contains Pages libraries and lists, which have been shared as catalogs. This section explains the features that are involved when you set up the authoring site collection for the content that will be reused across publishing site collections.

內容類型Types of content

您可以在製作網站集合以文件庫與清單的形式儲存不同的內容類型。以目錄的形式共用這些文件庫與清單,您可以在一或多個發佈網站集合重複使用其中所含的資料。根據預設,可由搜尋系統編製索引和傳回的只有 HTML 內容。像是 Word 文件與 PDF 等的非 HTML 內容不會儲存在索引中,而必須直接參照。下列清單將說明可用於製作網站集合的不同內容類型。You can store different types of content in libraries and lists in the authoring site collection. By sharing these libraries and lists as catalogs, the data that they contain can be reused in one or more publishing site collections. By default, only HTML content is indexed and returned by the search system. Non-HTML content, such as Word documents and PDFs, is not stored in the index, and must be referenced directly. The following list describes the different types of content that you can use in an authoring site collection.

  • 頁面庫。 您可以使用頁面庫,建立您計劃要跨網站集合重複使用的任何 HTML 內容。使用頁面庫,可讓您利用 SharePoint Server 發佈功能集中的核准工作流程與內容排程功能。如需核准工作流程與內容排程功能的詳細資訊,請參閱<規劃內容核准與排程 (SharePoint Server 2010)>。Pages library. You can use a Pages library to create any HTML content that you plan to reuse across site collections. By using a Pages library, you can take advantage of the Approval workflow and content scheduling features that are part of the SharePoint Server publishing feature set. For more information about the Approval workflow and content scheduling, see Plan content approval and scheduling (SharePoint Server 2010).

    注意

    每個網站只能有一個頁面庫。不過,一個網站集合內可以有多個網站,您可以藉此將頁面庫內容放入不同的目錄中。You can have only one Pages library per site. However, you can have multiple sites within a site collection, and thereby put Pages library content into separate catalogs.

  • 清單。 您可以使用一或多個清單,來儲存將其儲存在清單中比在頁面庫中較為適合的任何資料類型。如需何時使用頁面庫與何時使用清單,以及如何規劃頁面庫與清單內容的詳細資訊,請參閱<規劃 SharePoint Server 的跨網站發佈>。List. You can use one or more lists to store any type of data that is better stored in a list than in Pages library content. For information about when to use a Pages library and when to use a list, and how to plan Pages libraries and list content, see Plan for cross-site publishing in SharePoint Server.

  • 資產庫。 如果像是圖片、音訊或視訊檔案等的二進位大型物件檔案 (BLOB) 含有您要顯示在發佈網站上的主要內容,您就可以使用一或多個資產庫來儲存來那些檔案。用以包含頁面或清單 (例如 PDF 或產品圖像) 所參照之 BLOB 的資產庫,對於跨網站發佈功能而言,代表不同的內容類型且必須以不同的方式處理。如需參照圖像與目錄中其他 BLOB 的詳細資訊,請參閱<規劃 SharePoint Server 中跨網站發佈用的製作網站>中,<規劃製作網站的目錄內容>一節的<規劃資產庫內容>。Asset library. You can use one or more Asset libraries to store binary large object files (BLOBs) such as pictures, audio, or video files, if those files contain the primary content that you want to show on the publishing site. Asset libraries that are used to contain BLOBs that are referenced by Pages or lists, such as PDFs or product images, represent a different type of content, and are handled differently for cross-site publishing. For more information about referencing images and other BLOBs in catalogs, see "Plan asset library content" in the "Plan catalog content for authoring sites" section in Plan authoring sites for cross-site publishing in SharePoint Server.

  • 文件庫。 您可以使用一或多個標準 SharePoint Server 文件庫來儲存像是 Word、Excel 文件的檔案。不過,因為這些檔案類型也被視為 BLOB,所以文件庫與資產庫的處理方式相同。如需參照圖像與目錄中其他 BLOB 的詳細資訊請參閱<規劃 SharePoint Server 中跨網站發佈用的製作網站>中,<規劃製作網站的目錄內容>一節的<規劃資產庫內容>。Document library. You can use one or more standard SharePoint Server document libraries to store files such as Word and Excel documents. However, because these types of files are also considered BLOBs, you treat Document libraries in the same manner that you treat Asset libraries. For more information about referencing images and other BLOBs in catalogs, see "Plan asset library content" in the "Plan catalog content for authoring sites" section in Plan authoring sites for cross-site publishing in SharePoint Server.

標記字詞組Tagging term sets

在製作網站中,您可以使用字詞組來標記內容。以一或多個字詞來標記內容時,這些字詞會成為與內容相關聯的中繼資料。搜尋系統在將內容新增至索引時,也會新增相關聯的中繼資料。稍後,在頁面上顯示內容時,還有用於「受管理導覽」時,就會在發佈網站集合中使用該中繼資料。In authoring sites, you use term sets to tag content. When you tag content with one or more terms, the terms become part of the metadata that is associated with the content. When the search system adds content to the index, it also adds the associated metadata. That metadata is later used in the publishing site collections when content is shown on pages, and when used for managed navigation.

目錄組態Catalog configuration

在跨發佈網站集合重複使用文件庫與清單中的內容之前,您必須先共用要作為目錄使用的文件庫和清單。在以目錄的形式共用文件庫與清單時,指定您要與其他網站和網站集合共用。您也可以選擇啟用在目錄中匿名存取內容的功能。您最多還可以選取五個欄位,用來唯一識別目錄中的項目。最後,您要指定單一受管理的中繼資料欄位,用來作為發佈網站集合中的導覽字詞組。以目錄的形式共用文件庫或清單,然後對內容編目和編製索引之後,就可以從發佈網站集合與之連線。如需如何讓發佈網站集合與目錄連線的詳細資訊,請參閱<規劃 SharePoint Server 中供網站間發佈用的製作網站>中的<規劃發佈網站的目錄內容>一節。Before the content in the libraries and lists can be reused across publishing site collections, you have to share libraries and lists for use as catalogs. When you share a library or list as a catalog, you specify that you want to share it with other sites and site collections. You can also choose to enable anonymous access to the content in the catalog. You also select up to five fields that are used to uniquely identify items in the catalog. Finally, you specify a single managed metadata field that is used as a navigation term set in the publishing site collections. After a library or list is shared as a catalog, and the content has been crawled and indexed, you can connect to it from a publishing site collection. For more information about how to connect publishing site collections to catalogs, see "Plan catalog connections for publishing sites" in Plan publishing sites for cross-site publishing in SharePoint Server.

注意

您必須至少新增一段內容,接著務必要使用字詞組中的字詞來加上標記,然後才能以目錄的形式共用文件庫或清單。此外,在建立與標記字詞組相關聯的受管理中繼資料網站欄時,該欄必須是單一值欄位。Before you share a library or list as a catalog, you must add at least one piece of content, and you must tag it with a term from the tagging term set. In addition, when the managed metadata site column that is associated with the tagging term set is created, it must be a single value field.

適用於 SharePoint 跨網站發佈功能的發佈網站集合Publishing site collections for SharePoint cross-site publishing

在使用跨網站發佈功能時,會使用搜尋技術來決定要向使用者顯示的內容。本節說明在建立可從以目錄的形式共用的文件庫或清單中取得資料的發佈網站時所涉及的功能。文中也說明如何使用搜尋功能來影響要向使用者顯示的內容及順序。When you use cross-site publishing, search technology is used to determine what content is shown to users. This section describes the features that are involved when you build a publishing site that obtains data from libraries or lists that are shared as catalogs. It also describes how you can use search features to influence what, and in which order, content is shown to users.

主版頁面與頁面配置Master pages and page layouts

因為來自一或多個製作網站集合的內容可以顯示在一或多個發佈網站集合,所以您必須設定發佈網站集合,以支援塑造方案品牌的需求。這包括設計您用以顯示內容的主版頁面、頁面配置及階層式樣式表 (CCS)。您也可以設定用以控制如何在網站上顯示圖像的圖像轉譯功能。如需如何設計 SharePoint Server 發佈網站的詳細資訊,請參閱<SharePoint 頁面模型概觀>。Because content from one or more authoring site collections is shown on one or more publishing site collections, you have to configure the publishing site collections to support the branding needs of your solution. This includes designing the master pages, page layouts, and cascading style sheets that you use to show content. You can also configure image renditions that are used to control how images are shown on the site. For more information about how to design for SharePoint Server publishing sites, see SharePoint page model overview.

您可以使用字詞組,建立發佈網站集合中的網站導覽。使用的字詞組可用於標記製作網站集合上的內容,亦可固定於由發佈網站集合使用的導覽字詞集。您可以在字詞庫管理工具中設定個別的字詞,自訂整個網站導覽。您也可以新增字詞,或是使用其他字詞組的字詞,額外地自訂網站導覽。如果在建立多語系網站,您可以複製導覽字詞集,然後翻譯成和變化標籤相同的語言。You use term sets to create the site navigation in publishing site collections. Term sets that were used for tagging content on the authoring site collection can be pinned to the navigation term set that is used by the publishing site collection. By configuring individual terms in the Term Store Management Tool, you can customize the navigation for the whole site. You can also add new terms, or use terms from other term sets, to additionally customize the site navigation. If you are creating multilingual sites, you can copy the navigation term set and translate it into the same languages that are used for variation labels.

目錄連線Catalog connections

您必須在將使用目錄的發佈網站集合中設定目錄連線,然後才能顯示製作網站集合中的內容。設定目錄連線時,您要指定發佈網站集合將用以顯示內容的目錄。在設定目錄連線時,您可以指定的資訊包括是否將目錄內容整合到網站、在哪裡放置要用於導覽的類別、標記時所用的字詞組,以及應如何建構類別項目 URL。如需如何讓發佈網站集合與目錄連線的詳細資訊,請參閱<規劃 SharePoint Server 中供網站間發佈用的製作網站>中的<規劃發佈網站的目錄內容>一節。Before you can show content from an authoring site collection, you have to configure the catalog connections in the publishing site collection that will consume those catalogs. When you configure catalog connections, you specify which catalogs the publishing site collection will use to show content. When you configure a catalog connection, you specify information such as whether to integrate catalog content into the site, where to put the categories to use for navigation, the term set that was used for tagging, and how category item URLs should be constructed. For more information about how to connect publishing site collections to catalogs, see "Plan catalog connections for publishing sites" in Plan publishing sites for cross-site publishing in SharePoint Server.

類別頁面與目錄項目頁面Category pages and catalog item pages

類別頁面與目錄項目頁面屬於頁面配置,您可用來以一致的方式顯示整個網站的結構化目錄內容。根據預設,SharePoint Server 會對每個目錄連線自動建立一個類別頁面配置與一個目錄項目頁面配置。讓網站與目錄連線時,就會在發佈網站的頁面庫中,根據這些配置來建立頁面。這些頁面要注意下列事項:Category pages and catalog item pages are page layouts that you can use to show structured catalog content consistently across a site. By default, SharePoint Server can automatically create one category page layout and one catalog item page layout per catalog connection. Pages based on these layouts are created in the Pages library of a publishing site when you connect the site to a catalog. These pages have the following considerations:

  • 不是為您所發佈。They are not published for you.

  • 您應該編輯頁面配置的 HTML。請從類別頁面配置與目錄項目頁面配置開始。You should edit the HTML of the page layouts. The category page layout and the catalog item page layout are meant to be used to get you started.

  • 當您編輯 HTML 頁面配置時,會同步處理至對應的 ASPX 頁面。如果您想要直接編輯 ASPX 頁面,應該先刪除 HTML 版本。When you edit the HTML page layouts, they are synced back to the corresponding ASPX pages. If you prefer to edit the ASPX pages directly, you should first delete the HTML version.

使用類別頁面與目錄項目頁面,就不必建立針對要在整個網站以相同方式顯示的內容,建立許多個別的頁面。類別頁面與目錄項目頁面通常會與受管理導覽和搜尋網頁組件一起使用。您可以透過用於受管理導覽的字詞組內的特定字詞,來與類別頁面或目錄項目頁面關聯。例如,在內部網路案例中,所有事件 (公司) 會在以目錄的形式共用的清單中維護為項目。在該清單中,每個事件都會以字詞組 (定義公司內的不同部門) 中的字詞來標記 例如,「行銷」或「人力資源」。您希望整個網站能以相同的方式顯示事件的相關資訊 例如,有可顯示各部門發生之所有事件的概觀頁面,而且個別的每一事件都有一個頁面。若要避免對每個部門都建立一個概觀頁面,您可以建立一個類別頁面,以相同的方式來顯示所有部門的事件概觀。您也可以建立目錄項目頁面,來供每個事件使用。接著,設定類別頁面或目錄項目頁面上的搜尋網頁組件,確保向使用者顯示的內容,取決於以目錄形式共用的清單中所維護的事件資訊。By using category pages and catalog item pages, you do not have to create many individual pages for content that you want to show in the same manner across your site. Category pages and catalog item pages are often used in combination with managed navigation and Search Web Parts. You can associate a category page or catalog item page with a specific term within the term set that is used for managed navigation. For example, in an intranet scenario, all company events are maintained as items in a list that is shared as a catalog. In the list, each event is tagged with a term from a term set that defines the different departments within the company — for example, Marketing, or Human Resources. You want the information about the events to be shown in the same manner across your site — for example, an overview page showing all events for each department, and one page per individual event. To avoid having to create an overview page for each department, you can create one category page that you can use to show the overview of events for all departments in the same manner. You can also create a catalog item page that you can use for each event. Then you configure Search Web Parts on the category pages or catalog item pages to make sure that the content that is shown to users varies depending on the event information that is maintained in the list that you shared as a catalog.

根據預設,以類別頁面配置為基礎的頁面會以 Category- <catalog name> 的名稱新增至頁面庫。該頁面適用於目錄導覽結構內的所有層級,但最後一層 (目錄項目) 除外。例如,在連線到電子產品清單的網際網路商業案例中,預設的類別頁面適用於目錄導覽所使用字詞組內的所有字詞,例如,電腦、音訊、筆記型電腦及 MP3 播放器。在字詞庫管理工具的 [字詞導向頁面]**** 索引標籤上,會顯示類別頁面與字詞間的關聯。類別頁面配置的功能如下:By default, a page based on the category page layout is added to the Pages library with the name Category-. The page is applied to all levels, except the last (catalog item), within the catalog navigation structure. For example, in an Internet business scenario where you connect to a list of electronic products, the default category page is applied to all terms within the term set that is used for catalog navigation, such as Computers, Audio, Laptops, and MP3 players. The association between a category page and a term is shown in the Term Store Management Tool, on the TERM-DRIVEN PAGES tab. The category page layout has the following features:

  • 類別頁面配置有四個網頁組件區域:本文、左方、正下方及右方。The category page layout has four Web Part zones: Body, Left, Bottom Center, and Right.

  • 可將內容搜尋網頁組件新增至本文網頁組件區域。A Content Search Web Part is added to the Body Web Part zone.

  • 內容搜尋網頁組件中預先設定的查詢,會使用在目錄連線期間自動建立的結果來源。結果來源會以目前與子頁面導覽字詞的搜尋結果為限。The query in the Content Search Web Part is pre-configured to use the result source that is automatically created during catalog connection. The result source limits search results to the current and sub-page navigation terms.

  • 使用的項目顯示範本是圖片在上方,而文字行在下方 (在主版頁面圖庫中稱為 Item_Picture3Lines)。The item display template that is used is Picture on top, 3 lines on bottom (known as Item_Picture3Lines in the Master Page Gallery).

根據預設,以目錄項目頁面為基礎的頁面會以 CatalogItem- <catalog name> 的名稱新增至頁面庫。該頁面適用於目錄導覽結構內的最後一層 (目錄項目) — 例如,顯示個別產品 Contoso Digital Camera M200。在字詞庫管理工具的 [字詞導向頁面]**** 索引標籤上,會顯示目錄項目頁面與目錄內的項目間的關聯。目錄項目頁面配置的功能如下:By default, a page based on the catalog item page is added to the Pages library with the name CatalogItem-. The page is applied to the last level (catalog item), within the catalog navigation structure — for example, to show the individual product Contoso Digital Camera M200. The association between a catalog item page and items within the catalog appears in the Term Store Management Tool, on the TERM-DRIVEN PAGES tab. The catalog item page layout has the following features:

  • 目錄項目頁面有一個網頁組件區域:本文。The catalog item page has one Web Part zone, Body.

  • 可將目錄項目重複使用網頁組件新增至本文網頁組件區域。A Catalog-Item Reuse Web Part is added to the Body Web Part zone.

  • 目錄項目重複使用網頁組件中預先設定的查詢,會使用在目錄連線期間自動建立的結果來源,並以根據額外的查詢篩選器所搜尋到的結果為限。The query in the Catalog-Item Reuse Web Part is pre-configured to use the result source that was automatically created during catalog connection, and to limit search results based on an additional query filter.

  • 除了本文網頁組件區域中的目錄項目重複使用網頁組件之外,還會為目錄中的每個索引欄位,將一個伺服器端的目錄項目重複使用網頁組件新增至目錄項目頁面配置。根據預設,和第一個目錄項目重複使用網頁組件一樣,頁面上的所有目錄項目重複使用網頁組件都會使用相同的查詢。這些欄位會在伺服器端以該頁面配置來轉譯,只有直接編輯目錄項目頁面配置,才能加以變更。因為這些是伺服器端的網頁組件,所以您應該編輯 HTML 來源頁面,指定要和目錄內容一起轉譯的 HTML。In addition to the Catalog-Item Reuse Web Part in the Body Web Part zone, one server-side Catalog-Item Reuse Web Part is added to the catalog item page layout for each indexed field in the catalog. By default, all Catalog-Item Reuse Web Parts on a page use the same query as the first Catalog-Item Reuse Web Part. These fields render server-side in the page layout, and can only be changed by editing the catalog item page layout directly. Because these are server-side Web Parts, you should edit the HTML source page to specify the HTML that is rendered together with the catalog content.

如需類別頁面與目錄項目頁面的詳細資訊,請參閱<規劃 SharePoint Server 中供網站間發佈用的製作網站> 中的<規劃類別頁面與項目詳細資料頁面>。For more information about category pages and catalog item pages, see "Plan category pages and item detail pages" in Plan publishing sites for cross-site publishing in SharePoint Server.

搜尋網頁組件Search Web Parts

搜尋網頁組件採用搜尋技術,來顯示編目後新增至索引的內容。在搜尋網頁組件中,事先設定的查詢可以特定的排名順序顯示搜尋索引中的內容子集。當使用者瀏覽內含搜尋網頁組件的頁面時,網頁組件就會自動發出該查詢。接著在網頁組件中顯示結果。Search Web Parts use search technology to show content that was crawled and added to the index. In Search Web Parts, queries are configured so that a subset of content from the search index is shown in a particular ranking order. When users browse to a page that contains a Search Web Part, the Web Part automatically issues the query. The result is then shown in the Web Part.

搜尋網頁組件通常會與受管理導覽和類別頁面與目錄項目頁面一起使用。例如,在顯示產品型錄的網際網路商業案例中,為受管理導覽指定之字詞組內的字詞,會和特定的類別頁面相關聯。類別頁面上的內容搜尋網頁組件可以讓目前的導覽類別 (字詞) 成為查詢的一部分。當使用者瀏覽到類別 (例如,電腦) 時,網頁組件就會發出查詢,傳回和顯示歸類為電腦的搜尋索引中的所有項目。同樣地,使用者瀏覽到音訊類別時,同一類別頁面上的相同網頁組件將會顯示歸類為音訊的搜尋索引中的項目。Search Web Parts are often used in combination with managed navigation and category pages and catalog item pages. For example, in an Internet business scenario where a product catalog is shown, a term within the term set specified for managed navigation is associated with a specific category page. A Content Search Web Part on a category page can have the current navigation category (term) as part of the query. When users browse to a category, such as Computers, the Web Part issues a query that returns and shows all items in the search index that are categorized as Computers. Similarly, when users browse to the category Audio, the same Web Part on the same category page will show items in the search index that are categorized as Audio.

若要影響查詢的撰寫方式,或是增加搜尋結果的相關性,您可以使用「結果來源」與「查詢規則」。如需詳細資訊,請參閱<在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能>中的<規劃結果來源與查詢規則>一節。To influence how the query is written, or to increase the relevance of search results, you can use result sources and query rules. For more information, see "Plan result sources and query rules" in Plan search for cross-site publishing sites in SharePoint Server 2016.

如需搜尋網頁組件的詳細資訊,請參閱<規劃 SharePoint Server 中供網站間發佈用的製作網站>中的<規劃將搜尋網頁組件新增至頁面>一節。For more information about Search Web Parts, see "Plan to add Search Web Parts to pages" in Plan publishing sites for cross-site publishing in SharePoint Server.

搜尋 SharePoint 跨網站發佈功能Search for SharePoint cross-site publishing

使用跨網站發佈功能時,您使用搜尋技術來擷取和顯示內容。搜尋索引是搜尋的核心。在發佈網站上不同搜尋網頁組件中指定的查詢,會傳送至搜尋索引來擷取相關的內容,並顯示在網頁組件中。When you use cross-site publishing, you use search technology to retrieve and show content. The search index is the center of search. The queries that are specified in the different Search Web Parts on the publishing site are sent to the search index to retrieve relevant content and show it in the Web Part.

本節說明如何新增和管理搜尋索引中的內容。This section explains how content is added to and managed in the search index.

了解如何在搜尋索引中新增和管理內容Understanding how content is added to and managed in the search index

若要將內容放入目錄的搜尋索引中,您必須先建立內容來源並開始進行完整編目。內容編目後,您必須管理搜尋索引中的內容中繼資料。To get content into the search index from catalogs, you must first create a content source and start a full crawl. After the content is crawled, you have to manage the content metadata in the search index.

內容來源與編目Content sources and crawling

若要建立搜尋索引,您必須先針對一或多個內容來源中指定的內容開始編目。「內容來源」是一組選項,可用於指定已編目的內容類型、所要編目的 URL,以及應要編目內容的頻率。內容來源可由Search Service 應用程式管理員在管理中心中設定和維護。如需詳細資訊,請參閱<在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能>中的<規劃結果來源與編目>一節。To build the search index, you must first start a full crawl of content that is specified in one or more content sources. A content source is a set of options that you can use to specify what type of content is crawled, what URLs to crawl, and how frequently the content should be crawled. Content sources are set up and maintained in Central Administration by a Search service application administrator. For more information, see "Plan content sources and crawling" in Plan search for cross-site publishing sites in SharePoint Server 2016.

搜尋索引中的內容中繼資料Content metadata in the search index

在內容編目後,所編目項目的中繼資料會以編目屬性表示。若要讓搜尋索引中包含編目屬性,請將編目屬應對應為 Managed 屬性。這是因為搜尋結果中只能包含 Managed 屬性。When content is crawled, the metadata of the items that are crawled are represented as crawled properties. To include crawled properties in the search index, crawled properties are mapped to managed properties. This is because only managed properties are included in search results.

為了避免必須手動為目錄將編目屬性對應為 Managed 屬性,SharePoint Server 會為所有網站欄自動建立 Managed 屬性。在目錄中,Managed 屬性是指文件庫或清單中項目的規格,例如作者、日期、文章類型、色彩或產品類別。如需詳細資訊,請參閱<在 SharePoint Server 中自動建立 managed 的屬性>。To avoid having to manually map crawled properties to managed properties for a catalog, SharePoint Server automatically creates managed properties for all site columns. In a catalog, managed properties are the specifications of the items in the library or list, such as Author, Date, Article Type, Color, or Product Category. For more information, see Automatically created managed properties in SharePoint Server.

您可以指定 Managed 屬性設定,來影響在搜尋網頁組件與在搜尋結果中顯示內容的方式。設定是以搜尋結構描述維護。如需 Managed 屬性設定的詳細資訊,請參閱<在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能> 中的<規劃管理搜尋索引中的 Managed 屬性>。You can specify settings for managed properties to affect how content is shown in Search Web Parts and in search results. The settings are maintained in the search schema. For more information about managed property settings, see "Plan to manage managed properties in the search index" in Plan search for cross-site publishing sites in SharePoint Server 2016.

結果來源與查詢規則Result sources and query rules

「結果來源」可在搜尋網頁組件用來縮小要顯示在網頁組件的搜尋結果範圍。在 SharePoint Server 2010 中,這類限制查詢稱為搜尋範圍。快速了解結果來源概念的方法之一,是將其當作可重複使用的查詢。您可以建立結果來源,指定要從要擷取搜尋結果的位置 (例如,目錄 URL),或是指定只能擷取特定項目類型的搜尋結果,例如圖片。Result sources are used in Search Web Parts to narrow the scope of search results that are shown in the Web Part. In SharePoint Server 2010, this kind of restricted query was called a search scope. One way to quickly understand the concept of a result source is to think of it as a reusable query. You can create result sources to specify a location from which search results can be retrieved — for example, the URL for a catalog, or to specify that search results can only be retrieved for a particular item type — for example, pictures.

「查詢規則」是一組條件,會以特定方式來改變查詢。看待查詢規則最簡單的方式,就是「如果發生 X,就執行 Y」。查詢規則適用來限制搜尋結果中顯示的內容類型,以及影響搜尋結果的顯示順序。設定查詢規則時,您可以指定會觸發查詢規則的「查詢條件」。例如,查詢條件可以指定查詢要符合字詞組中的特定字詞,或是查詢要符合特定搜尋字詞。此外,您要指定查詢規則觸發時,應對搜尋結果執行的動作。例如,在搜尋結果最上層顯示特定字詞的動作。假設您的內部網路網站在以目錄的形式共用的清單中,維護所有公司事件,而您想要推廣急救研討會。若要執行這項操作,您可以建立一個查詢規則,當有人搜尋「研討會」或「事件」時,就將急救研討會提升到搜尋結果最上層。A query rule is a set of conditions that cause the query to be changed in a specific way. An easy way to think of a query rule is to think, "if X happens, then do Y." Query rules are used to limit the type of content that can appear in search results, and to influence the order in which search results should appear. When you configure a query rule, you specify query conditions that cause the query rule to be triggered. For example, a query condition could specify that a query matches a specific term in a term set, or that a query matches a particular search term. Additionally, you specify the actions that should happen to the search results when the query rule is triggered. For example, an action could be to show a specific item at the top of the search results. Say you have an intranet site where all company events are maintained in a list that you have shared as a catalog, and you want to promote a first-aid seminar. To do this, you create a query rule that raises the first-aid seminar to the top of the search results when someone searches for "seminar" or "event."

您可以針對一或多個結果來源設定查詢規則,還可以指定一段可觸發查詢規則的時間。You can configure query rules for one or more result sources, and you can specify the time period during which the query rule is triggered.

如需結果來源與查詢結果的詳細資訊,請參閱<在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能>中的<規劃結果來源與查詢結果>一節。For more information about result sources and query rules, see "Plan result sources and query rules" in Plan search for cross-site publishing sites in SharePoint Server 2016.

精簡器與多面向導覽Refiners and faceted navigation

您可以將「精簡器」新增至頁面,幫助使用者迅速瀏覽到特定內容。精簡器是以搜尋索引中的 Managed 屬性為基礎。若要在頁面上顯示精簡器,您必須先啟用要作為精簡器使用的 Managed 屬性,然後將精簡搜尋面板網頁組件新增至要顯示精簡器的頁面。例如,在有知識庫文章目錄的內部網路網站案例中,您可以將 Managed 屬性 [作者] 新增為精簡器。精簡搜尋面板網頁組件將會列出所有知識庫文章作者。當使用者按一下特定作者名稱時,只會列出該作者撰寫的知識庫文章。You can add refiners to a page to help users quickly browse to specific content. Refiners are based on managed properties from the search index. To show refiners on a page, you must first enable the managed property that you want to use as a refiner, and then add a Refinement Panel Web Part to the page where you want the refiners to appear. For example, in an intranet scenario in which you have a catalog of knowledge base articles, you might add the managed property Author as a refiner. The Refinement Panel Web Part will list all authors of the knowledge base articles. When users click a specific author name, only knowledge base articles written by that author are listed.

SharePoint Server 具備「多面向導覽」功能,可透過與字詞組中的字詞關聯的精簡器篩選功能,幫助使用者更輕鬆地瀏覽內容。使用多面向導覽,您就可以針對字詞組中的不同字詞設定不同的精簡器,而不需要建立額外的頁面。例如,在顯示電子產品型錄的網際網路商業案例中,可以使用字詞組來將不同的產品分類,例如電腦或相機。兩個字詞都可以使用同一個類別頁面。在啟用 Managed 屬性 [螢幕大小] 與 [百萬像素] 作為精簡器之後,您可以設定多面向導覽,以讓 [螢幕大小] 顯示為電腦的精簡器,而將 [百萬像素] 顯示為相機的精簡器。這表示您不用建立額外的頁面,引導使用者前往特定類別的相關內容。SharePoint Server has faceted navigation to help users browse for content more easily by filtering on refiners that are tied to terms in a term set. By using faceted navigation, you can configure different refiners for different terms in a term set without having to create additional pages. For example, in an Internet business scenario in which a catalog of electronic products is shown, a term set might be used to categorize different products, such as computers or cameras. The same category page is used for both terms. After you enable the managed properties Screen size and Megapixels as refiners, you can configure faceted navigation so that Screen size is shown as a refiner for computers, and Megapixels is shown as a refiner for cameras. This means that you don't have to create additional pages to guide users to content that is relevant for a specific category.

如需詳細資訊,請參閱在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能中的<規劃精簡器與多面向導覽>。For more information, see "Plan refiners and faceted navigation" in Plan search for cross-site publishing sites in SharePoint Server 2016.

流量分析與建議Usage analytics and recommendations

SharePoint Server 中的流量分析功能會自動追蹤使用者如何檢視不同的項目。該項目可以是網站上顯示的文件、頁面或清單項目。每當使用者檢視項目時,系統就會發出「使用事件」,然後將該事件加入該項目的總計與近期的檢視計數。Usage analytics in SharePoint Server automatically tracks how different items are viewed by users. Items can be documents, pages, or list items that are shown on a site. Every time that a user views an item, the system issues a usage event and adds the event to the total and recent view counts for that item.

您可以使用流量分析資訊來設定網站上的「建議」。根據使用事件追蹤到使用者先前與網站互動的方式來顯示建議。建議功能可將使用者引導到可能和其檢視內容相關的其他內容。例如,您可以將使用者引導至類別中的常用項目,或是讓他們知道檢視此項目的使用者還檢視哪些其他項目。您可以新增建議項目網頁組件或是常用項目網頁組件,來將建議新增至頁面。You can use the usage analytics information to configure recommendations on your site. The recommendations that are shown are based on how users previously interacted with a site, tracked by the usage events. The recommendations feature can guide the users to other content that may be relevant for them, related to what they are viewing. For example, you can guide users to popular items in a category or let them know that users who viewed this item also viewed these other items. You add recommendations to a page by adding the Recommended Items Web Part or the Popular Items Web Part.

您也可以在流量報告中檢視使用事件的相關資料。You can also view data about usage events in usage reports.

如需詳細資訊,請參閱<SharePoint Server 的分析處理概觀>。For more information, see Overview of analytics processing in SharePoint Server.

如需建議的詳細資訊,請參閱<在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能>中的<規劃流量分析、使用事件及建議>一節。For more information about recommendations, see "Plan usage analytics, usage events and recommendations" in Plan search for cross-site publishing sites in SharePoint Server 2016.

SharePoint 跨網站發佈功能的限制Limitations of SharePoint cross-site publishing

下列清單包含 SharePoint Server 中跨網站發佈功能限制的相關資訊:The following list contains information about the limitations of the cross-site publishing feature in SharePoint Server.

  • 發佈網站集合中不會顯示尚未編製索引的內容Content is not shown in publishing site collections until it is indexed.

    製作網站集合中儲存的內容必須先編制索引後、才能提供給發佈網站集合。搜尋系統只會針對主要版本的項目編製索引。這表示如果您建立頁面內容,然後使用核准工作流程或內容排程,搜尋系統將不會對尚未核准發佈或未達排程之發佈日期的頁面內容編製索引,原因是該內容尚未標示為主要版本。此外,發佈網站上的導覽中將不會顯示與該內容關聯的字詞。在內容發佈後,發佈網站上的導覽中就會立即出現該字詞。不過,在將內容編目和編製索引之前,該內容將不會顯示在發佈網站上的結果中。Content stored in authoring site collections must be indexed before it will be made available to publishing site collections. The search system only indexes items that are major versions. This means that if you create Pages content and use the Approval workflow or content scheduling, the search system will not index Pages content that has not been approved for publishing, or that has not yet reached its scheduled publication date because it is not yet marked as a major version. In addition, the term associated with that content will not appear in the navigation on the publishing site. When the content is published, the term will be immediately available in the navigation on the publishing site. However, content does not appear in results on the publishing site until the content is crawled and indexed.

  • 字詞庫不支援版本設定。The term store does not support versioning.

    如果您太早在程序中將字詞新增至字詞庫,就會在任何相關內容備妥之前,在發佈網站集合上公開導覽字詞。對字詞所做的變更會立即生效,而且不會有字詞組的歷程記錄。因此,如果您變更字詞,將無法讓其回復為先前的值。If you add terms to the term store too early in the process, you can expose navigation terms on the publishing site collection before any related content is ready. Changes to terms are immediate, and there is no history for term sets. Therefore, if you change a term, you cannot revert it back to a previous value.

  • 清單沒有核准工作流程。There is no Approval workflow for lists.

    只有頁面庫才有核准工作流程。如果您將項目新增至以目錄形式共用的清單,就會在下次將目錄編目時,自動將該項目新增至搜尋索引中。建議您使用版本設定,或是不要將項目新增至以目錄形式共用的清單,直到您準備好要標記內容並在發佈網站集合上顯示為止。Only the Pages library has an Approval workflow. If you add an item to a list that is shared as a catalog, it will automatically get added to the search index the next time that the catalog is crawled. We recommend that you either use versioning, or do not add items to a list that is shared as a catalog until you are ready to tag content and have it appear on the publishing site collection.

  • 必須調整網站架構才能使用多語系網站的變化。Using variations for multilingual sites requires adjustments to the site architecture.

    在發佈解決方案中使用變化的方式,取決於您擁有的是頁面或清單內容,以及是否想在一或多個發佈網站集合上顯示內容。上述任一情況都需要針對您的解決方案來變更網站架構。如需詳細資訊,請參閱<規劃 SharePoint 2016 的變化>。How you use variations in your publishing solution will depend on whether you have Pages or list content, and whether you intend to show the content on one or more publishing site collections. Either case will require changes to the site architecture for your solution. For more information, see Plan for variations in SharePoint 2016.

另請參閱See also

概念Concepts

在 SharePoint Server 中發佈至網際網路、內部網路及外部網路網站的功能概觀Overview of publishing to Internet, intranet, and extranet sites in SharePoint Server

規劃 SharePoint Server 的網際網路、內部網路及外部網路發佈網站Plan for Internet, intranet, and extranet publishing sites in SharePoint Server

規劃 SharePoint Server 的跨網站發佈Plan for cross-site publishing in SharePoint Server

規劃 SharePoint Server 跨網站發佈的邏輯架構Plan the logical architecture for cross-site publishing in SharePoint Server

規劃 SharePoint Server 中跨網站發佈用的製作網站Plan authoring sites for cross-site publishing in SharePoint Server

規劃 SharePoint Server 中供網站間發佈用的製作網站Plan publishing sites for cross-site publishing in SharePoint Server

在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能Plan search for cross-site publishing sites in SharePoint Server 2016

在 SharePoint Server 中設定跨網站發佈Configure cross-site publishing in SharePoint Server

評估 Web Content Management 的容量和效能 (SharePoint Server 2013)Estimate capacity and performance for Web Content Management (SharePoint Server 2013)