Managed Metadata Services ❘ 459 Column-Specific Term Sets When creating a managed metadata site column, you can choose the option “Customize your term set” to create a column-specific term set. This term set will be created and stored in the service application that is configured as the default storage location; however, it will only be available for use in this specific location. This implies that if it is created at the list level, it can only be referenced in that specific column within the list; and if it is created at the site level, it can only be referenced within that site. If it is created as part of a content type that is published, it would be available wher- ever that content type is available, thereby facilitating enterprise manageability to that term set. Key Usability Features Managed Metadata columns provide several key usability features that will help define the end user experience. These rich features provide a clear and easy way to create, manage, and maintain global tagging structures. These features enable users to easily use, define, and communicate suggestions for existing structures. All the commands are located within the user interface, so users will not have to leave the entry screen to take advantage of these various features. Type Ahead When a user is entering the value for a field by directly typing the value into the text field, the field will identify what is being typed and provide selections based on the values being entered. For exam- ple, as a user types the value “Nor” into the text field, the field control will offer the selections of “North,” “Northeast,” and “Northwest.” A user can then select from among these options, without having to type the complete value. Values for synonyms are also identified; for example, if the user enters “N,” the field control would recognize the value as a synonym for the value “Northeast.” For fields that are part of open term sets, any previously typed values are displayed for the user. This valuable feature enables users to quickly zero in on previously created entries. Figure 16-16 demon- strates this feature. FIGURE 1616 460 ❘ CHAPTER 16 maNaged metadata service aPPlicatioNs Browsing for Valid Options Instead of manually typing the desired value, users can select the Browse icon located to the right of the field control. This option enables users to browse the tree structure of the values and select the desired value. If users don’t see the desired value, they can suggest a new value or create a new value, if the term set allows. Users can drill down multiple levels within the tree view to select their desired value. Figure 16-17 illustrates the Browse feature. FIGURE 1617 Oce UI From within the Office applications, the SharePoint document properties can be accessed in several ways. Two specific ways are through the Document Information Panel and the Advanced Properties screen. Each of these options integrates with the user interface features described above. This inte- gration enables users to become familiar with adding content in a way that can be utilized across multiple applications. Having access to the suggestions and tree view within the Office application greatly increases the usability of managed metadata services across the organization. Figures 16-18 and 16-19 show examples of entering metadata from Excel. Managed Metadata Services ❘ 461 FIGURE 1618 FIGURE 1619 Metadata Navigation Another new feature in SharePoint 2010 is the capability to create dynamic filters based on meta- data. These new filters are referred to as Metadata Navigation and can be configured from the List Settings page. From the List Settings page you can configure Navigation Hierarchies and Navigation Filters. Hierarchies display in a tree view below the Quick Launch and enable you to drill down to filter through the various list metadata. Navigation Filters enable you to enter a specific value from the tree for filtering. Figure 16-20 shows a filter for the city of New Orleans. 462 ❘ CHAPTER 16 maNaged metadata service aPPlicatioNs FIGURE 1620 In addition to these navigation options, the filter can also be configured through the column drop- down menu. From this menu you can select which node of the tree to filter on and to include or exclude the descendants from the list. Note that if the column is configured to be part of the Key Filters, then filtering from the column drop-down is not enabled. Figure 16-21 shows the col- umn filtering options. Metadata-driven, filter-based navigation is a logical and helpful addition to SharePoint 2010. Before this version of SharePoint, this type of navigation was only possible through localized customization of a SharePoint list. FIGURE 1621 Content Types ❘ 463 CONTENT TYPES Content types are a powerful feature within SharePoint that provide a single point of management of common document or list types. Content Types were introduced with SharePoint 2007 and could be used within any single site collection. If you needed to use content types across multiple site col- lections, the content types had to be deployed and managed at each of the site collections. This restriction made the use of global content types difficult in many organizations. With the release of SharePoint 2010, many of these restrictions have been removed. Within managed metadata services, along with the Enterprise Term Stores, SharePoint administrators can configure a Content Type hub. This Content Type hub will be responsible for managing content types that can be published to all site collections that are consuming the services provided in the managed metadata service. Keep in mind that a single site collection can consume multiple managed metadata services. The Content Type hub is configured once for each managed metadata service. Any site collection to which the Service Owner has access can be configured to be the site collection hub. Figure 16-22 shows the Managed Metadata Service configuration screen with the option for selecting the Content Type hub to be associated with the specific managed metadata service. Content Type hub configura- tion settings can be found in the Managed Metadata Service properties page. FIGURE 1622 When selecting the Content Type hub, you also have an option to report any syndication errors. This is important because it provides detailed information about specific content that is not cor- rectly deployed to all consuming site collections. When a site collection is configured as a Content Type hub, the Content Type Syndication Hub feature is automatically activated, enabling the neces- sary features to become available for the site collection to publish content types. 464 ❘ CHAPTER 16 maNaged metadata service aPPlicatioNs Additionally, several new options become available on the Site Settings page and the Content Type settings page. These new options control the ability to publish content types and review specific errors from the publishing process. Content type publishing is controlled by two different timer jobs, the Content Type Hub and the Content Type Subscriber. The Content Type Hub timer job manages the maintenance logs and the unpublished content types. When this timer job is run, content types that have been identified to be published are made available to the Content Type Subscriber timer job. The Content Type Subscriber job is created for each of the web applications and is responsible for retrieving published content types and making them available in the local content type galleries for the subscribed site collections. The timer jobs are run on a default schedule, but you can update the schedule to match your organization’s needs. Figure 16-23 shows the different timer jobs; notice that there is one global Content Type Hub timer job but a Content Type Subscriber job is created for each web application. FIGURE 1623 Content Types ❘ 465 Creating and Publishing Content Types Once the Content Type hub has been created, users who have access to the hub can create and man- age the content types that will be published to the subscribing sites. The creation of the published content type follows the same creation process for nonpublished content types. The difference is that when a user is working within a site that has been created as a Content Type hub, additional con- figuration options are available in the Content Type management screen. The additional options are shown in Figure 16-24 and explained in detail in the following sections below. FIGURE 1624 Publishing, Unpublishing, and Republishing Content Types Once a content type has been created in the Content Type Gallery on the hub site collection, it can be published to the subscribing site collections. The Content Type Publishing dialog, shown in Figure 16-25, allows you to Publish, Unpublish, or Republish a content type. Notice that it also dis- plays the timestamp for the last successful publication. . to SharePoint 2010. Before this version of SharePoint, this type of navigation was only possible through localized customization of a SharePoint list. FIGURE 1621 Content Types ❘ 463 CONTENT. organizations. With the release of SharePoint 2010, many of these restrictions have been removed. Within managed metadata services, along with the Enterprise Term Stores, SharePoint administrators can. types are a powerful feature within SharePoint that provide a single point of management of common document or list types. Content Types were introduced with SharePoint 2007 and could be used