I'm sitting here in a session at SharePoint Saturday Austin on Managed Metadata in SharePoint 2010, with Stephanie Donahue and Stacy Deere. Great, super stuff. We had been talking about 2013 metadata and catalogs on the way in, and Stephanie offered to refer any questions on what's new in 2013 to my blog post on catalogs.
University of Texas Clock Tower, Austin © 2013 Christopher F. McNulty and on Flickr
Whoops – it's going to be in my new book, but it wasn't done yet. Nothing like a little time pressure, right???
What's one of the critical new features of MMS in 2013? Navigation!
Navigation is often described as being part of a 'catalog'. This can be a little confusing. Yes, you can use MMS to set up navigation for a range of merchandise for access on a public facing Internet site. But it's probably more common, and more powerful to use it to publishing a navigable "catalog" to browse information regardless of its physical/logical hierarchy among your SharePoint sites?
What does this really mean? So long as your content is tagged with an MMS tern, you can unify the view – regardless of whether our docs "belong" to sites for marketing, products, IT or anywhere else in your farm.
Setting up a catalog
First, set up the term set (Site Settings | Site Administration |Term Store Management: For now, any Term Set will do:
In the Properties for the Term Set as a whole, ensure that under intended use you check:
Use this Term Set for Site Navigation and Use this Term Set for Faceted Navigation.
Next, make sure that in the document libraries you have either Enterprise Keywords or MMS Columns defined so content can be appropriately tagged with your MMS terms.
Set up MMS navigation
First, lets create a new team site to be our catalog. I'm calling mine "InfoCatalog"). Next, go into Site Settings | Look and Feel |Navigation
You have a choice between Global Navigation (top menu) or Current Navigation (Side Menu). Let's use top navigation, and select Managed Navigation to let MMS drive navigation. Finally, further down on the screen, we'll specify the specific term set to use for navigation.
Back on the InfoCatalog site, we create a library or at least a place where we can create a web part page. I have created a library called ProductPages and a page titled Details.aspx
On that web part page, add the Items Matching a Tag web part:
Back on the Term Set properties, make the new page the Target page for terms in this term set.
Now we can go back to our source page and edit properties of the Items Matching a Tag web part: (default properties shown)
The most important thing we want to do is Change Query. This brings up a modal dialog that lets us adjust the query. The great things about this dialog is that it shows the immediate impact of your changes as you make them. Since our content could live anywhere, let's broaden scope to the current site collection, and restrict the search to the navigation term of the current page:
We'll also expand the number of items to show by default to five, and the default template to allow for List with Paging
Save the page, and voila – we now have a dynamic page that adjusts with navigation to show auto-query tagged content:
And, over time, as you adjust the term set, the navigation adjusts accordingly: