The document discusses advancements in content management within SharePoint 2010, highlighting features like managed metadata services, business connectivity services, and content type syndication. It outlines the benefits of external content types and enhanced integration capabilities for external data, as well as improvements in list functionalities and document set management. The focus is on enabling efficient organization, tagging, and retrieval of content to support varied business needs.

1. Content Management in SharePoint 2010 Eli RobillardSharePoint Server MVP

2. Microsoft SharePoint 2010SitesConnect and Empower PeopleCommunitiesCompositesCut Costs with a Unified InfrastructureContentInsightsRapidly Respond to Business NeedsSearch

3. What’s New for ContentManaged Metadata Service Business Connectivity Services What’s New for Lists and Libraries New ways to tag content

4. Managed Metadata ServiceA Term Store contains term sets and managed keywords.Term Sets are hierarchical taxonomies.Keywords are non-hierarchical terms.Content Types can be syndicated from a Hub.

5. Term StoreMetadata Shared ServiceOne term store per shared service appTerm StoreContentTypeHubMany groups per term store. Used as security boundaryContent TypesGroup(s)Many term sets per group (max 1000 total per term store)Term Set(s)30K terms per term set (max. 1m total)SynonymsDescriptionTranslationsCustom propertiesTerm(s)

6. Managed Metadata Service

7. Managed Metadata ServicesFarm 1Farm 2Term Store 1aWeb App 2Web App 1aConnection ProxyTerm Store 2Doc Lib 1bWeb App 1bWeb App 3Term Store 3Farm 3Site Coll. 1b

8. Content Type SyndicationBig value addsUp-to-date and consistent schemas across the EnterpriseSyndicated content types can have a single policy i.e,. from now on blogs posting must expire after 18 monthsPublishing content types1Content Types are ‟published” from a ‟normal” Site Content Type GalleryMaximum of 1 Hub per Metadata Shared Application ServiceIt is not a requirement that a Metadata Service syndicate content typesIt is not a requirement that a service connection consume content types from the serviceSetting a site collection to be the hub enables necessary components on hubWhat gets published?2Content Type with all the corresponding columnsIncluding Document Set Content TypePoliciesAnd workflow associations (not the workflows)

9. Content Type Syndication3Managing published content typesFrom the hubPublish UnpublishRepublishRoll-up errors from consuming site collectionsOn the consumer sideExtend a published content typeDerive from a published content typeView import errorsRefresh all content types consumed from the Hub

10. Business Connectivity ServicesExternal Content TypesBusiness Data Connectivity (BDC)

11. SharePointDesign ToolsOffice ApplicationsBCS ClientDev PlatformEnterprise SearchBusiness IntelligenceCollaboration SocialEnterprise Content ManagementSharePointDesignerExternal ListsExternal Content Type RepositoryVisual StudioBusiness Data ConnectivityWeb 2.0DBWCFWeb ServiceLOBBusiness Connectivity Services

12. External Content Type (ECT)The building blockSuperset of entity capabilities; describes:Structure of the external system (Fields, Methods, Connection)How this data behaves within SharePoint and OfficeManage and reuse from a central locationAdded to the Business Data Connectivity service through:SharePoint DesignerVisual Studio 2010Import into the Business Data Connectivity service as part of a model

13. External Content Type (ECT)The building blockBCS-enabled solutions rely on ECTs to integrate external data into SharePoint and the Office client applicationsCan be reused in:External ListSearchOutlookSharePoint Workspace WordInfoPathAccessOther Office applications via code

14. External Content TypeThe Building BlockSharePoint Workspace with InfoPath FormsOutlook Forms andTask panesSharePoint External listsSearch resultsOffice Apps

15. PresentationExternal Lists in SharePointPresentationConnectivityToolingExpose external data as a native SharePoint list Full CRUD capability Familiar UI and navigationSort, Filter, GroupProgrammatic access via SPList OMProfile page available for each item in the list FormAuto-generated OOBUpsize to InfoPathOffline-able

16. PresentationOffline External ListPresentationConnectivityToolingConnect to Outlook asContactsTasksCalendarsPostsDownload to SharePoint Workspace as ListsWord doc libraries with external data columns

17. PresentationSurfacing External DataPresentationConnectivityToolingExternal Data Columns Add data from external content types to standard SharePoint listsCan be made available as Content Controls in WordWeb PartsScenario: Use for Dashboard pagesExternal Data List External Data ItemExternal Data Item BuilderExternal Data Related ListExternal Data Connectivity FilterChart Web PartExternal Data Search Integrate External Data into search results

18. ConnectivityPresentationConnectivityTooling.NET Assembly ConnectorUseful approach if business logic can be exposed through static APIs that rarely changeDoes not provide facility to over-ride default TypeReflectorCustom ConnectorUseful approach when back end interfaces change frequently (dynamic)Provides facility to over-ride default TypeReflectorServer & Client side pluggability for customSSO provider

