Skip to main content

Working with Managed Metadata in SharePoint 2010

I have started playing around with SharePoint 2010 Beta recently. One of the most attractive features of the new version is Managed Metadata. It allows people to maintain metadata across the site collections.

Here's the quick sample of how you can use managed metadata in SharePoint 2010.

Scenario
We have a list or library to store Customer Sales Orders. This list is located on several site collections. Our goal is to manage metadata for those lists centrally.
I have two site collections: wylde.slava.com and solutions.slava.com.

Step 1. Create a custom list called Customer Sales Orders on both site collections.

Step 2. Add a managed metadata column called Sales Order Status on solutions.slava.com:



Select "Customize your term set" option to create new term set called Sales Order Status. Then it appears in the list of available term sets to use anywhere else.

Select this custom term set.

Step 3. I have done the same for wylde.slava.com, but when I created a managed metadata column I have chosen the "Use a managed term set" option to select the one created previously.



Step 4. Adding items to the list. Hit New Item command and the form will appear:



I typed Order Submitted in the Sales Order Status box and when I tried to Save changes the error message appeared:



Then I clicked the button near the text box:



That brought up a dialog from where I could populate the list of available values:









Saved the new item:



Step 5. Add new item to the list on other site collection - wylde.slava.com. Metadata values managed on the other site collection is available here:





Good one.


UPD: Some additional functionality you can use when manage Managed Metadata described in the new article - Working with Managed Metadata in SharePoint 2010 - Term Set Management

Stay tuned for more articles from Wylde Solutions and if you have any questions regarding SharePoint 2010, migrating from MOSS 2007 or SharePoint Portal Server 2003 contact us now for a consultation.

Comments

Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w

InfoPath 2013 Preview - URL not valid error when publishing

In InfoPath 2010 there is a problem when you try to publish a Form to a SharePoint site that doesn't have root site collection. You will get an error message "The following url is not valid". It's described here:   http://support.microsoft.com/kb/981854 The solution is to create root site collection for the Web application. Same problem is with InfoPath 2013: In my situation I didn't create the root site collection initially, but used "/sites" managed path instead for all site collections. To solve the problem with InfoPath I had to create it. Used a new site template "Project Site". Will get a chance to research that too. :)  

Document Sets - SharePoint 2010 - Part 1

Hi again, in this post I am going to demonstrate how set up and start using Document Sets in SharePoint 2010. In Beta version there was a little problem when working with Document Sets. You could see the discussion around it here: Document Set content type issue . Now it is fixed and I will show you how to set up Document Sets properly to also use Keywords. 1. Activate two site collection features - Document Sets and Document ID Service: 2. Select a document library settings where you want to implement Document Sets. In my case it is Shared Documents. When you have selected the settings go to Advanced settings and then allow content types management: 3. Add an existing content type called Document Set: 4. Now I want to create a new Document Set. I have a sales opportunity and I have two documents related to this sales opportunity. So first I select New Document -> Document Set command, then provide name and description and there it is: 5. To check if our Document ID