Taxonomy in SharePoint 2010

Veena Sarda
Sep 18, 2012

34.5k
0
0
- facebook
- twitter
- linkedIn
- Reddit
- WhatsApp
- Email
- Print
- Other Artcile

Taxonomy in SharePoint 2010 is realized through Managed metadata services (MMS). MMS is a hierarchical collection of centrally managed terms that you can define, and then use as attributes for items in SharePoint 2010.

The structure of Managed metadata affects many parts of your SharePoint Server solution, such as the following:

Valid values for columns and the way users enter these values.
The enterprise keywords that users can apply to SharePoint Server 2010 items.
The way that search results can be refined.
How documents are routed.
The workflows that are applied to SharePoint Server items.
The ways that users can sort and filter SharePoint Server items.
If you are using social tagging, the tags that users can apply to items that are not SharePoint Server items.

Term Sets, Groups and Terms

Vocabulary can be built in SharePoint in the form of Term Sets and Terms, as in the following example:

Conference rooms (Group)

Auditoriums (Term Set)
- Auditorium C (Term) [Term Properties - Available for tagging, Language, Description, Default Label and Synonyms]
- Auditorium D
- Auditorium E
Halls
- Hall A
- Hall B
Second floor
- Room 256
- Room 257

Process of Building a Taxonomy

The following diagram depicts the process to build taxonomy:

Figure 1: Process to build taxonomy

You need to start by defining the subject area and listing the concepts. You will start with the broader level and then gradually lower the level of detail.
You can gather the metadata either from your relevant industry, internally from content in your organization, subject area experts, existing taxonomies etc. It may lead to certain overlap in term sets.
Next you need to organize these term sets using either a top down or bottom up approach. It will lead to gap identification.
Validate and then implement them.
A metadata governance board will keep check on the scope, timelines and validation of term sets.

Classification of data

Data is proprietary to the organization
May be based on LoBs
May be department based
May be function based
May be Regional
May be based on Products
May be Project based

The following diagram illustrates how various kinds of SharePoint-based solutions might require various approaches to taxonomy based on business need:

Figure 2: Taxonomy approaches based on business needs

Designing managed metadata services

An example of how to design the managed metadata services infrastructure is shown below:

Figure 3: Ex. of Designing managed metadata services

Global Term Sets - The corporate taxonomy is represented by global term sets in the term store that is associated with the corporate managed metadata service. The content type hub that is associated with the corporate managed metadata service makes shared content types available to users of all site collections.

Every Web application has a connection to the corporate managed metadata service. The connections from the My Site Web application, the team sites Web application, and the legal sites Web application, numbered 2, 3, and 4 in the figure, all have restricted access to the corporate managed metadata service. Restricted access lets users of the sites in these Web applications use the shared content types and global term sets, add new enterprise keywords, and create local term sets, but it prohibits them from modifying global term sets.

The administrative Web application hosts the site collection from which authorized users manage the corporate taxonomy and the shared content types. The site collection's content type gallery contains the shared content types, such as the updated document content type that reflects the additional required properties. This content type gallery is the content type hub of the corporate managed metadata service. The connection from the administrative Web application, numbered 1 in the figure, has full access to the corporate managed metadata service.

Local Term Sets are created within the context of a site collection, and are available for use (and visible) only to users of that site collection. For example, the term store that is associated with the legal department's managed metadata service contains term sets that represent confidential information that the legal department uses. Only the legal sites Web application has a connection to legal's managed metadata service, so that users of the site collections in the legal sites Web application can manage their term sets.

Permissions

Application Pool Level

The following table summarizes the permission that each managed metadata service grants to the accounts that the connections use to access the service. Note that a local farm is explicitly given reduced permission. If you do not remove or reduce the permissions for a local farm, other local accounts will connect to the services using the permissions that are specified for the local farm.

Figure 4: Ex. of Permissions at Application Pool Level

Group Level

Permissions can also be given at group level. Groups define security boundaries. A group is a set of term sets that all share common security requirements. Only users who are designated as Contributors to a specific group can manage term sets that belong to the group or create new term sets within it.

Capacity Planning for Term Store (database)

The following table lists the recommended guidelines for the organization of managed metadata in a Term Store:

You can create multiple managed metadata services, and share multiple term stores and content types from multiple site collections. However, each managed metadata service must specify a different term store. When you specify a nonexistent database for the term store, a new database is created.

Term Store Management Tool

SharePoint Server 2010 includes the Term Store Management Tool, which you use to create and manage term sets. If you have the appropriate permissions you can use the Term Store Management Tool to: