SharePoint ECM, DM, TaxonomyOverview

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

www.wygwam.com

Wygwam ParisWygwam NordWygwam Belux

Wygwam Suisse

Microsoft SharePoint 2010The Business Collaboration Platform for the Enterprise and the Web

3

Connect and Empower People

Cut Costs with a Unified Infrastructure

Rapidly Respond to Business Needs

Communities

Search

Sites

Composites

Insights Content

Microsoft SharePoint 2010The Business Collaboration Platform for the Enterprise and the Web

4

Connect and Empower People

Cut Costs with a Unified Infrastructure

Rapidly Respond to Business Needs

Communities

Search

Sites

Composites

ContentInsights

Enterprise Content TypesMetadata and NavigationDocument SetsMulti-stage DispositionAudio and Video Content TypesRemote Blob StorageList Enhancements

SharePoint ECM Investment Strategy

User Participation

Content

Types

Drug Application

Aircraft Manual

Pitch books Marketing

Materials

Collaborative Content

Customer Case Studies

Formal Policies

Official ArchivesSpecialists

Everyone

Formal and

Structured

Informal and Unstructured

RFP’s

ScannedDocs

Project Plans

Traditional ECM

SharePoint

2007

SharePoint 2010

Delivering ECM for the Masses

Search Delivers Engaging Information Experiences

Social Networking and Collaboration

Traditional Content

Management

• Tagcross farm with shared hierarchal taxonomies, folksonomy and types automatically with location based metadata defaults

• Discoverwith metadata based navigation in client and serverwith location based view definitionsthe best content with Ratingsthe latest version with Unique Document IDsrepositories with ties to Office Client New/Open/Save

• ManageWith Document Sets for multi-document work productswith Metadata based content organizerwith Multi-stage retention policieswith Location/Folder based policieswith millions of documents

Document Management:Feature Review

DEMODocument Management

• Metadata promises to drive search, navigation and business behaviors• Ongoing challenges with user adoption and data consistency • Features:

Modern end-user experienceAuto-complete: MRU & against term set

Rich, symmetric client and web-based UX

Synonyms, multiple language support

Enable both folksonomy and taxonomyReader tagging surfaced in MySites and on documents

Bottoms-up folksonomy through ‘open’ fields

Structured hierarchical taxonomy

Ok to mix approaches at the field levele.g. keywords and cost center code in the same content type

Syndication of content types incl. associated term sets and policyAcross webs, site collections, farms

Flexibly consume term sets from multiple levels around the organization

Enterprise Metadata

2 majors conceptsFolksonomy Taxonomy

New object to manage work products made up of multiple documentsThink Folder++

Key ScenariosTight collection of documents

A sales proposal that includes documents, spreadsheets and presentationsHeterogeneous file types not usually assembled

Compound documentsA user manual that is an assembled roll-up of separate sections

Document Set FeaturesShared MetadataCustomized welcome pageDefault documents addedVersion captureWorkflowsPortability (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

DEMODocument Set

Scalable Architecture Large List Optimizations

- Column Indexes were not possible- Database Indexes were not supported

SharePoint 2003

- Column Indexes could be configured via the UI- End users could impact performance with poor performing list views

SharePoint 2007

- Database optimizations allow far more items in a list- Server automatically “does the right thing” for high scale

Compound Index supportAutomatic index managementQuery 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

SharePoint 2010

SharePoint 14 Scale Targets

1 million items in a folder10’s of millions of items in a single library100’s of millions of items in large archive scenarios

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-replicationuse 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)?

Digital MediaManage your digital content with Asset Libraries

1. Business Data Connectivity (External List)2. List Validations3. Enterprise Managed Metadata4. Search5. Remote Blob Storage6. Large List Optimizations7. Audit Trail8. Document IDs9. Content Organization10. Document Sets

Summary10 super ECM Features in SharePoint 2010