110 likes | 195 Views
ECM + Social + Publishing = ESP; Yes...I do know what you are thinking!. Keith Bunge. Agenda. Session Flow Review a planned implementation and understand design decisions for different user roles Demo and see how new features work together to make KM easier than ever on SharePoint
E N D
ECM + Social + Publishing = ESP; Yes...I do know what you are thinking! Keith Bunge
Agenda • Session Flow • Review a planned implementation and understand design decisions for different user roles • Demo and see how new features work together to make KM easier than ever on SharePoint • Takeaways • High value content is about more than documents • User contribution doesn’t have to compromise value or trust • Metadata is key: drives navigation, discovery, relation,and reusability of content
Dealing with Multiple Repositories • Just one of several KM systems that are in place • Repository of high-quality, field-ready content • Many teams have their own implementations Core Query Web Parts Custom Query Web Parts SharePoint Portals CMS Custom Taxonomy SQL Server 2000 Distributed File System Knowledge Center Content Submissions
KM on SharePoint 2010 - Goals • Maintain content discoverability and authority • One sanctioned place to go to find content • Consistent layouts and branding • Tight OOTB way to integrate pages and documents • Subject area experts have the final word • Empower more people to contribute. • Just a few clicks to contribute to a topic • Rating, tagging, and commenting is quick and integrated everywhere • No hang-ups over where’s “The Right Place” to put content
Key Elements of the Solution Publishing Pages A Publishing Site • Pages are storefronts • Consistent Wiki-like experience • Implicit structure Documents A Document Center • High-value, managed content • Not a walled garden • Submissions come from anywhere Shared Services • Enterprise consistency • Taxonomy and Folksonomy Content Types Managed Metadata Content Analytics Social Feedback
Content Organization 1 3 2 CustomerReady PartnerReady CustomerReady Microsoft Only • Workflow: • Approval workflow on create • Retention Policy: • Vital review every year • Permissions: • Inherit from library root CustomerReady Folder structure created to map to business requirements Content Organizer rules created to route incoming documents to the right folder Documents inherit policies and permission from their destination folder
High value content is about more than documents Wrap UpKey Features & Takeaways Wiki-like Publishing Document Sets Ratings & comments Approval Workflow Content Organizer Metadata Search Filtering CQWP Metadata Navigation Per-Location Policy • User contribution doesn’t have to compromise value • Metadata is key Federated Content Types, Metadata