Mark Orange - SharePoint 2010 Content Types Model - SPC NZ 2011
Download as PPTX, PDF5 likes1,485 views
The document outlines the agenda and content types model for the New Zealand SharePoint Conference held on March 16-17, 2011. It discusses the importance of content types in managing information within SharePoint, including their structure and the role of various columns as metadata. Additionally, it describes the layers of the content types model, emphasizing the operational management and design of these content types within an enterprise context.
Mark Orange - SharePoint 2010 Content Types Model - SPC NZ 2011
- 2. Content Types ModelMark Orange
- 4. Session AgendaContentContent TypesContent Types ColumnsContent Types Model
- 5. SharePoint Service ApplicationsSharePoint - PlatformSharePoint ServerClient AppsProject Server2010Browsers (IE, Fire Fox)Search ServiceProject Web AccessPowerPoint Broadcast ServiceOffice ClientExcel Calc ServiceWeb Analytics ServiceOneNoteFAST 2010 User ProfilesOffice Web App Service3rd PartyServices..FAST Search ServiceVisio Graphics ServiceInfoPathBusinessConnection ServiceAccess ServiceProjectInfoPath ServiceManaged MetadataOutlook Word Conversion ServicePerformancePointRSS ViewersSharePoint FoundationSharePoint WorkspaceSandboxed Code ServiceUsage & Health LoggingVisioSharePoint DesignerContentConfigWorkflowAccess
- 7. SharePoint - PlatformContentLists & LibrariesColumnColumnColumnColumnColumnColumn
- 8. SharePoint - PlatformContentContent TypeColumnColumnColumnColumnColumnColumn
- 9. Content TypesThe fundamental building blocks for managing information and data within SharePoint
- 10. What vs. Where
- 11. Site Content Types GalleryBook Content TypeReport Content Type
- 13. Business UnitDocument BaseEffective Date
- 14. Lawyer
- 15. Client Code
- 16. Business Unit
- 17. Review Date
- 18. Category
- 19. Client Code
- 20. Business Unit
- 21. Theme
- 22. Author
- 23. Client Code
- 24. Business Unit
- 27. Security ClearanceGeneral ManagerGeneral ManagerGeneral ManagerContent Types
- 29. Document LibraryDocument LibraryDocument LibraryContent TypeContent TypeContent TypeContent Types
- 31. Content Types apply rules and behaviors based on what an item isLists and libraries apply rules and behaviors based on where an item isContent Types
- 33. The Columns in a Content Type define the different content elements and metadata needed to manage that type of information.Columns need a purpose!Columns
- 34. Column Purposes ContentInformation to be displayed to end users.Metadata RecordInformation captured at a specific point in time that records an important immutable value.Metadata FindabilityInformation to allow the discovery, sorting, filtering, and grouping of items.Metadata ActivityInformation to support an activity, process or function.
- 35. Columns Content–Information to be displayed to end users.Column contains information such as text and images that is the content or part of the content of the SharePoint item that is to be displayed to end users. Such as the Headline or body of a web page item, the Name or phone number of a Contact item.Metadata Record –Information as captured at a specific point in time and retained as a record.Column contains content or data that relates to a SharePoint item, such as a document or a task, which is an important record of a business transaction, activity or process. The column may contain the content that was published, or provide context about who edited the content and at what time. Metadata Findability – Information to allow the discovery, sorting, filtering, and grouping of items.Column is leveraged by end users for advanced search, content query web parts, data view web parts, or views to create lists of SharePoint items based on the information within the column. For example all SharePoint items that are customer documents created after a certain date by a certain user.Metadata Activity – Information to support an activity, process or function. Column contains information that is used programmatically to support an activity such as a workflow, routing of items, or integration with another business system such as K2 or SAP.
- 36. Heading
- 37. Date
- 38. Source
- 39. Body
- 40. Category
- 41. Date Created
- 42. Date ModifiedContent Type: Article Web PageArticle Web PageContentRecordFindabilityActivity
- 43. Content Type: Project TaskProject Task WaterfallProject Task AgileStage
- 45. Description
- 46. Owner
- 48. Content Type: Client DocumentDocument Client IdentityDocument Client ContractClient Full Name Record
- 49. Contract DateDocument Client BaseName
- 50. Title
- 53. Content Types ModelPURPOSE: The Content Types Model illustrates and describes the relationships, context, and purpose of all Content Types through the layers of an Enterprise SharePoint Platform.
- 54. Content Types ModelVALUE:The model is an important information asset for the design and the on-going operational management of Content Types, and ultimately all information within a SharePoint platform.
- 55. The Model: LayersSite LayerSolution LayerPlatform LayerSystem Layer
- 56. Site LayerSolution LayerPlatform LayerSystem Layer
- 57. The Model: LayersSite LayerSolution LayerPlatform LayerSystem Layer
- 58. The Model: LayersSystem Layer
- 59. The System LayerOwned and managed by: MicrosoftThe generic foundation Content Types that are created by the Microsoft development team that builds the SharePoint product. These are the Content Types that are automatically provisioned when SharePoint is installed in any organisation.
- 60. The Model: LayersSite LayerSolution LayerPlatform LayerSystem Layer
- 61. The Model: LayersPlatform Layer
- 62. The Platform LayerOwned and managed by: Architecture and GovernanceThe global Content Types that are created for the enterprise and are consumed by solutions that are built on the platform. As existing solutions evolve and new solutions are created new global Content Types will be identified as part of the solution design that need to be provisioned and managed as part of the Platform Layer.
- 63. The Model: LayersSite LayerSolution LayerPlatform LayerSystem Layer
- 64. The Model: LayersSolution Layer
- 65. The Solution LayerOwned and managed by: Architecture and GovernanceThe Content Types that are created for specific business solutions that are deployed on the platform. These solutions are usually developed by a Project team and then handed over to the operations team on completion.
- 66. The Solution LayerOwned and managed by: Architecture and GovernanceA critical part of the solution design process is to identify Content Types within a solution that will:reuse existing Solution Layer Content Typesbe new solution specific Content Typesextend Platform Layer Content Types be new Platform Layer Content Types
- 68. The Model: LayersSite LayerSolution LayerPlatform LayerSystem Layer
- 69. The Model: LayersSite Layer
- 70. The Site LayerOwned and managed by: Ops team and Site OwnersThe Content Types that are provisioned and configured for a specific SharePoint Site Collection and/or SharePoint Site that is being used by business users on the SharePoint platform.
- 71. The Site LayerOwned and managed by: Ops team and Site OwnersSites are the end user experience of the SharePoint platform and the solutions delivered upon it. A critical part of provisioning a site is understanding, communicating, and managing the type of site it is and the type of Content it manages within the organisation.
- 72. Content Type HubThe role of the Content Type hub is to provide centralised management of globalContent Types. In particular parent Content Types.Platform Layer
- 73. THE MODELIN ACTION
- 77. Gold SponsorsSilver SponsorsBronze Sponsors
Editor's Notes
- #4: One of the challenges with modern information management systems is the ease at which users can create vast amounts of information.There is no question we are well into the information age with the internet ‘the information black hole’ providing the backbone to this.Like the internet is to society, SharePoint can become an ‘Information Black hole’ within an organisation.SharePoint can be both the solution and the problem.
- #9: A Content Type is an Item Template.Like a Site Column it is created independent of a list and can then be used across many lists.Content Types allow us to manage information Assets by What they are rather than Where they are.As an Item Template a Content Type is a collection of properties, rules and behaviours that are enforced for items of that type regardless of the list they are stored in.
- #13: All Content Types inherit from a parent Content Type, this can be used to an organisations advantage by creating a parent content type that includes any properties that are required across all items and documents.Over time as the organisation evolves further properties can be added to the parent content type and therefore be added automatically to all the other content types.Click – So if Security Clearance was added as a property to the Parent Type it will also be used for the content types that inherit from it
- #21: Column PurposesColumns may have a single purpose or more likely be used for a number of different purposes. The purpose of a Column should be defined and captured in supporting code comments and any supporting documentation. For example the purpose of a Body Content Column on a News Article Content Type is most likely needed for containing the body of the news article and also providing a record of what the body of the news article was at a given time.For example the date and time an item is created useful for finding items within a date range and also as a record of when the item was created.
- #22: Column PurposesColumns may have a single purpose or more likely be used for a number of different purposes. The purpose of a Column should be defined and captured in supporting code comments and any supporting documentation. For example the purpose of a Body Content Column on a News Article Content Type is most likely needed for containing the body of the news article and also providing a record of what the body of the news article was at a given time.For example the date and time an item is created useful for finding items within a date range and also as a record of when the item was created.
- #48: Example Libraries Content Types – Bring up in Visio and walk through.
- #49: Example Lists Content Types – Bring up in Visio and walk through.