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 wou…

SharePoint 2010 Search Issue - FQDN Crawl

I have recently set up a standalone SharePoint 2010 environment.

The Web application was created with host header and the site collection is accessible from the client machines, but not internally. That was because of using FQDN to access the Web site.

The error when I tried to access site internally was similar to the one described here:

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version

And the search returned the following error in the Event Log:

"The start address cannot be crawled.

Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

Details: This item could not be crawled because the crawler could not connect to the repository."

One of the suggestions was to disable the loopback check, but that would compromise the Web server.

So what I have done was:

1. Added a binding to my IIS Web site for a different port. Let's say my Web server name is win-v7m…

SharePoint 2013 - Setting Up External Content Type

There were earlier posts where we discussed External Content Types setup for SharePoint 2010:

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

External Content Types - Reload - Setting up for SQL Server database using SQL Server authentication - SharePoint 2010 Server

This one is about creating connection to the custom SQL Server database (External System) in SharePoint 2013.

1. Create Secure Store Service Target Application

1.1. Go to Central Administration -> Manage Service Applications -> Secure Store Service Application. Click "Generate New Key" if required:


1.2. Provide Pass Phrase:

1.3. Create "New" to create new Target Application:


1.4. Provide the name and other parameters and click "Next":

Note: It's good idea to specify "Group" for Target Application Type. In that case you would be able to manage access to the external data using Active Directory groups rather …