Re: Best practices for where to put department sites (sps vs. wss side)?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Candice (candice.franklin_at_asia.ing.com)
Date: 06/24/04 

Date: Thu, 24 Jun 2004 02:45:30 -0700

This is more or less what we have done. Areas/Topics =
departments with public access. All doc
storage/collaboration is done at the WSS level with some
public libraries/lists and others secure. Only problem is
trying to keep users from adding a document to the area.
We are going to takle this by removing the button and also
adding links to all doc libraries of that department under
the Manage Content link of an area.
>-----Original Message-----
>The common configuration I've seen and think works best
is using the SPS
>site as an aggregate view of WSS site content. Have your
collaboration occur
>down at the WSS level and bubble up whatever public info
you want into the
>SPS areas. This way you can target content using audience
filtering but have
>your contributors work in a web based collaboration
space. There are pros
>and cons with both approaches but this keeps things
simple for the most
>part.
>
>--
>Bil Simser
>Development Evangelist
>Microsoft MVP - SharePoint Portal Server
>http://weblogs.asp.net/bsimser
>
>
>"Scott" <anonymous@discussions.microsoft.com> wrote in
message
>news:1e3e001c45576$5e49e720$a301280a@phx.gbl...
>> Hey everyone, I'm delurking here hoping to get general
>> guidance... ;-)
>>
>> We're getting ready to roll on an SPS implementation,
and
>> while many of the capabilities of WSS sound great to the
>> stakeholders, we are really struggling with our
>> information architecture design.
>>
>> In the past we had an 'intranet' running on IIS, with
>> pages linked to the document library function of the
>> earlier version of sharepoint. We didn't use team
services
>> at all.
>>
>> Now we're planning to use SPS to replace the 'intranet'
>> and integrate document storage into SPS and WSS sites
(and
>> of course make use of the collaboration tools).
>>
>> Along with true topical areas, we're planning to make
>> department pages SPS Areas, but I'm very concerned
about a
>> few things in this scenario:
>>
>> 1. Some documents are 'general' and can easily be put
into
>> an area document library, but many aren't, and so would
>> require sub-areas (given the permissions connection to
the
>> area). This would seem to lead to the creation of many
sub-
>> areas.
>>
>> 2. Following from the above, aside from true
collaboration
>> sites, there is going to need to be a handoff point from
>> SPS Areas to WSS sites, but where do you draw the line,
>> and what are the consequences in terms of training end
>> users?
>>
>> 3. Or, is this entirely the wrong approach, and should
we
>> stick to Topics etc., on the SPS side and put all
>> department sites and their associated documents on the
WSS
>> side?
>>
>> Are there any best practices outlined somewhere? Or, at
>> least some concrete scenarios with possible
consequences?
>> This seems to be a decision that we will have to live
>> with, so we don't want to make the wrong one.
>>
>> What have you done? What do you suggest as to how to
get a
>> good handle on the standard/best practices here so that
we
>> can make a good decision?
>>
>> Thanks,
>> Scott
>
>
>.
>

Quantcast