Designing a Microsoft SharePoint 2010 Infrastructure Vol 1 part 38. This course is intended for IT Professionals who use Microsoft SharePoint 2010 in a team-based, medium-sized to large environment. While they may have implemented a SharePoint deployment, they have limited experience in designing a SharePoint infrastructure. They likely work as a senior administrator who acts as a technical lead over a team of administrators. Members of this audience should have at least 6 months experience with SharePoint 2010. | Planning Managed Metadata 7-31 Term set name Term set description LCID locale identifier Available for tagging true false Term description Level 1 term Level 2 term Level 3 term Level 4 term Level 5 term Level 6 term Level 7 term Note The Term Store Management Tool provides a sample CSV import file. You are recommended to create a planning worksheet that identifies any term set requirements by using these columns. You can then use the planning worksheet to import the term set into SharePoint 2010. You can use Microsoft Excel to facilitate this import process. Question Who can import term sets Additional Reading For more information about the managed metadata input file format in SharePoint Server 2010 see http fwlink LinklD 200886 clcid 0x409. MCT USE ONLY. STUDENT USE PROHIBITED 7-32 Designing a Microsoft SharePoint 2010 Infrastructure Planning for Shared Taxonomies and Content Types Key Points In most SharePoint 2010 environments you only require a single instance of the Managed Metadata Service. When you plan for a single instance of the Managed Metadata Service consider the following points You can implement any term sets that you require in the single instance of the Managed Metadata Service up to 1 000 term sets. You can implement enterprise keywords from the single instance of the Managed Metadata Service. You can publish content types from a single site collection only. If you are planning for multiple instances of the Managed Metadata Service and you plan to share instances across Web applications consider the following best practices Only configure one Managed Metadata Service instance to be the default storage location for column-specific term sets. MCT USE ONLY. STUDENT USE PROHIBITED Planning Managed Metadata 7-33 Only configure one Managed Metadata Service to be the default storage location for keywords. If you are planning the Managed Metadata Service to support a multi-tenancy environment consider the following Term set groups can .
