SharePoint Information Architecture AppliedBy Bob MixonCollectiveKnowledge Solutions, Inc.
About Bob MixonDelivering business solutions for more than 30 yearsFocusing on business process improvement, documentmanagement, knowledge management, collaboration and portalsMicrosoftSharePoint MVP2006, 2007, 2008, 2009, 2010Specializing In Strategic Content Management Knowledge Management Document Management Content Choreography Records Management Business Social Collaboration Governance Business Process Managementand Automation Intranet IMS, DMS, DAM, KMSand Collaboration PortalImplementation Training SpeakingCollectiveKnowledge Solutions, Inc.Founder of CollectiveKnowledge Solutions, Inc.Senior SharePoint Information Architect
Agenda• High-level Process Overview• Site Structure Taxonomy• Content Types (Data Taxonomy)• Content Type Hub (Enterprise Data Taxonomy)CollectiveKnowledge Solutions, Inc.
High-level IA Process OverviewEducate•Educate team onProcessAssessment•Audit Content•RequirementsDesign•PrimaryDestinations•Site Structure•NavigationStructure•Data Taxonomy•MetadataImplement•Web Apps•Site Collections•Content Type Hub•Local SiteCollection ContentTypes•MetadataMigrate•Content migrationeffortsEducate•Educate team onnew solutionOur Focus Today
Site Structure Taxonomy• IA plays a significant part when designing aSite Structure Taxonomy– Reduce the question “where do I store andmanage this content?”• Store and manage content, of similar topic, ina central location (use grouping principals)– Example: All HR content in the HR sitecollection, all IT content in the IT sitecollection, etc.CollectiveKnowledge Solutions, Inc.
Site Structure TaxonomyExample Logical Design ModelPrimary DestinationsCollectiveKnowledge Solutions, Inc.
Site Structure TaxonomyExample Logical Design ModelBusiness Operations Web ApplicationCollectiveKnowledge Solutions, Inc.
SharePoint Site TaxonomyIntranet Example• A common mistake is to store and managecontent to support consumersCollectiveKnowledge Solutions, Inc.IntranetDepartmentsHumanResourcesOperationsResourcesCorporatePoliciesCorporateFormsStoring all corporate policy documents in this site isproblematic!1. Requires content owners to mark another sitesto manage their content.2. Promotes use of item-level security.
SharePoint Site TaxonomyIntranet Example• Store and manage content as close to thepoint of topic/ownership as possible– Group content based on topic/ownership; notconsumption• Once you architect your information (throughcategorizing and metadata principals) you can:– Consumer content grouping and views can beproduced through querying– Highly relevant results can be produced by searchusing scopes and faceted filteringCollectiveKnowledge Solutions, Inc.
SharePoint Site TaxonomyIntranet Example• Consider a different approachCollectiveKnowledge Solutions, Inc.IntranetDepartmentsHumanResourcesHumanResourcesPoliciesOperationsOperationsPoliciesResourcesCorporatePoliciesCorporateFormsCorporate Policies site is simplya point of aggregation.Corporate Policy documents arequeried based on content type;Corporate Policy Document.Human ResourcePolicies are stored andmanaged in the HumanResources destination.Operations Policies arestored and managed inthe Operationsdestination.Query policy documents based on Corporate PolicyDocument content type.
Content TypesA Quick Refresher• Provide a means of centralmanagement• Will enforce the types of content thatcan be managed in a list or library• Will consistently enforce themetadata associated with specificcontent• Document content types can refer toa specific document template• Associate workflow• Associate policies• Content types are hierarchicalCollectiveKnowledge Solutions, Inc.Content Types are a schema used to define the types of content you wish tomanage in your solution!All content stored in SharePoint is associated with a Content Type
Content Type Taxonomy• Content Types are used to categorize the typeof content to be stored in SharePoint– Some confuse this with the use of metadata• Metadata is instance specific!• Don’t fear creating deep Content Typetaxonomies (hierarchy)– Each level can be used for aggregate scoping• Can improve aggregate relevancy to support variousbusiness contextual needsCollectiveKnowledge Solutions, Inc.
Content TypeExampleCollectiveKnowledge Solutions, Inc.
Content Type TaxonomyExampleCollectiveKnowledge Solutions, Inc.
Content TypesBest Practices• Never modify a SharePoint out-of-box contenttype• Avoid organizational taxonomy– Difficult and time consuming to re-base a content type• Use a consistent naming convention– Consider “Document” suffix for all document contenttypes• Govern design, implementation and use• Educate users as to the valueCollectiveKnowledge Solutions, Inc.
Content TypesWhen to Create Content Types?• When you wish to govern specific types ofcontent– Specify what types of content can be stored in specificlists and libraries• When you need to include specific metadata• When you wish to associate a specific documenttemplate• When you wish to associate specific workflow• When you wish to specify policies– Such as for records managementCollectiveKnowledge Solutions, Inc.
Content Type HubEnterprise Content Types• Centrally manage content types andpublish them to subscribed sitecollections• Consider a dedicated site collection forEnterprise CTHCollectiveKnowledge Solutions, Inc.
Content Type HubThings to Remember• Republish after all changes• Cannot publish a content type that hasmanaged metadata column associated with aterm set defined in the hub• Govern the implementation, maintenance anduse of content types derived from the hubCollectiveKnowledge Solutions, Inc.
Advantages of Doing All This IA Work?• Reduce the question “where do I store andmanage my content”• Product highly relevant aggregate content• Product highly relevant search results• Provide aggregate and search refinement(scopes)• Provide further refinement through facetedfiltering
Join us right after the event at the Firehouse Grill!Socialize and unwind after our day of learning.1765 E. Bayshore RoadEast Palo Alto, CA