2. Agenda Managed Metadata in 2010 Pre-Requisites Need for Metadata management History End User Experience End User - DEMO Administrative / Design Experience Administrative / Design - DEMO Architectural components
3. Pre-Requisites FARM Web Application Site Collection Site Lists Document Libraries Content Types Metadata
4. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User - DEMO Administrative / Design Experience Administrative / Design - DEMO Architectural components
9. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User - DEMO Administrative / Design Experience Administrative / Design - DEMO Architectural components
13. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User – DEMO Administrative / Design Experience Administrative / Design – DEMO Architectural components
14. End User Experience Data Entry Options Type ahead with synonyms Hierarchical picker Office Integration Navigation Navigation within your lists / document libraries Filter on key values
16. End User Experience Gotchas Does not work in Datasheet view Does not work in InfoPath forms If you customize (InfoPath) your list/library views, you won’t be able to use the MM columns
17. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User – DEMO Administrative / Design Experience Administrative / Design – DEMO Architectural components
19. Administrative / Design Plan for Metadata Start with Groups -> Term Sets -> Terms Use the planning worksheet provided by Microsoft Term Sets Planning: http://bit.ly/TSPlanning Detailed Term Sets: http://bit.ly/DetailTSPlan Have no clue where to start? Have $$?http://bit.ly/Layer2Terms (Layer2 Product)
22. Administrative / Design Control over metadata with flexibility of deployment as compared to 2007 Allows for hierarchical storage Hierarchy gives context Security
23. Administrative / Design Accessible from Central Admin as well as Site Settings Synonyms Multi-Lingual User Interface (MUI) Feedback from end users (Contact) Delete Rename
24. Administrative / Design Content Type Hub Allows you, the admin, to share content types across site collections In the MMS, you can select which Site Collection is to be used as a HUB 1 SC per MMS
30. Administrative / Design Gotchas As an admin, although you have rights to look at the term store, you need to add yourself as the ‘Term Store Administrator’
31. Gotchas Import option available but NO EXPORT In 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. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User – DEMO Administrative / Design Experience Administrative / Design – DEMO Architectural components
34. Architectural Components Based on Service Application Architecture “Managed Metadata Service” is the Service Application we need Uses a DB to store and manage information Can create more than 1 MMS Web App can be associated with more than 1 MMS
35. FARM 1 Architectural Components FARM 2 Web App1 Web App 2 Web App 3 Managed Metadata Service MMSDB
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)
38. Housekeeping Please remember to submit your session evaluation forms after each session you attend to increase your chances at the raffle Follow SharePoint Saturday Chicago on Twitter @spschicago and hashtag #spschicago
39. Thanks to Our Sponsors! Premier Gold Silver Bronze Sponsors
40. Thank You! Hersh Ajgaonkar I can be reached at: w_cyber@hotmail.com @wcyber
