Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 40 potx

MCT USE ONLY. STUDENT USE PROHIBITED
Planning Social Computing 8-9
Privacy Considerations

Key Points
Privacy is a key planning point for organizations that intend to deploy social
computing features. Users may have concerns that their personal data will be
shared outside the organization or shared with inappropriate groups in the
organization. SharePoint 2010 provides tools to help maintain the privacy of
information in your social computing environment.
Your approach to social computing must balance the availability of personal
information and privacy. SharePoint 2010 provides personal and enterprise-level
security settings that govern access to and visibility of data. Site owners, including
My Site owners, can perform the following tasks:
• Grant permissions for readers, editors, and content managers.
• Grant or revoke access to sites individually or by group or organizational role.
• Open and close comment threads.
• Enable or disable content ratings.
• Make only certain content viewable.
MCT USE ONLY. STUDENT USE PROHIBITED
8-10 Designing a Microsoft® SharePoint® 2010 Infrastructure
• Enact other fine-grained controls to ensure that information does not spread
further than policy permits.

In terms of content, individuals must determine what they feel is appropriate to
share and what is not. You can help them by providing firm guidelines that apply
to the nature of the content that they post. Enforcing these guidelines is a matter of
management, education, and training—not technology.
The information in the user profile that is displayed on the user’s My Site Web site
is accessible to search services. It is also exposed in tags, notes, ratings, and the
user’s activity feed. Your social computing plan should include how to assess the

requirement for privacy and how to protect information. You should use
SharePoint policies, which help you to maintain the privacy of information that you
store in the user profile.

MCT USE ONLY. STUDENT USE PROHIBITED
Planning Social Computing 8-11
Planning for Collaboration

Key Points
Collaboration sites store information that individuals and groups can collectively
author, share, and modify. Collaboration sites may be associated with a particular
portal site collection or part of a publishing collection. However, they can also be
stand-alone sites for specific projects, teams, or events. For example, you can create
a collaboration site for members of a project team to share information, schedule
meetings, and discuss the status of the project without publishing this information
to the corporate intranet.
Planning the Number of Collaboration Sites
You can create collaboration sites for your users, or you can allow the users to
create collaboration sites themselves.
If you choose to restrict the number of people in the organization who can create
collaboration sites, you can control the number of sites and plan for their storage
and maintenance.
If you choose to allow users to create collaboration sites themselves, you should
plan for monitoring of the size, location, and activity levels of each site.
MCT USE ONLY. STUDENT USE PROHIBITED
8-12 Designing a Microsoft® SharePoint® 2010 Infrastructure
You should estimate how many collaboration sites to expect in your environment
and decide how many of these sites you are willing to support.
Planning the Location of Collaboration Sites
When you plan the location of your collaboration sites, consider hosting them

either on a separate Web application or in separate content databases in the same
Web application as your portal or publishing site. This will give you more
flexibility for data backup and maintenance. It will also give you easier recovery.
Planning Paths for Collaboration Sites
You can use specific paths to contain site collections, similar to the way in which
folders contain files or documents in the file system. When you create a Web
application, two paths are made available for you:
• Root path (/). The root path contains only one site collection. For example, if
you want a URL to appear as http://company_name/default.aspx, you create
the site collection at this root path.
• Sites path (/sites). The /sites path can contain many site collections. For
example, when you use the /sites path, the URL for a site named Site_A would
be similar to http://server_name/sites/Site_A/default.aspx.

