Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Site Collection Architecture in SP 2007

  Asked By: Helen    Date: Jul 14    Category: Sharepoint    Views: 889

I work in a department within a mid-sized university. Our department
provides technical services to the Office for Undergraduate Education (OUE),
of which we are one part. We last fall, we put up SharePoint 2003 for OUE,
making each department within the division a subsite. Our Operations group
found some problems with that architecture; for example, each site
collection must be backed up separately.

In the course of events, uptake of SP 2003 has not been very fast; we are
now preparing to move to SP 2007 (WSS) and we have an opportunity to
rearchitect while there's not too much content. Our Ops manager asked me
whether there were changes in 2007 that would lead us to a different
architecture. My response was, "I'll ask..."

I would be very happy with some linkage to discussions of this issue; I
don't expect anyone to carve out a new response to such a big topic.



3 Answers Found

Answer #1    Answered By: Elisha Abbott     Answered On: Jul 14

Site Collections in WSS v3 become even more important. In WSS v2 Web
Parts, List Templates, Site Templates, Cross Site Groups, and a User
Info were managed in Site Collection Galleries. In WSS v3 we add to
that, Site Columns, Content Types, Master Pages, and Workflows (sorta).

The scoping decision about when to use a common Site Collection and when
to use disparate Site Collections has become even more challenging.
There are no tools to support managing Site Collection Galleries across
your enterprise (we are working on one) nor is there any way to filter
what people see in these galleries in a common Site Collection.

I prefer your current architecture  but I also empathize with you
regarding the lack of enterprise support tools.

Answer #2    Answered By: Naimish Ranganekar     Answered On: Jul 14

Your points are lucid and well-taken, as usual.

The consequence I see is that if we want to offer (e.g.) workflows, some of
which are common to all parts of OUE, and some of which are specific to a
department like the Honors College, we will have to either 1) use one site
collection, and mark the specific workflows with names like "Honors App
Form", or 2) set up separate site  collections and propagate the common
workflows across them.

Neither is what I think of as a scalable solution.

Answer #3    Answered By: Caleb Gordon     Answered On: Jul 14

Yet that is our reality. FWIW, the propagation of common workflow can be
as easy as activating a Feature in the top-level site  of each site
collection that needs them. Not too bad to support, IMO.

Didn't find what you were looking for? Find more on Site Collection Architecture in SP 2007 Or get search suggestion and latest updates.