SharePoint 2010 Managed Metadata (SharePoint 2010 JumpStart)

SharePoint Taxonomy - Predefined Taxonomy Content for the Managed Metadata Service

Contents:

  • Know it. Prove it. Challenge
  • Hello {0}, thanks for registering!
  • Breadcrumb
  • In this article
  • Introduction to managed metadata in SharePoint Server 2010

    • You submitted this rating on. You submitted this rating recently. Add to your Playlist. Join now You are not signed in yet. Join now to get cool features, including: Join now Maybe later. Share Share this lesson. The player is governed by this license. By copying or displaying this player, you agree to abide by this license.

    If you do not agree, do not copy or display the player. Check out our new embed option! You can now easily embed a specific lesson into your site. Time requirements, modules and assessments for this course: Some of the course content has been removed since your last visit. Individual course material files.

    Transcript not available for this lesson. The group manager would create term sets that relate to Human Resources, such as job titles and pay grades in the Human Resources term set group. Users can see only global term sets and term sets that are local to the user's site collection. Terms can be divided into two types: Managed terms , which are usually pre-defined, can only be created by users who have the appropriate permissions, and are often organized into a hierarchy. Enterprise keywords , which are merely words or phrase that, were added to SharePoint items.

    Know it. Prove it. Challenge

    Jump-start Microsoft SharePoint Knowledge Management using pre- defined Taxonomy Metadata. Layer2, the SharePoint Experts from Hamburg. In Microsoft SharePoint Server taxonomies of managed metadata can cover virtually any Dynamic topic pages: Try the Tag Profile Page in SharePoint or.

    All enterprise keywords are part of a single, non-hierarchical term set that is named the keyword set. Name Database Name Application Pool Configurable Account When user finished giving all the information to the wizard, user should see that the service has been started. Imagine this range as a kind of continuum.

    At one end of this continuum, there are taxonomies , which are formal, centrally-managed, hierarchical groups of terms.

    At the other end of this range, there are folksonomies , which are the collaborative classifications that result when individuals apply tags freely to content. SharePoint Server supports both extremes of this continuum, as well as points along the way. At one end of the continuum, you can implement formal taxonomies through managed terms and term sets.

    Hello {0}, thanks for registering!

    At the other end, there is support for enterprise keywords and social tagging, both of which enable site users to tag content with keywords of their choosing. In between these extremes, you can apply flexible degrees of structure and control to metadata, and you can adjust the scope at which you apply this control by choosing to make it global across sites or local to specific sites. For example, you have the ability to configure term sets to be closed or open to user contributions.

    You can choose to use enterprise keywords and social tagging in conjunction with managed terms, or not. SharePoint Server enables organizations to combine the advantages of formal, managed taxonomies with the dynamic benefits of social tagging in customized ways.

    Breadcrumb

    Local term sets are created within the context of a site collection, and are available for use and visible only to users of that site collection. If duplicate or similar terms are suggested, you may also be able to see descriptive text that the Term Store Administrator has configured for the term to help users make appropriate selections. Unfortunately, the Term Store starts out empty and most companies don't have a taxonomy. Taxonomy is a critical component of information governance and the Managed Metadata Service is key to taxonomy in SharePoint. For example, when you create a new social tag, you have the option of selecting from existing terms, which may include managed terms, as well as enterprise keywords.

    The following diagram illustrates how different kinds of SharePoint-based solutions might require different approaches to metadata based on business need. There are several advantages to employing managed metadata across the sites in an organization:. With term sets and managed terms you can establish control over the types of terms that are available to be added to content, and you can control who has the ability to add new terms. You can also limit the use of enterprise keywords to a specific list of keywords by configuring the Keywords term set as closed.

    When the same terms are used consistently across sites, it is easier to build robust processes or solutions that rely on metadata. Additionally, the user experience for working with metadata on sites, in lists and libraries, as well as in the Office client programs makes it easy for site users to apply consistent metadata to their content. New search features, such as the refinement panel, which displays on the left-hand side of the search results page, enable users to filter search results based on metadata.

    Additionally, you can configure metadata navigation for lists and libraries to enable users to create dynamic views of information based on specific metadata fields.

    Table of contents

    Users can navigate libraries by folder or by metadata pivot, and they can then refine the results by using additional Key Filters. You can update a term set easily in the Term Store Management tool, and new or updated terms will automatically become available for use wherever a Managed Metadata column associated with that term set is available. If you merge multiple terms into one term, content that is tagged with these terms is automatically updated to reflect this change.

    You can specify multiple synonyms or labels for individual terms. If your site is multi-lingual, you can also specify multilingual labels for individual terms. Your organization may want to engage in some degree of planning before you start using the managed metadata features. The degree of planning required is more or less proportional to the degree of formality and control you want to impose on metadata.

    If you want to let users help develop your taxonomy, then you can simply have users add keywords to items, and then organize these into term sets as necessary. If your organization wants to use managed term sets to implement formal pre-defined taxonomies, then key stakeholders with a vested interest in the structure of the taxonomy need to collaborate to plan and develop the term sets and terms to be used.

    In this article

    For more information about this planning process, see Plan terms and term sets. For more information about configuring a Managed Metadata Service application, see Managed metadata administration. After the key stakeholders in the organization agree upon the required term sets, you can use the Term Store Management Tool to import or create your term sets and to manage and maintain the term sets as users begin working with the metadata. The Term Store Management Tool provides a tree control you can use to perform most tasks.

    Your user role for this tool determines what tasks you can perform. For detailed information about these roles, see Managed metadata roles. To take actions on an item within the hierarchy, point to the name of the Managed Metadata Service application, group, term set, or term you want to modify, click the arrow that appears, and then use the menu to select the actions you want. If you are a Term Store Administrator or a Group Manager you can create, import, or delete term sets within a group. Term set contributors can create new term sets. If you are a Term Store Administrator, a Group Manager, or a term set Contributor, you can create or reuse terms within a term set, as well as copy, move, or delete a selected term set.

    If you are a Term Store Administrator, a Group Manager, or a term set Contributor, you can create copy, reuse, merge, deprecate, move, or delete individual terms within a term set. At each level of the hierarchy, you can configure specific properties for a group, term set, or term using the Properties pane that displays to the right of the Term Store tree control. For example, if you are configuring a term set, you can use the Properties pane to specify details such as Name, Description, Owner, Contact, and Stakeholders.

    You can specify whether you want a term set to be open or closed to new submissions from users.

    Introduction to managed metadata in SharePoint Server 2010

    You can also specify if you want the term set to be available for tagging. If you choose to make a term set unavailable for tagging, then it will not be visible to most users. If a term set is still under development, for example, you might choose to make in unavailable for tagging. If a Managed Metadata column has been added to a content type, list, or library, then content owners can tag their content with managed terms from a specific term set by editing the properties for a list or library item and then updating the relevant fields in the Edit Properties form for the item or document.

    Managed Metadata columns are easy to identify because they display a tags icon that can be used to launch the term picker dialog box.

    • Prayers from the Heart (Inspire Charming Petites) (Inspire Charming Petites Ser).
    • International Life Writing: Memory and Identity in Global Context.
    • Schwarzstart (German Edition).
    • Word Empowered Life.
    • Mobile Navigation.