My blog has moved!

My blog has moved to http://www.lamber.info. Click on the redirect button below to be redirected to the blog post.

Please update your bookmarks and use the new url for getting new updates.

Pages

Saturday, January 29, 2011

Assigning a managed term set to a custom column

In the last posts we created a managed metadata service application and a term store with sample data. Our term store was assigned to a web application that contains one site collection. In this post we are going to see how to use the data in your sample term store in a managed metadata column added to a SharePoint document library.

Overview

SharePoint 2010 uses the managed metadata service application to provide organization wide values for following scenarios:

  • Use enterprise keywords and tagging functionalities for your farm
  • Define a taxonomy and use it within metadata columns in a SharePoint list and library

In this post we are showing the last of two scenarios. Find more information on how to enable the enterprise keywords on this post. Finally, find here a TechNet article that introduces the social tagging features if you are interested in the first scenario.

Prerequisites

Before we are going to enable a metadata column we have to follow these prerequisites:

  • you are using at least SharePoint 2010 Standard
  • you already created a managed metadata service application and assigned it to the web application you are going to use

If you need help in setting up a managed metadata service application and create a taxonomy, then follow my previous posts.

Creating a managed metadata column on a list/library

In this demonstration I already created a new document library. This document library is going to be extended with a managed metadata column that contains the different departments in our organization (check the sample term store in my previous post). The aim of this customization is to associate a single document with a department. The steps that I followed are:

  • In the document library go to Library –> Create Column (you can access the columns also under Library –> Library Settings)

man02

  • the window Create Column pops up
  • Define as column name Department (the name of the column can be freely defined)
  • select as type Managed Metadata

man03

  • the Create column window refreshes and provides you the last settings below
  • Select Use a managed term set and select the Departments term set (alternatively you can use the Customize your term set option. This option permits you to manage your term set only for a single site collection. It is not shared to other site collections and not used in the enterprise keywords.)

man04

  • Press OK and you added your managed metadata column

Note: you can maintain the column afterwards by making your changes under Library –> Library Settings under library columns.

Finally, we only need to test our changes by uploading a test document. Press the upload button of the document library and choose a file. Afterwards, you should see the managed metadata column as document property displayed before finishing the upload.

man07

The managed metadata column provides you a selection button on the right side of the text box (the two small labels). You can either insert directly the term in the text box or choose from the selection button. If you do latter, a new window will pop up with the definition of the departments of our managed metadata service application.

man06

Summary

In this post you saw how to create a managed metadata custom column on a SharePoint document library. This metadata column uses the sample data of our managed metadata service application. This is the last post about the term set and managed metadata service applications. In the next and last post of this post series we are going to see the last feature of this service application… the content type hub.

 

Hope this helps,

Patrick

Wednesday, January 26, 2011

How do I manage my taxonomy in the term store management tool?

In this blog post of the post series about the managed metadata service application we are finishing our journey on the term store management tool and see what operations are available to maintain our taxonomy in the term store.

Overview

In our last post we saw how to setup a simple taxonomy with the term store management tool. Naturally, we cannot pretend that the initially defined taxonomy remains unchanged forever. Because of that, we need some operations on the different terms that help us to better manage the future changes and new scenarios that we are going to encounter. For the sake of our sample let us recap the taxonomy that we already used in our examples so far.

image

You can execute a set of operations on each single term in this taxonomy. You can see the list of operations when you click on the black arrow on the right side of the term (try to however over the term. If you still can’t see it than you probably do not have enough privileges to work with the term store. Check my last post for more information). You should see the operations listed in the next figure when you click on the black arrow:

man01

In the next sections we are going to describe the different operations and when to use them.

Operation: Create term

Use this operation if you want to create a new sub-term under the selected term. We already used it more than once in our last post to create the taxonomy.

If we take our example we used the create term operation under Information & Technology three times:

  • Administration
  • Quality Assurance
  • Software Development

Note: you can have a maximum number of 7 nested terms in your term set (check this TechNet article with information about this and other limitations in SharePoint 2010).

Operation: Copy Term

Use the copy term operation if you want to create a separate copy of a term in another location. If you make changes on the copied term, these changes are not reflected on the original term.

Operation: Reuse term

The reuse term is also used to make a copy of a term on a different location of the term set. On the other hand, every change that you are performing on the copy or the original term is applied automatically on both sides. Such an operation is useful if you have to classify a term in your term store for different locations and want to maintain only one copy of this term.

Operation: Merge term

Use the merge term operation if you want to merge a term and all its synonyms into another term. The source term and its synonyms are becoming synonyms for the target term.

This operation could be useful if you want to merge two departments into a single one.

Operation: Deprecate term