You can also create additional paths, which enable you to group site collections. By
defining managed paths, you can specify which paths in the URL namespace of a
Web application are used for site collections. You can specify that one or more site
collections exists at a specified path. This can be a convenient method of
consolidating multiple site access for users in various departments.
You can use an explicitly named path (for example, http://server/sites/team) for a
single site collection. A wildcard path of "sites" (for example, http://server/sites/)
indicates that child URLs of the path are site collections.
This means that when you create a site collection, you have the following options:
• You can create the site collection at the root of the Web application.
• You can create the site collection under the /sites path.
• You can create the site collection under any additional paths that you have
created for that Web application.


MCT USE ONLY. STUDENT USE PROHIBITED

Planning Social Computing 8-13
When you plan how to group collaboration sites, consider the following:
• For a complex infrastructure with many site collections, you can group similar
sites together. For example, you can use /personal for individual user sites and
/team for group collaboration sites, instead of using /sites for all.
• For an infrastructure that has external access to sites, you can add a filter to
your firewall or router to constrain a specific namespace to internal access
only. For example, you can expose the /team path but not the /personal path
for external collaboration.


MCT USE ONLY. STUDENT USE PROHIBITED
8-14 Designing a Microsoft® SharePoint® 2010 Infrastructure
Lesson 2
Planning for Social Computing Functionality in
SharePoint 2010

To create a plan for social computing in your organization, you must identify the
social computing functionality that will meet the business requirements. You must
be able to describe the key features of social computing, including My Site Web
sites, social tagging, wikis, and blogs. You must be able to identify who will use
these features and plan how to deploy and manage them. This will support the
goal of enabling your users to locate people and expertise quickly.
Objectives
After completing this lesson, you will be able to:
• Map business requirements to social computing functionality.
• Describe My Site Web sites.
• Plan My Site Web sites.
• Describe social tagging.
MCT USE ONLY. STUDENT USE PROHIBITED

Planning Social Computing 8-15
• Plan social tagging.
• Plan wikis.
• Plan blogs.
• Describe how to locate people and expertise.


MCT USE ONLY. STUDENT USE PROHIBITED
8-16 Designing a Microsoft® SharePoint® 2010 Infrastructure
Mapping Business Requirements to Social Computing
Functionality

Key Points
When you plan for social computing, you must review the business requirements
and determine which features you will deploy.
User Profiles
User profiles provide social computing features such as My Site Web sites and
profile information. User profiles also expose user information to search services.
Locating people and expertise is key in making knowledge available in the
organization, which is a major driver for deploying social computing. When you
plan user profiles, consider the following questions:
• Which profile properties are likely to be searched on?
• Which profile properties can you synchronize from directory services or
business systems?
• Which synchronized profile properties will map to default properties?
MCT USE ONLY. STUDENT USE PROHIBITED
Planning Social Computing 8-17
• If the required profile property does not map to a default property, will you
create an additional property for it?
• Which properties should be available to the Search Service?

• Which user profile properties should be visible on the user’s My Site Web site?

My Site Web Sites
My Site Web sites are used in organizations that want to provide users with a
personal space.
When you plan My Site Web sites, consider the following questions:
• Does each user require a personal, customizable Web site?
• Should users be able to customize their My Site Web sites?
• Should users be able to view other users’ profiles?
• Should users be able to edit their own profile information?

Social Tagging
Social Tagging is a subset of Social Feedback. Business requirements that indicate
the use of social tagging are primarily related to search. If your organization places
a high value on users being able to locate people and expertise quickly, you should
enable social tagging.
When you plan social tagging, consider the following questions:
• Will you use social tagging?
• Should all users be able to add social tags?

Wikis
Wikis provide a central location for content to be published, commented on, and
amended. When you plan wikis, consider the following questions:
• Is there a requirement for a central information store that could be
implemented by using a wiki?
• Should all users be able to edit all wikis?
• Do you require media-rich wikis?

MCT USE ONLY. STUDENT USE PROHIBITED
8-18 Designing a Microsoft® SharePoint® 2010 Infrastructure

Blogs
Blogs provide a location for a user or group of users to publish information. Other
users may comment on this information but not amend it. When you plan blogs,
consider the following questions:
• Should all users be able to create their own blogs?
• Should all users be able to comment on all blogs?
• Do you require media-rich blogs?