Navigate Up
Sign In

Understanding Managed Metadata in SharePoint 2010: its Impact on Taxonomy, Navigation and Search - Part 2: Focusing on Content Organizer, Routing Rules, Content Types and Search

Item is currently unrated. Press SHIFT+ENTER to rate this item.1 star selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+ESCAPE to leave rating submit mode.2 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.3 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.4 stars selected. Press SHIFT+ENTER to submit. Press TAB to increase rating. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.5 stars selected. Press SHIFT+ENTER to submit. Press SHIFT+TAB to decrease rating. Press SHIFT+ESCAPE to leave rating submit mode.

You may also be interested in: SharePoint Fest Denver 2013

 

Note: We recently unearthed articles that were published on EndUserSharePoint's sister site EUSP2010 but were never migrated over to NothingButSharePoint. Over the next few weeks we'll be publishing these. The following article was originally published in June 2010.

Editor's note: Follow contributor Fabian Williams @fabianwilliams

Synopsis: Building on my previous post Understanding Managed Metadata in SharePoint 2010: its Impact on Taxonomy, Navigation and Search we discussed how Managed Metadata may be used to build out a Sites Taxonomy and Folksonomy, aid in Navigation and compliment or extend Search. In this post we will discuss the role of the Content Organizer, Routing Rules, and how Managed Metadata may be used in Content Types to dictate where a content final resting place may be.

In order to use Content Organizer it has to be Activated as a “Site Feature”; notice below in the Quick Launch that under ‘Libraries’ there is only one Document Library before the Feature is activated, “Documents”, however once activated in the second image, there is a new Document Library called “Drop Off Library”. The purpose of this library will be discussed further in this blog, for now lets just go step by step in creating and using it.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-01.png

Above: Content Organizer is a Site Feature so you have to activate it at a site level. Remember that when you think about scope and routing

2010-06-04-ManagedMetadataFocusOnContentOrganizer-02.png

Above: Once Activated you get the link above

In addition to the activate icon practically what you have are new items under the Site Administration menu in Site Settings. Before you activated “Content Organizer” you did not have options for (1) Content Organizer Settings or (2) Content Organizer Rules. In addition you also get a Document Library called “Drop Off Library” which is where all documents go that do not adhere to a defined rule.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-03.png

Above: Site Administration with Content Organizer Not Activated

2010-06-04-ManagedMetadataFocusOnContentOrganizer-04.png

Above: Site Administration with Content Organizer Activated

In Content Organizer Settings you have a few options as presented below. There are a few options here worth mentioning. Most notably is the option for Folder Partitioning; in previous versions of SharePoint folder use was de-emphasized because of the inability to tie meta-data to folders and the manageability aspects of maintaining and making visible what is inside a folder with little effort. Folder partitioning solves that by allowing you to create rules around how big a folder gets before you break it into two, or three, or four…

2010-06-04-ManagedMetadataFocusOnContentOrganizer-05.png

2010-06-04-ManagedMetadataFocusOnContentOrganizer-06.png

Above: Content Organizer Settings

In this example what I will do is build upon a pervious post where we discussed the use of Managed Metadata Understanding Managed Metadata in SharePoint 2010: its Impact on Taxonomy, Navigation and Search and we will use the Content Organizer to effectively route documents to an appropriate destination. In this example we will say that we have:

  • A Content Type based on our Managed Metadata
  • Use the Content Type to build a Content Organizer Rule
  • Route documents based on Content Type to the appropriate folder

2010-06-04-ManagedMetadataFocusOnContentOrganizer-07.png

Above: This is our Managed Metadata in our Term Store, we will focus on Exchange and SharePoint items/ work products

First we create a new Document Library called Projects and we will have Folders in there that are broken up based on Technology.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-08.png

Above: Document Library called Projects is created

2010-06-04-ManagedMetadataFocusOnContentOrganizer-09.png

Above: Folders for Exchange and SharePoint is created

Next we will create a rule for both Exchange and SharePoint as denoted below; we will also use the Managed Metadata as a means by which to route information see below…

2010-06-04-ManagedMetadataFocusOnContentOrganizer-10.png

Above: A Content Organizer Rule that send artifacts to the Exchange Folder based on the Managed Metadata of Exchange 2007 or Exchange 2010 selected.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-11.png

