SharePoint Web Content Management can seem overly-complicated for people used to platforms like Drupal, WordPress or even DotNetNuke. Fortunately, there are a lot of resources to help you get up to speed. Here’s a set of articles I’ve leveraged in planning the taxonomy and meta data for a new project being built on SharePoint 2013.
Getting Up to Speed on SharePoint 2013 Taxonomy
SharePoint is very different from other content management systems and SharePoint 2013 introduces a lot of features that weren’t available in earlier releases. Start by getting the lay of the land with these articles that provide overviews of terminology and tools.
Introduction to managed metadata
This is the best place to start when learning about how meta data is used in SharePoint 2013. Key things to learn about are the differences between Taxonomy (structured, formal, set lists like Categories) & Folksonomy (user/community generated for content like Keywords or Tags). The other key learning is how these things are managed: You can have global sets or localized sets (site collection content type, library, list). If you are going to have a lot of authors and continue adding content regularly, then dig deeper on Managed Meta Data column & Enterprise Keywords column.
There is a section at the very end about term set properties. Give it a read because you’ll want to think about usage of the terms and term sets before getting too deep into development.
Managed metadata and navigation in SharePoint 2013
An overview of newer features and changes to how meta data is managed in SP2010 v SP2013. Some of this is technical, but it identifies some key things that you’ll want to take advantage of: Pinning, Managed Navigation and (SEO) Friendly URLs. This is a good place for you to pick up some terminology before going deeper on the topics elsewhere.
How to build a SharePoint site taxonomy
This article is about intranet and team sites, but there are some good points here about deciding the importance of certain terms in your taxonomy and it also gives some pointers on where to look during planning. Think of it as a starting point for brainstorming what should be included in taxonomy.
SharePoint 2013 Managed Metadata 2.0 – what’s right, what’s wrong
This post assumes you have a basic understanding of your taxonomy options. It gives you some thoughts on when to use different taxonomy vs folksonomy in your organization. Read this to get a better feel for what works and what doesn’t for enterprises.
Planning Your SharePoint 2013 Taxonomy
Once you know what terms mean and what a taxonomy consists of, its time to start figuring out what you want and documenting it. These are articles that look more closely at the components of taxonomy including the hierarchy of terms, different places that things can be stored and how to maintain them in SharePoint.
Plan managed metadata in SharePoint Server 2013
Bookmark this and come back to it at different points in your planning and implementation. I used this article to find the next one on my list which was very helpful.
Plan terms and term sets in SharePoint Server 2013
This article walks you through the steps of setting up terms sets, gives you examples of what might be used as meta data and brings up some questions about the best situations to Managed Meta Data. You’ll want to read this a few times and keep it handy. There are also some templates at the bottom of the article that you can use to get started.
Designing Your Taxonomic Hierarchy
One of my favorite articles in this list. It looks at organizing meta data into either a single column (1 sub set with multiple nested term) or multiple column (multiple sub sets with shallower term nesting). Most of the article will have you thinking that single column is the way to go because of the ease of setup and management. Later in the article you’ll see that single-column leads to a much weaker search experience. If you have a large site or a lot of documents, then you’ll want multi-column so users can search using a wider variety of terms.
Putting SP2013 Taxonomy & Meta Data to Use in Navigation and Search
The main point of using Managed Meta Data or Term Management Tool is to leverage it for site navigation and search. Here are articles that will help you determine implementation.
Managed Metadata and Taxonomies in SharePoint 2013 [Webinar]
I found a webinar by Chris McNulty that does an amazing job of tying everything together. It reviews the things covered in earlier articles in this list and then goes into how the term management tool and taxonomies get used by SharePoint across sites. Chris also talks about limitations of metadata usage depending on how SharePoint 2013 is configured.
The webinar is an hour. I definitely think its worth watching in its entirety before finalizing any development or usage decisions.
SharePoint 2013 search, metadata-driven navigation simplify structure
This is an overview article on using tags for navigation via the Managed Navigation feature. There is not a lot of meat on this one. Read it for the section called “Getting Ready for Navigation”. Here’s the key bit of info:
By default, SharePoint will automatically create navigation paths based on the names of pages. In some cases, this approach to SharePoint search might be desirable for default pages in a section of your site. But for most pages, turning this option off will allow you to manually create term affinities for individual pages…
This means that you can decide whether SharePoint uses the page name/URL as navigation or relies on your terms. You might want the default option for your main navigation, but you should look at using term based navigation for in-page sub-nav or internal linking within content.
SharePoint Navigation – Structured, Metadata Managed, Intelligent Contextual Navigation?
I’m going to warn you that there is some terrible grammar in this article and could use a little copy-editing. I like it because it talks about navigation choices and using managed meta data in a very non-technical way. It’s short and worth the read for the ideas.
Please suggest other resources in the comments. SharePoint 2013 is a complicated animal and I think everyone can use some help from time to time.