Terms flagged as deprecated cannot be used anymore by our end-users for tagging or metadata columns. The items that where already tagged remain unchanged. You can reactivate the term after deprecation if necessary.

Operation: Move term

The move operation is used to change the location of the term you want to move.

Operation: Delete term

Deleting a term removes it completely from the store. Please note that there is no recycle bin for the terms. All child terms of the deleted term are moved to a special folder called orphaned terms. All tagged items associated to the deleted term are marked as invalid when you try to modify them.

Summary

In this blog post we got a description of the different term store operations available to maintain our term store. Slowly we are coming to the end of our managed metadata service application blog post series.

 

Stay tuned,

Patrick

Saturday, January 22, 2011

SharePoint Server 2010 and Project Server 2010 update packages

The idea of this blog post is to document for my customers and for me the different updates (cumulative updates and service packs) that are available for SharePoint Foundation 2010, SharePoint Server 2010 and Project Server 2010. I’m going to update this blog post in future so just make a bookmark if you want to have the latest updates about this platform.

Note: follow this blog post if you want to know the steps to perform an update on SharePoint 2010 or Project Server 2010.

Outline

  • April 2011 cumulative update
  • February 2011 cumulative update
  • December 2010 cumulative update
  • October 2010 cumulative update
  • August 2010 cumulative update
  • June 2010 cumulative update

 

April 2011 Cumulative Update

Platform KB
SharePoint Foundation 2010 KB 2512804 Download
SharePoint Server 2010 KB 2512800 Download
SharePoint Server 2010 and Project Server 2010 KB 2512801 Download

 

Platform KB
Project 2010 Client Updates KB 2516479 Download

 

February 2011 Cumulative Update

Platform KB
SharePoint Foundation 2010 KB 2475880 Download
SharePoint Server 2010 KB 2475878 Download
SharePoint Server 2010 and Project Server 2010 KB 2475879 Download

 

Note: seems that the above KB links are not functioning properly. This might be a temporary issue.

Platform KB
Project 2010 Client Updates KB 2496946 Download

 

December 2010 cumulative update

Platform KB
SharePoint Foundation 2010 KB 2459125 Download
SharePoint Server 2010 KB 2459257 Download
SharePoint Server 2010 and Project Server 2010 KB 2459258 Download

 

Platform KB
Project 2010 Client Updates   No Update

 

October 2010 cumulative update

In the first release of the October 2010 cumulative update Microsoft discovered a critical issue. The cumulative update was removed by Microsoft after some days from the downloads. After some weeks they solved the issues and put a new cumulative update version for October 2010. You find these links below.

Platform KB
SharePoint Foundation 2010 KB 2394323 Download
SharePoint Server 2010 KB 2394320 Download
SharePoint Server 2010 and Project Server 2010 KB 2394322 Download

 

Platform KB
Project 2010 Client Updates KB 2413663 Download

 

August 2010 Cumulative Update

Platform KB
SharePoint Foundation 2010 KB 2266423 Download
SharePoint Server 2010 KB 2352342 Download
SharePoint Server 2010 and Project Server 2010 KB 2352345 Download

Platform KB
Project 2010 Client Updates   No Update

 

June 2010 Cumulative update

Please note that this cumulative update was not provided as a server package. Therefore follow the links and this post.

Platform KB
SharePoint Foundation 2010 KB 2028568 Download
SharePoint Server 2010   Check here
Project Server 2010 KB 2075990 Download

Platform KB
Project 2010 Client Updates KB 2075992 Download

 

Hope this helps,

Patrick

Creating the term store example with the term store management tool

This post continues the journey of our post series SharePoint 2010: exploring the managed metadata service application”. We are going to see how to work with the term store management tool and create the example term store that was shown in the last posts of this series. In the next posts we are going to see how to manage these terms and make taxonomy and folksonomy modifications.

Overview

This post guides you in creating a sample taxonomy with the term store management tool. The requirements for this post are a created managed metadata service application (see my post if you need help in doing this).

First of all, we are going to grant us the necessary permissions for working with the term store management tool. We are going to grant us the term store administrator role (see my post if you don’t know the available managed metadata roles). Second, we are able to create our taxonomy shown in the next figure in the term store management tool.

image

To sum up the steps are as follows:

  • Step 1: grant the term store administration permissions to a user
  • Step 2: create the taxonomy with the term store administrator

Step 1: grant the term store administration permissions to a user

The last post of this series described the different roles that are available for managing the term store with the term store management tool. One of these roles is the term store administrator. The term store administrator has the ability to manage the taxonomy and folksonomy in the term store. He is also responsible in setting up the contribute permissions to other users for the taxonomy we are going to create. Please note that the farm administrator is not automatically a term store administrator. However, the farm administrator has to define a term administrator if you want to manage the term store with the term store management tool.