19. ConnectivityConnecting to External DataPresentationConnectivityToolingBusiness Data Connectivity enhancementsRead/write capabilityClaims awareConnect via ADO/SQL, WCF/WS, .Net Assembly and Custom ConnectorsBatch and bulk operation supportBDC used for Search indexing connectorsAdded blob, incremental crawl and item level SecuritySymmetrical server and client runtimesConnect from client or server directly to external dataRich client cacheSQL CE database is used to cache external dataAllows for “cached mode” behavior on external data

20. ToolingEasily create and customize solutionsPresentationConnectivityToolingAssemblyNo-code solutions in SPDExternal Content Type definitionsForm layout and validationWorkflow integrationBuild Pro-Dev Solutions in Visual StudioCreate reusable components (UI parts, ECTs, actions)Custom Office Integration (add-ins)Custom connectivity.Net Assembly ConnectorCustom ConnectorCode-based business logic

21. Types of SolutionsPresentationConnectivityToolingCustom connectivity for data aggregation, transformation, security, etc.

22. Use custom code to integrate data into any Office app

23. Business logic in forms

24. Create reusable components (UI parts, ECTs, actions)

25. Customize

26. InfoPath forms

27. Workflow

28. Web Part Pages

29. Outlook task pane and ribbon

30. Out-of-box

31. Surface data in External Lists

32. Connect those lists to Outlook, SPW

33. External Data ColumnsIntermediateSimpleAdvancedNO CODE*CODESharePoint DesignerSharePoint SDKVisualStudioAdvanced DeveloperDeveloperPower User

34. Baked into the Platform…SharePoint Server 2010Office 2010Secure Store ServiceExternal Data SearchRich Client ExtensionsBDC Client RuntimeExternal Data Web PartsProfile PagesSharePoint Foundation 2010External ListExternal Data ColumnBusiness Data Connectivity Service

35. What’s New for ListsRelationships with Cascade or BlockLocation-based metadataMulti-select operationsBetter scalability and performanceAuto-generated indexesList query throttlingAsset Libraries for Rich Media content

36. What’s New for ListsExternal ListsDocument SetsDocument IDsMetadata-based Navigation

37. External ListsSurface external data to usersSupports all CRUD operationsFamiliar UI (sort, filter, group, etc.)Auto-generated formsOption to upsize to InfoPath forms

38. Document SetsA way to group related filesInherits from FolderCan set location-based metadata Documents Sets can have Document IDs

39. Document IDsA unique identifier that follows a document wherever it goes.Documents with IDs have permanent URLs (permalinks) A Doc ID Redirector locates the documentCan use the out-of-box service to generate IDs or build your own

40. Metadata-based NavigationFolder-like navigation Auto-generated based on metadata

41. Ways to tag files with metadataWeb Browser1List items can be tagged by using the ‟Edit Properties” UIBy a business processBy virtue of the location in which we choose to store the item (location based metadata)Values from the parent Doc SetOffice Clients2Document Information Panel allows for tagging in the authoring surface of the Office clientBackstage in the Office clients will allow full fidelity of the managed metadata controlsInfoPath forms Custom Apps33rd party or custom applications using SharePoint Metadata OM

42. Metadata driven scenariosRecords ManagementDAMGlobalBy modifying out-of-the-box settings a single infrastructure can support a large range of business needs:Managed Metadata Column Term SetShared Service ApplicationStandardized Contract TemplateCorp. IntranetCorp.Tag CloudTeam or Application SpecificScopeKnowledgeBaseMySiteLocalTeam or Project Doc LibFolksonomyManaged TaxonomyOpen HierarchiesLevel of Control

43. Metadata field & featuresManaged Metadata ColumnClosed Term SetOpen Term SetType-aheadDisambiguationMUI supportDescriptionSynonymsTree PickerAdd new TermControlled & managedFlexible & open

44. Metadata field & featuresManaged Keywords Column & Social Tagging ControlClosed Term SetOpen Term SetKeywords SetType-aheadDisambiguationMUI supportDescriptionSynonymsTree PickerAdd new TermValidates all termsUploadControlled & managedFlexible & open

45. Why do we tag?Metadata drives discovery and decisionsMetadata is how we navigateMetadata improves search

46. Types of dataStructuredIndustry-standard categories

47. Line-of-business data

48. Central lookup lists

49. Data warehouses

50. Surveys

51. Access databases

52. SharePoint ListsUnstructuredFile shares

53. Narratives, blogs

54. Office documents

55. Surveys

56. Access databases

57. SharePoint ListsTypes of metadataStructuredTaxonomiesCentrally managedStandardizedMature languagesSimple, well-understood domainsUnstructuredFolksonomiesAnyone can define a termAd hoc Emerging languagesComplicated or complex domains

58. Action ItemsThink about the new scenarios SharePoint 2010 makes possible.Consider the planning you’ll want to do to prepare for RTM. Start using the beta!