Above: A Content Organizer Rule that send artifacts to the SharePoint Folder based on the Managed Metadata of SharePoint 2003 or SharePoint 2007 selected.

Below you see the result of our rules as they are defined and notice I also made one a higher priority over the other.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-12.png

Above: Content Organizer Rules are defined

Next I will demonstrate two examples

  1. Uploading a document and applying the Managed Metadata as the document is persisted to the library
  2. Create a new document and use the DIP to apply the Managed Metadata to the new document

2010-06-04-ManagedMetadataFocusOnContentOrganizer-13.png

Above: Uploading a document to the Library Root; no folder specified

 2010-06-04-ManagedMetadataFocusOnContentOrganizer-14.png

Above: By clicking on the Tag Icon I can select or Multi-Select the appropriate fields

2010-06-04-ManagedMetadataFocusOnContentOrganizer-15.png

Above: Fields Selected

Next, we will create a new document from that library based on that Content Type (to which the Managed Metadata played a role), note in the DIP that we can select our options.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-16.png

Above: New Document created in the Document Library and the DIP is used to apply the relevant tagging

2010-06-04-ManagedMetadataFocusOnContentOrganizer-17.png

Above: Post Selection and apply a name to the new file

2010-06-04-ManagedMetadataFocusOnContentOrganizer-18.png

Above: Name applied to the new file and persisted to the SharePoint System

Note here that based on the fact that I selected a Managed Metadata that is flagged in a rule, the Document is persisted however it is saved to an alternate location based on the rules in the Content Organizer. Again, the WIN here is how you can create a Taxonomy and/or Folksonomy that can not only drive Structure, Navigation, Search, but can also provide intelligence in-terms of location.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-19.png

Above: The Final Destination is not where the intent of the end user is, rather, it is based on rules.

An examination of the folder [by clicking on the link or using the quick launch bar] shows that the document is routed by a rule.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-20.png

Above: Final resting place for this Status Report is in the Exchange Folder because of the hit on the Managed Metadata during content creation / uploading.

2010-06-04-ManagedMetadataFocusOnContentOrganizer-21.png

Above: Using the Managed Metadata Navigation feature in SharePoint you can also navigate, filter, based on the now MILLIONS UPON MILLIONS of rows that can be placed in a list.

Conclusion

The takeaway here is that Content Organizer is huge, and it builds upon other feature sets in SharePoint 2010 to make the overall experience very clean, simple, and results driven.

Comments and Critiques are welcomed. Spread the word.

Categories: Managed Metadata Service; Content Types; Search and Indexing; Taxonomy; SharePoint; MOSS; WSS; 2010

Comments

Chandramohan

Managed metadata and migrating list items with Export/Import

Hi Fabian, I am currently working on migrating list items from one doc. library to a different doc. library (which would be dynamically determined based on some metadata for each list item). I went through Stefan Gobner's 6 part article series from 2007 on using SPExport/SPImport for migrating SPListItems (http://blogs.technet.com/b/stefan_gossner/archive/2007/08/30/deep-dive-into-the-sharepoint-content-deployment-and-migration-api-part-1.aspx) and it greatly helped me. I'm now really stuck with an issue :( If you can help with any answers, please do read on: The issue is that in all of the destination document libraries, some fields are managed metadata fields and some seem to be normal/traditional fields (single line of text, multiple lines of text, etc), while in the source doc. library, all the fields are normal/traditional metadata fields. Due to this, upon migration, duplicate fields are getting created in the destination document library and also information is not updated for the managed metadata fields in destination doc. library. I'm new to this concept of managed metadata and not sure how to resolve this. 1. Should I convert the destination fields as normal/traditional fields OR 2. Should I convert all the fields in both source and destination to managed metadata fields (if so, how to initially upload document into source doc. library with information updated into managed metadata fields and how to migrate without problems) OR 3. Is there a way to flawlessly still migrate data with the existing setup and not create duplicates and also update information in all the destination fields. Please let me know if you have any quick answers. I would really be grateful for any insights shared. Regards, Chandramohan S

Posted 22-Feb-2013 by Chandramohan

Notify me of comments to this article

E-mail:
   

Add Comment

Title:

 
Comment:
Email:

   


Name:

 
Url: