1. Renaud Comte [MVP] Renaud.comte@wygwam.com

2. www.wygwam.com

3. 3

4. 4 Enterprise Content Types Metadata and Navigation Document Sets Multi-stage Disposition Audio and Video Content Types Remote Blob Storage List Enhancements

5. User Participation Content Types Specialists Everyone Formal and Structured Informal and Unstructured Traditional ECM SharePoint 2007 SharePoint 2010

7. Tag Tag cross farm with shared hierarchal taxonomies, folksonomy and types automatically with location based metadata defaults Discover 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 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

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 folksonomy and taxonomy 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

11. Document ratings Human Readable Unique Document IDs MSFT-12-3455 Insertable into document contents Per-folder metadata defaults All documents in particular folder tagged Year=2007

12. 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) 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/Shar ePoint-2010-Content-Type-Hubs-e28093- Publish-and-Subscribe-to-Content- Types.aspx Content routing

14. SharePoint 2007 High scale libraries require careful planning and management SharePoint 14 End user features for high scale Ex: Metadata pivots, Key filters, Content organizer Server automatically “does the right thing” for high scale Compound Index support Automatic index management Query throttling w/ fallback 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

15. SharePoint 2003 SharePoint 2007 SharePoint 2010 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 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

16. 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.

17. Proposed standard for interoperability between ECM repositories and applications Started in October 2006 by IBM, EMC, MSFT Overseen by an OASIS Technical Committee, as of Sept. 2008 Version 1.0 anticipated by end-of-year 2009 Goals: Rationalize the connectivity/interop story between multiple vendors’ products Enable MSFT to offer federated ECM & interoperability capabilities for the Office system