Managed Metadata SPS 062011
Download as PPTX, PDF0 likes401 views
This document provides an overview of managed metadata in SharePoint 2010. It discusses the need for metadata management, the history of metadata in SharePoint, the end user and administrative experiences, and the architectural components. Key points include: metadata allows for easy classification and finding of information; columns and values were previously used for metadata but lacked management; end users can easily add metadata through typing, hierarchies, and Office integration; administrators can plan, design, and control metadata through term sets and libraries; and the managed metadata service stores metadata in a database and can be used across web applications.
Managed Metadata SPS 062011
- 1. Managed MetadataHersh AjgaonkarPointBridge Solutionswww.pointbridge.comw_cyber@hotmail.com @wcyberhttp://lifewithsharepoint.com
- 2. AgendaManaged Metadata in 2010Pre-RequisitesNeed for Metadata managementHistoryEnd User Experience End User - DEMOAdministrative / Design ExperienceAdministrative / Design - DEMOArchitectural components
- 3. Pre-RequisitesFARMWeb ApplicationSite CollectionSiteListsDocument LibrariesContent TypesMetadata
- 4. AgendaManaged Metadata in 2010Need for Metadata ManagementHistoryEnd User Experience End User - DEMOAdministrative / Design ExperienceAdministrative / Design - DEMOArchitectural components
- 5. met·a·da·ta
- 6. Need for MetadataEasily classify informationEasily find information
- 8. Metadata
- 9. AgendaManaged Metadata in 2010 Need for Metadata ManagementHistoryEnd User Experience End User - DEMOAdministrative / Design ExperienceAdministrative / Design - DEMOArchitectural components
- 10. HistoryColumns to be used as metadata…
- 11. HistoryValues to be used as metadata…
- 12. HistoryOops…
- 13. AgendaManaged Metadata in 2010Need for Metadata ManagementHistoryEnd User Experience End User – DEMOAdministrative / Design ExperienceAdministrative / Design – DEMOArchitectural components
- 14. End User ExperienceData Entry OptionsType ahead with synonymsHierarchical pickerOffice IntegrationNavigationNavigation within your lists / document librariesFilter on key values
- 16. End User ExperienceGotchasDoes not work in Datasheet viewDoes not work in InfoPath formsIf you customize (InfoPath) your list/library views, you won’t be able to use the MM columns
- 17. AgendaManaged Metadata in 2010Need for Metadata ManagementHistoryEnd User ExperienceEnd User – DEMOAdministrative / Design ExperienceAdministrative / Design – DEMOArchitectural components
- 18. Administration / DesignNew Column TypeDEMO
- 19. Administrative / DesignPlan for MetadataStart with Groups -> Term Sets -> TermsUse the planning worksheet provided by MicrosoftTerm Sets Planning: http://bit.ly/TSPlanningDetailed Term Sets: http://bit.ly/DetailTSPlanHave no clue where to start? Have $$?http://bit.ly/Layer2Terms (Layer2 Product)
- 20. Design : Term Set Planning
- 22. Administrative / DesignControl over metadata with flexibility of deployment as compared to 2007Allows for hierarchical storageHierarchy gives contextSecurity
- 23. Administrative / DesignAccessible from Central Admin as well as Site SettingsSynonymsMulti-Lingual User Interface (MUI)Feedback from end users (Contact)DeleteRename
- 24. Administrative / DesignContent Type HubAllows you, the admin, to share content types across site collectionsIn the MMS, you can select which Site Collection is to be used as a HUB1 SC per MMS
- 25. Administrative / DesignService Configuration
- 27. Administrative / DesignTerm Set
- 30. Administrative / DesignGotchasAs an admin, although you have rights to look at the term store, you need to add yourself as the ‘Term Store Administrator’
- 31. GotchasImport option available but NO EXPORTIn certain cases, the features required are not enabled (not available in UI, use PS)Enable-SPFeature-id "73EF14B1-13A9-416b-A9B5-ECECA2B0604C" -Url <Site-URL>Enable-SPFeature-id "7201D6A4-A5D3-49A1-8C19-19C4BAC6E668" -Url <Site-URL>Administrative / Design
- 33. AgendaManaged Metadata in 2010Need for Metadata ManagementHistoryEnd User ExperienceEnd User – DEMOAdministrative / Design ExperienceAdministrative / Design – DEMOArchitectural components
- 34. Architectural ComponentsBased on Service Application Architecture “Managed Metadata Service” is the Service Application we needUses a DB to store and manage informationCan create more than 1 MMSWeb App can be associated with more than 1 MMS
- 35. FARM 1Architectural ComponentsFARM 2Web App1 Web App 2 Web App 3 Managed Metadata ServiceMMSDB
- 36. Things to think about…Designing your IA for tagging information – best way to architect the Term Store(s)Sharing content types across Site Collections?Security?Size?DR when architecting MMS stores (number)
- 37. Q & A?
- 38. HousekeepingPlease remember to submit your session evaluation forms after each session you attend to increase your chances at the raffleFollow SharePoint Saturday Chicago on Twitter @spschicago and hashtag #spschicago
- 39. Thanks to Our Sponsors!PremierGoldSilverBronzeSponsors
- 40. Thank You!Hersh AjgaonkarI can be reached at:w_cyber@hotmail.com@wcyber