SharePoint ECM, DM, Taxonomy Overview

1. SharePoint ECM, DM, TaxonomyOverview Renaud Comte [MVP] Renaud.comte@wygwam.com

2. www.wygwam.com Wygwam Paris Wygwam Nord Wygwam Belux Wygwam Suisse

3. Microsoft SharePoint 2010The Business Collaboration Platform for the Enterprise and the Web Sites Composites Communities Connect and Empower People Cut Costs with a Unified Infrastructure Content Insights Rapidly Respond to Business Needs Search

4. Microsoft SharePoint 2010The Business Collaboration Platform for the Enterprise and the Web Sites Composites Communities Connect and Empower People Enterprise Content Types Metadata and Navigation Document Sets Multi-stage Disposition Audio and Video Content Types Remote Blob Storage List Enhancements Cut Costs with a Unified Infrastructure Content Insights Rapidly Respond to Business Needs Search

5. SharePoint ECM Investment Strategy SharePoint 2007 User Participation Everyone Project Plans Collaborative Content SharePoint 2010 Formal Policies Traditional ECM Customer Case Studies RFP’s Pitch books Marketing Materials Aircraft Manual Scanned Docs Drug Application Official Archives Specialists Formal and Structured Informal and Unstructured Content Types

6. User Experience – PC, Phone, Browser Delivering ECM for the Masses Traditional Content Management • Social Networking and Collaboration • Social Networking and Collaboration Traditional Content Management Search Delivers Engaging Information Experiences

7. Tag cross farm with shared hierarchal taxonomies, folksonomy and types automatically with location based metadata defaults Discover with metadata based navigation in client and server with location based view definitions the best content with Ratings the latest version with Unique Document IDs repositories with ties to Office Client New/Open/Save Manage With Document Sets for multi-document work products with Metadata based content organizer with Multi-stage retention policies with Location/Folder based policies with millions of documents Document Management:Feature Review

8. DEMO Document Management

9. Metadata promises to drive search, navigation and business behaviors Ongoing challenges with user adoption and data consistency Features: Modern end-user experience Auto-complete: MRU & against term set Rich, symmetric client and web-based UX Synonyms, multiple language support Enable both folksonomyandtaxonomy Reader tagging surfaced in MySites and on documents Bottoms-up folksonomy through ‘open’ fields Structured hierarchical taxonomy Ok to mix approaches at the field level e.g. keywords and cost center code in the same content type Syndication of content types incl. associated term sets and policy Across webs, site collections, farms Flexibly consume term sets from multiple levels around the organization Enterprise Metadata

10. 2 majors concepts Folksonomy Taxonomy

11. New object to manage work products made up of multiple documents Think Folder++ Key Scenarios Tight collection of documents A sales proposal that includes documents, spreadsheets and presentations Heterogeneous file types not usually assembled Compound documents A user manual that is an assembled roll-up of separate sections Document Set Features Shared Metadata Customized welcome page Default documents added Version capture Workflows Portability (download/upload/send to record center) Document Sets:Scenario Overview • Tag Management • - Déplier arbre de taxonomy • - Import • Terms Set ouvert fermé • Folksonomie keyword • Tag de page • Création de tag, synonymes • Content type • Publish Content Types • Ajout de colonnes • http://www.chakkaradeep.com/post/SharePoint-2010-Content-Type-Hubs-e28093-Publish-and-Subscribe-to-Content-Types.aspx • Content routing

12. DEMO Document Set

13. Scalable Architecture Large List Optimizations SharePoint 2003 • Column Indexes were not possible • Database Indexes were not supported • SharePoint 14 Scale Targets • 1 million items in a folder • 10’s of millions of items in a single library • 100’s of millions of items in large archive scenarios SharePoint 2007 • Column Indexes could be configured via the UI • End users could impact performance with poor performing • list views SharePoint 2010 • Database optimizations allow far more items in a list • - Server automatically “does the right thing” for high scale • Compound Index support • Automatic index management • Query throttling w/ fallback • Resource intensive operations can be limited or disallowed • during production hours • Large query thresholds • Blocking Operations • Can be overridden via the Object Model

14. What is RBS? Interface for SharePoint & SQL 2008 R2 to store files outside the Content DB. Benefits with RBS storage system: Better price for large scale deployments (> 5 TB) cost per MB of SQL storage vs. other systems Better OPEX for fault tolerance, backup/restore and geo-replication use of storage-system level tools vs. SQL-level tools Compliance with specific regulations around data retention/expunging (e.g. DoD 5015.2) Should I use RBS for rich media? It depends on your storage provider… Pro: Capital & operational savings from “cheaper” storage. Con: Coordinated management required. Remote Blob Storage (RBS)?

15. Digital MediaManage your digital content with Asset Libraries

16. Business Data Connectivity (External List) List Validations Enterprise Managed Metadata Search Remote Blob Storage Large List Optimizations Audit Trail Document IDs Content Organization Document Sets Summary10 super ECM Features in SharePoint 2010