The User Profile Service Application 479 Synchronization Timer Job Once synchronization connections have been set up, you will need to configure a schedule for when this synchronization is to take place. An import should be performed at a frequency that matches how often the data source content changes. In the User Profile Service Application, click Configure Synchronization Timer Job. Use this screen to set the timer job to run on a recurring schedule accord- ing to minutes, hours, days, weeks, or months. In addition, you can start the synchronization immedi- ately by clicking the Run Now button. Synchronization Settings In the User Profile Service Application, click Configure Synchronization Settings. This page enables you to change more specific configuration settings regarding the data synchronization connections that have been created. Several options are available, such as whether to import only Users, or Users and Groups. Organizations The concept of organizations in the User Profile Service Application is similar to the user profiles, the difference being that user properties are related to individual people, and organization properties are related to entire organizations. Organization sub-types can be used to more granularly categorize multiple organizations, such as by a company’s major divisions or subsidiaries. On the main User Profile Service Application screen, there is an area called Organizations that contains links to Manage Organization Properties, Manage Organization Profiles, or Manage Organization Sub-types. A multinational company with different subsidiary companies is one example of how this feature might be used. The company could use these Organizations in order to specify different information about the subsidiary. Some users can actually have multiple profiles, one for each of different subsidiaries that they may work with. Audiences SharePoint audiences, which are used to target content to specific sets of users, can be quite powerful when used to their full extent. Audiences are defined here in the User Profile Service Application, and can be used in many ways in sites and lists to display information relevant to specific users. Audiences are not a security setting, but are simply used to display pertinent information to certain people. Before creating audiences, it is important to plan audience use. Audiences cannot be used to their full advantage unless the user data is accurate in the user profiles and properties. Whether this information comes from Active Directory or another line of business directory services such as PeopleSoft, cor- rect and consistent profile data is imperative. Once this profile data is accurate and useful, you should understand how to use audiences before going through the process of defining them. The following is a list of places in SharePoint 2010 where audiences are applicable: List items displayed in a Content Query Web Part Personalization Site links and Publish links to Office client applications Web Parts 480 CHAPTER 17 social comPUtiNg aNd sharePoiNt 2010 Web Part pages Navigation links Setting Up an Audience Follow these steps in order to set up audiences in the User Profile Service Application: 1. In the People section, click Manage Audiences. 2. Click the New Audience button. The screen shown in Figure 17-6 will appear. FIGURE 176 3. Give the audience a Name and Description. 4. Define the audience owner. 5. Multiple rules can be defined, so specify whether all or any of the rules need to be satisfied in order for a user to be included in the audience. Click OK. 6. Using the screen shown in Figure 17-7, set up a rule that defines the audience. 7. Create a rule based on either the User or Property Operand. Click OK. FIGURE 177 The User Profile Service Application 481 Audience Targeting Rules and Logic This section uses some examples to describe the rules for audience targeting and the logic behind them. For the first example, suppose you want to make sure that new employees see Web Parts and content relevant to those new to the company, such as forms to fill out and orientation announcements to read. You could create an audience called “New Hires.” The rule that defines it can be as follows: Property of Hire Date >= 1/1/2010 This rule could be changed once per year to include everyone hired in the past year as new hires. The second example uses an audience called Marketing, with three possible ways to define this group of people: Define an audience according to a group of people who report to the same manager. This option is useful as long as the Manager property is accurate in the user profiles. The down- side to this option is handling employee attrition. Because this rule is based on an individual person, when that person leaves the company, this audience must be redefined to include the new marketing manager’s name. The rules for this example would be: Operand — User Operator — Reports under Value — Select the name of the manager of the marketing department. Define an audience based on group membership. Any security-based distribution list in Active Directory can be selected as the basis for an audience. In this example, we have already created a group called Marketing, which contains all of the members of the marketing department. The rules for this example would be: Operand — User Operator — Member of Value — The name of the group, in this case “Marketing” Define an audience based on information in user profile properties. In this example, the Department property contains the word “Marketing.” The rules for this example would be: Operand — Property Operator — Contains Value — Marketing Given the different rules that might define the marketing department in the company, think about how restrictive the audience definition should be. In Figure 17-7, under the Audience settings, you could include users who satisfy all of the rules if each person must report to the specific marketing manager and have membership in the Marketing group in Active Directory and have “Marketing” as part of their department name. Alternately, you could choose to include users who satisfy any of the rules, if at least one of these criteria needs to be met. The second option allows for a broader audience, of course. 482 CHAPTER 17 social comPUtiNg aNd sharePoiNt 2010 Audience Compilation The list of audience members can be compiled on a schedule. This compilation entails a scan of changes in the user profi les, and changing the audience member list accordingly. For example, if a user was not in the marketing department during the last compilation, then the new compilation will recognize the changes to the user’s profi le, and add them as a member of the audience automati- cally. All audiences are compiled on the same schedule. Follow these steps to set up an audience compilation schedule in the User Profi le Service Application: 1. In the People section, click Schedule Audience Compilation. 2. Check the box to Enable Scheduling. 3. Confi gure settings for daily, weekly, or monthly compilation. Click OK. At any point, a manual compilation of all audiences can be started by clicking Compile Audiences in the People section. Any individual audience can be manually compiled from that audience’s properties screen by clicking Compile audience. Targeting Content to Audiences We create audiences in SharePoint, so that some content can be targeted to be seen by certain people. It is a good idea to fi rst determine where audiences will need to be used, before going through the process of creating them. Several bullet points on this page note that audiences do not need to be created at the Central Administration level in order to target content. In some cases, the audience settings allow for the selection of already existing SharePoint or Active Directory Groups. This section describes several targeting methods, along with instructions to carry them out. List Items displayed in a Content Query Web Part — In the settings for any list or library, click Audience targeting settings, and check the box to Enable audience targeting. There will be a new fi eld in the list, called Target Audiences. Set target audiences on individual items in the list, from the Edit Properties page. The way that the audience targeting is made appli- cable is to display the list in a Content Query Web Part on a Web Part page on a site in the same site collection. In the Web Part’s tool pane settings, note two checkboxes: In the Query section, there is an Audience Targeting area. Once the setting to Apply audience fi ltering is selected, you can optionally choose to include items that are not targeted. Pick from audi- ences, distribution lists, or SharePoint groups for targeting. This means that if an audience for a Content Query Web Part simply needs to be an Active Directory or SharePoint group, then it is not necessary to defi ne this audience in the User Profi le Service Application. Personalization Site Links and Publish Links to Offi ce Client Applications — In the My Site Settings section of the User Profi le Service Application, the Personalization Site Links and The User Profile Service Application 483 the Publish Links to Office Client application options both allow for content to be audience targeted. Read more about these features in the “My Sites” section of this chapter. Web Parts — Any Web Part can be targeted to an audience. In the Web Part’s properties tool pane, expand the Advanced section, which contains a Target Audiences field at the bottom. Pick from audiences, distribution lists, or SharePoint groups for targeting. This means that if an audience for a Web Part simply needs to be an Active Directory or SharePoint group, then it is not necessary to define this audience in the User Profile Service Application. Web Part Pages — In SharePoint publishing sites, there is a library called Pages. Click to Edit Properties of any individual page in the library, to see the field called Target Audiences. Pages that have been targeted to audiences will be displayed only to that audience, within the site’s navigation. Pick from audiences, distribution lists, or SharePoint groups for targeting. This means that if an audience for a Web Part page simply needs to be an Active Directory or SharePoint group, then it is not necessary to define this audience in the User Profile Service Application. Navigation Links — Within the navigational structure of the site, individual links may be targeted to audiences. On a SharePoint Server 2010 site, click Site ActionsSite Settings. In the Look and Feel section, click Navigation. Click a link in the navigation, and then click the Edit button. (Some items are not editable because they are part of the built-in site structure.) This screen is displayed in Figure 17-8. Type an audience name and click OK. Pick from audiences, distribution lists, or SharePoint groups for targeting. This means that if an audience for a link simply needs to be an Active Directory or SharePoint group, it is not necessary to define this audience in the User Profile Service Application. FIGURE 178 Trusted My Site Hosted Locations — In larger SharePoint deployments with geographically distributed User Profile Service Applications, administrators manage a list of Trusted My Site host locations, which can be targeted to audiences. These different locations can exist as mul- tiple web applications in a farm. This setting is found in the My Sites section of the application. 484 CHAPTER 17 social comPUtiNg aNd sharePoiNt 2010 Remember that audiences are not a method of controlling security. Items that are not targeted to specifi c users are not inaccessible to those users. Navigation in SharePoint will automatically be security trimmed, which means that users who don’t have access to a list, library, or site, will not see that link in navigation. When it comes to navigation, audience targeting is most useful with links that have been manually added, such as links to external websites, or links to other site collections. TAGS AND NOTES Interfaces for social interactivity and feedback on content are pervasive throughout SharePoint 2010. Users are encouraged to tag items everywhere in the environment, which makes their expe- rience more interactive and collaborative. This section explains the tagging and notes interface, including steps for tagging and making notes. First, take a look at the top-right corner of any site in SharePoint 2010 to see the I Like It and Tags & Notes buttons, shown in Figure 17-9. These icons will become very familiar, as they appear pretty much everywhere in SharePoint 2010. ACTIVITY FEED TIMER JOB By default, SharePoint does not automatically compile the activity feed, which is the list of user activities like tags and notes. There is a server timer job that needs to be enabled fi rst. In Central Administration, click Monitoring in the quick launch. In the list of timer jobs, click the User Profi le Service Application Activity Feed Job, and click the Enable button. Tagging In SharePoint Server 2010 discussions, you hear a lot about metadata and social tags. Tags are basi- cally keywords, or data about data. To tag something is to assign keywords to it, separated by semico- lons, and these keywords can be associated with anything. End users are able to “tag,” which not only adds a level of rich interactivity, but enables participation in the SharePoint community in the organi- zation. The I Like It button, next to Tags & Notes, enables users to quickly identify content that they like. These tags can also be managed, and even structured, from within Central Administration and at other levels. Read Chapter 16 for a thorough understanding of this managed metadata. Here is a list of some objects that can be tagged in SharePoint 2010: Pages Libraries FIGURE 179 . places in SharePoint 2010 where audiences are applicable: List items displayed in a Content Query Web Part Personalization Site links and Publish links to Office client applications Web Parts 480. site in SharePoint 2010 to see the I Like It and Tags & Notes buttons, shown in Figure 17-9. These icons will become very familiar, as they appear pretty much everywhere in SharePoint 2010. ACTIVITY. appli- cable is to display the list in a Content Query Web Part on a Web Part page on a site in the same site collection. In the Web Part s tool pane settings, note two checkboxes: In the Query