AggregateSite Content Across Site Collections without Custom Code<br />Matt Bremer<br />Solutions Architect - Covenant Technology Partners<br />
Agenda<br />Site collection overview<br />Scenario<br />Why search?<br />Solution overview<br />Demo<br />Review<br />Q & A<br />
Site Collection Overview<br />Web Application<br />Root Site Collection<br />Addl. Site Collection<br />
Advantages<br />Multiple content databases<br />Distributed administration<br />Unique security<br />Unique navigation<br />Unique theme/brand<br />Site quota templates<br />Unique content deployments<br />Dedicated recycle bins<br />Dedicated search settings<br />
Disadvantages<br />Additional administrative effort<br />Unique navigation<br />Unique theme/brand<br />Aggregating content across site collections difficult out of box<br />
Scenario<br />Adventure Works Corporate Intranet<br />Publishing Portal Template<br />Marketing Site<br />Product Sites<br />Collaboration Portal Template<br />Each product has own site collection<br />Each product site collection hosts a marketing team site where sales brochures are generated<br />Custom content type used for all sales brochures<br />
Scenario<br />Business Requirements<br />Aggregate all product sales brochures into corporate intranet marketing site<br />Only product marketing groups should have permission to create and edit their respective sales brochures<br />
Why Search?<br />Available at SSP level<br />Security trimming<br />Extensible<br />
Solution Overview<br />Search Core Results Web Part<br />Configurable via UI<br />Disadvantages<br />Data View Web Part<br />Configurable only via SharePoint Designer<br />Disadvantages<br />
Demo <br />Where’s the code???<br />
Review<br />Search is ideal OOB solution<br />No custom code required<br />Extensible<br />Optimized<br />Security trimming<br />Some additional scenarios<br />Employee directory<br />Calendars<br />Portal content in MySites<br />Endless possibilities<br />
Q & A<br />It’s now time for “Stump the Presenter”!<br />
Resources<br />SharePoint MVP Dan Attis<br />http://www.devcow.com/blogs/jdattis/archive/2007/04/17/SharePoint-2007-How-to-Rollup-Content-from-multiple-Site-Collections.aspx<br />Shameless Self Promotion<br />Blog: http://blogs.msdn.com/mattbremer<br />Twitter: http://www.twitter.com/mattbremer<br />Email: firstname.lastname@example.org<br />
Contact Me<br />Snap bar code below to download my vCard to your mobile phone<br />Visit http://www.microsoft.com/tag for more information<br />
1. Poll audience for how many developers vs. administrators.2. Pollaudience for who has run into this issue before.
Poll audience for familiarity with Site Collections (e.g. how many have used multiple site colls. in a web app.?)Site collections are stored within web applications. (click)All web applications have a root site collection. (click)Site collections are not hierarchical. (click)Additional site collections are stored at same level as root site collection.Hierarchies can be implied through the use of managed paths.Cover site collection architecture and note how diagram boxes them off.
As you can see there are many advantages to leveraging site collections.I recommend at least 2 site collections per web app. (1 for “control”, 1 for collaboration)Does collaboration occur in “control”, sure but they are typically sites where users do their jobs thus this needs to be “controlled” by knowledge management personnel.Collaboration site coll. is less structured and more conducive to creativity.
Unique navigation easily overcome by custom sitemap provider.Unique theme/brand easily overcome by leveraging features.OOB difficulties- CQWP, Site Aggregator and TOC web parts are limited to one site collection.- Site Directory requires additional configuration as Master Site Directory.Good outweighs the bad.
Consider Adventure Works, the world’s largest outdoor equipment manufacturer and reseller. (click)Corp. intranet utilizes publishing portal enterprise template and only has 1 site collection.Marketing department site is utilized by corporate marketing managers to share information to rest of company. (click)Product sites utilize the collaboration portal enterprise template.
Content Query Web Part only aggregates within a site collection.CQWP requires publishing infrastructure.SSP level means that site collection barriers are moot.Search indexes respectitem level security.XSL allows for highly customized display of results.
Search Core Results Limitations:Only 100 results per page.Only 6 per page due to Cross Web Part Query ID property limitations. This connects other web parts to results part (e.g. paging).DFWP LimitationsNeed to consider that editing a page in SPD automatically makes it customized and requires you to detach it from page layout.Discuss customized vs. uncustomized. Uncustomized files are provisioned to WFE from content DB in the form of templates, most efficient (previously referred to as ghosted files)Customized files are files where the content lives exclusively in content DB, less efficient (previously referred to as unghosted files)Explain how to add DVWP and keep a page uncustomized. (e.g. export web part by creating hidden dataviewpage in site to use SPD on)
Today we will implement the Search Core Results Web Part on the marketing intranet site to aggregate sales brochures from the collaborative product marketing sites without writing any custom code.Will also demonstrate how to use DVWP to do the same and demonstrate how to customize results.
Employee Directory: mention how search core results is not ideal here as you would likely need more than 100 records per page.
I first read about this approach from SharePoint MVP Dan Attis.Visit my blog in the coming weeks for walkthroughs of everything covered here today. Demo will also be available on EndUserSharepoint.com in the coming weeks.
Poll audience on familiarity on MS Tag. Provide demo of Microsoft Tag using Windows Mobile device.Talk about potential applications in SharePoint.