Re: Using documents from libraries in Team Sites
- From: "Engelbert" <Engelbert@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 15 Jan 2006 16:55:37 +0200
Here's a brief note on the last points.
The easy one first. You create Data Access web parts by opening the site in
FrontPage 2003 (you'll find that you'll need FP 2003 anyway not only for
this) and going in the menu line to Data etc.
You can access lists with it that are anywhere on the server that is running
WSS and also access the databases of WSS sites on other servers
It's a nice way to create *a view* on a web page of documents stored
elsewhere - it does NOT **populate** those libraries with documents stored
elsewhere. As before that isn't the point, a document should only be stored
in one location but linked to from elsewhere.
Meeting / Document workspaces and Team / Basic Sites are all different.
They include different web parts. You will in certain cases find it
difficult (or impossible) to add to one type of Site (i.e. based on one type
of template) a web part that is standard in another.
To take only the simplest example a Basic Site isn't just a Team Site
showing an emptier page, it's a Team Site minus a lot of the web parts -
i.e. the web parts aren't just not used on the default page they aren't even
there. This catches a lot of people out.
Hope these help while doing your research.
Engelbert
"Nestor" <Nestor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4F393865-C66C-4A10-BA71-F4402F38D8DB@xxxxxxxxxxxxxxxx
> Engelbert:
> Thanks for your patience. It's obvious that I need to do more research
> into
> the product to get a better understanding of the inter-relationships and a
> "face to face" with knowledgeable individual would help.
> a) Got your clarification on WSS vs SPS 2003. Yup, the latter is the
> trial
> I am using.
> b) I'm pretty sure I'm OK with the Document Library concept (I am in the
> Legal industry and have been around the more traditional document
> management
> systems forever)
> c) Let's ignore Meeting sites for the time being--I understand their use
> and how they "fit" into things.
> d) Which brings us to Team and Meeting Sites. Team Sites (based on the
> Team template) appear to me to look essentially like the Baseline page.
> Meeting Sites contain more elements such as Tasks, Agendas, Attendees,
> etc.
> I assume that through the use of Web Parts, these can be modified to add
> or
> delete these elements. I work for a consulting firm. We have clients
> from
> whom we get repeat business. I would like to have a single document
> library
> for each client's documents as they accumulate through the years. Within
> the
> libraries will be appropriate sub-folders relating to the individual
> engagements. Separately, I would like to create Meeting or Team pages (or
> hybrids if necessary) that are engagement specific that a team would use
> to
> collaborate during the engagement. However, I would want the various
> Team/Meeting sites to deposit and retrieve documents from a common
> document
> library specific to that client. Right now, it appears to me that each
> webpage has its own document library and there is no "out of the box"
> ability
> to populate those libraries with documents that already exist in another
> document library. You mentioned a "Data View Web Part" which I wasn't
> able
> to quickly find, but perhaps that's the mechanism.
> Thanks again.
> Nestor
>
>
> "Engelbert" wrote:
>
>> Windows SharePoint Services is a free download so there isn't a 30-day
>> trial
>> version available as one isn't needed.
>>
>> So, can you please check again. There *is* a limited time version of
>> SharePoint Portal Server 2003.
>>
>> On b) document libraries are independent entities that contain their own
>> documents. Attachments offer a way to link from one List item to a
>> document
>> in another document library as do Link libraries. Another way to see
>> documents for doc lib A elsewhere in the site structure is to create a
>> Data
>> View Web part (with FP 2003) that access that other document library and
>> lists the documents from it. In all these scenarios however the document
>> remains in the same single location (and this is the intention).
>>
>> If you are indeed using SPS 2003 then you have other possibilities of
>> grouping links of relevant documents such as Areas (but the SPS newsgroup
>> know more about that). There again however the document remains in its
>> one
>> document library.
>>
>> In short: a) documents are stored in one location in one document library
>> b) there are many ways of being able to access the document
>> (read-only) from many other locations.
>>
>> I hope this helps.
>>
>> Engelbert
>>
>> P.S. Perhaps you'd better also say why you are using a Meeting Workspace
>> and
>> not a standard Team Site.
>>
>
.
- References:
- Re: Using documents from libraries in Team Sites
- From: Engelbert
- Re: Using documents from libraries in Team Sites
- From: Engelbert
- Re: Using documents from libraries in Team Sites
- Prev by Date: Sharepoint V3 Beta
- Next by Date: Re: Sharepoint V3 Beta
- Previous by thread: Re: Using documents from libraries in Team Sites
- Next by thread: Re: IIS and SQL DB
- Index(es):
Relevant Pages
|
