<p>One of the enduring challenges for most Web content management tools is the conflict between thephysical nature of storing content and the logical relationship between much of that content on awebsite. The SharePoint collaboration and content management platform is no exception.</p><p>End users have always had to create physical sites and libraries to store SharePoint content.This physical hierarchy also represented the foundation of navigation and, effectively, theinformation architecture of any SharePoint-poweredWeb application. While it is generally considered a tried-and-true approach, there are manycircumstances where physically locating content in a specific navigation branch causes problems forSharePoint 2013 search tasks. For example, on product sites, various product pages need to appearunder different navigational headings because they can be associated with multiple productcategories.</p><p>In such cases, the content can and should be logically associated with multiple branches.SharePoint2013 helps make that possible by combining the updated SharePoint search engine (which borrowsprimarily from FAST Search Server technology that's now completely integrated into the new release)with Microsoft's Term Store Manager.</p><p>Anyone who has used the Term Store Manager, introduced in SharePoint 2010, can attest to thefeature's usefulness when tagging content. It enables the creation of a controlled vocabulary thatcan be applied as values for various metadata fields. That works equally well for documents and Webcontent and improves overall content "findability" when combined with an enterprise search tool. Bymixing the two technologies, SharePoint2013 enables you to use the term store to define the hierarchy of your site and create multiplebranch affinities for content.</p><p><a href="http://searchcontentmanagement.techtarget.com/feature/SharePoint-2013-search-metadata-driven-navigation-simplify-structure">Keep reading...</a></p>