With the next steps we are going to grant the term store administration permissions to a user of our choice. To do this login in as a farm administrator and follow these steps:

  • open the central admin
  • go to “Application Management” –> “Manage Service Applications”
  • go to the managed metadata service application that you want to edit and click on its name (in our case the “Demo Managed Metadata”)
  • you should see the term store management tool. You should find a section called “Term store Administrators” on the right side of the term store properties
  • add as many users you want and press “Save”

Step 2: create the taxonomy with the term store administrator

Now, we are able to create our taxonomy described above with the term store administrator permissions. The term store management tool can be found in the central administration under the managed metadata service application or on any site collection (under site settings) associated to a web application which is consuming the managed metadata service application.

As the term store administrator follow these steps to open the term store management tool:

  • open the central admin
  • go to “Application Management” –> “Manage Service Applications”
  • go to the managed metadata service application that you want to edit and click on its name (in our case the “Demo Managed Metadata”)

With the term store management tool open, we are going to create three different types of objects:

  • a term group: in our example “Organization”
  • a term set: in our example “Department”
  • a term: in our example “Information & Technology”

Creating a term group

We should see the term store management tool and on the top of the left navigation bar the “Demo Managed Metadata” entry. We are going to create the first node “Organization” of our example. This node is a a term group that is usually used to organize more sets of terms. The term group is used as a security boundary. You can specify following properties in a term group:

  • description: a short description about the group
  • group managers: group managers are responsible in changing the structure of the term sets that are contained in this group. In addition, they are able to grant contribute permissions in this group to other people
  • contributors: these are users that can contribute terms and term sets in this group

managed06

Let us create a new group by following these steps:

  • select the arrow with the left mouse button near to the “Demo Managed Metadata” (if you can’t see the arrow, then you are not a term store administrator)
  • Press “New Group”
  • assign to the new group entry the name “Organization”
  • assign "Group Managers” and “Contributors” if necessary

managed07

Creating a term set

In the previously created group we are going to create a term set. A group can contain multiple term sets. Term sets are used to contain one or more hierarchical terms. These term sets are selected in our site collections as source for the managed metadata columns.

The properties pane of the term set provides you with two separate tabs. The first tab “Properties” defines the properties that are following (also see next figure):

  • description: a short description about the term set
  • contact-email: used as contact address for suggestions on the managed metadata choice popup in the site collections that use managed metadata fields
  • stakeholders: stakeholders are only for documentation purposes and do not define any permission settings or automatic notifications. Usually you can use them to track the names of persons that should be contacted before any change is made on this term set.
  • submission policy: this defines if this term set can be modified solely by the people defined in the term set management tool or opened to everyone
  • available for tagging: this flag defines if the term set is available for tagging or not

managed01

In the “Custom Sort” tab of the term sets you are able to sort your term sets individually or maintain the custom sort order.

We are going to create a new term set “Departments” by following these steps:

  • select the arrow near to the “Organization” (if you can’t see the arrow, then you are not a term store administrator)
  • Press “New term set”

managed03

  • assign to the new term set entry the name “Departments”
  • assign the properties that you want

Creating a term

As already stated before, a term set is used to group more terms. Terms now are used to specify a single term instance. The properties that can be defined in a term set are:

  • available for tagging: this flag defines if the term set is available for tagging or not
  • description: a short description about the term
  • language: the current language for the name of the term and its synonyms. If you have multiple language packs installed you might be able to translate your term
  • other labels: these are the synonyms that can be used for your term. When a end-user inserts a synonyms associated to a term in the term store, then the system changes this synonym into the associated term (for example the term “Information & Technology” could have a synonym “IT”).
  • stakeholders: stakeholders are only for documentation purposes and do not define any permission settings or automatic notifications. Usually you can use them to track the names of persons that should be contacted before any change is made on this term set

managed05

We are going to create a term called “Information & Technology” by following the next steps:

  • select the arrow near to the “Departments” (if you can’t see the arrow, then you are not a term store administrator)
  • Press “New term”

managed04

  • assign to the new term set entry the name “Information & Technology”
  • under “other labels” assign the value IT
  • assign additional properties if you want

Repeat the last steps for the remaining terms ("Accountancy”, “Management”, etc.)and you are done.

Summary

In this blog post we created the sample taxonomy of our blog series. We saw the different types of objects available in a term store and which properties can be set. The next steps that we are going to follow in the next posts describe on how to manage the taxonomy in the term store management tool with some store operations that might become handy in some situations.

 

Hope this helps,
Patrick