Managed Metadata - SPSChicago 2010
•
0 likes•295 views
This is the slide deck I created for SharePoint Saturday Chicago Oct. 2010.
Recommended
More Related Content
What's hot
What's hot (12)
Viewers also liked
Viewers also liked (14)
Similar to Managed Metadata - SPSChicago 2010
Similar to Managed Metadata - SPSChicago 2010 (20)
Recently uploaded
Recently uploaded (20)
Managed Metadata - SPSChicago 2010
- 1. Managed Metadata Hersh Ajgaonkar Client Manager, PointBridge Solutions w_cyber@hotmail.com @wcyber http://lifewithsharepoint.com
- 2. Agenda Managed Metadata in 2010 Need for Metadata management History End User Experience End User - DEMO Administrative / Design Experience Administrative / Design - DEMO Architectural components Managed Metadata 2010 – Dev : NEXT
- 3. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User - DEMO Administrative / Design Experience Administrative / Design - DEMO Architectural components
- 4. Need for Metadata Easily classify information Easily find information
- 5. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User - DEMO Administrative / Design Experience Administrative / Design - DEMO Architectural components
- 6. History Columns to be used as metadata…
- 7. History Values to be used as metadata…
- 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
- 10. 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
- 11. End User Experience DEMO
- 12. 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
- 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. Administration / Design New Column Type DEMO
- 15. 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)
- 16. Design : Term Set Planning
- 18. Administrative / Design Control over metadata with flexibility of deployment as compared to 2007 Allows for hierarchical storage Hierarchy gives context Security
- 19. Administrative / Design Accessible from Central Admin as well as Site Settings Synonyms Multi-Lingual User Interface (MUI) Feedback from end users (Contact) Delete Rename
- 20. 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
- 21. Administrative / Design Service Configuration
- 22. Administrative / Design Group
- 23. Administrative / Design Term Set
- 24. Administrative / Design Term
- 25. Administrative / Design DEMO
- 26. 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’
- 27. 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
- 29. Agenda Managed Metadata in 2010 Need for Metadata Management History End User Experience End User – DEMO Administrative / Design Experience Administrative / Design – DEMO Architectural components
- 30. 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
- 31. FARM 1 Architectural Components FARM 2 Web App1 Web App 2 Web App 3 Managed Metadata Service MMSDB
- 32. 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)
- 33. Q & A ?
- 34. Thank You! Hersh Ajgaonkar I can be reached at: w_cyber@hotmail.com @wcyber