Adding alot of static documents to a WSS site

I have a large number (20-50 GB) of reference documents that I need to
add to a WSS project site. These documents are for research only and
will not be edited, but they will be used in the collaboration process.
I have considered hosting these files on a separate website and
having the content indexed by the SP portal server (with the crawl for
these documents running much less frequently than for the portal and
WSS sites), but I would like to use a more integrated approach. I
don't want to stick these documents in a document library because their
content is indexed much more frequently and this would drasticly
increase the size of the content DB. Is there any more elagant
solution?

Shawn Kovalchick

Mike
Wed Aug 17 01:30:53 CDT 2005

1. If you mean by project site WSS as used by Project Server 2003 then
please post there (microsoft.public.project.server) and not here.

2. There are only two main places to store documents that I can think of
a) document library
b) as an attachment.

If my memory is right attachments are not indexed, however having to created
a text item for every document (in order to have the document as an
attachment) would be a major pain.

(and I'm not sure how a WSS site would cope with having 50GB as attachments)

A third idea: rename all your documents so they end with a .nnn name that is
not indexed because there is no IFilter for it - that might work but perhaps
not if the system works out they are in fact Word files ....

Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please reply to the newsgroup

"bamapookie" <bamapookie@gmail.com> wrote in message
news:1124292635.127256.282610@z14g2000cwz.googlegroups.com...
>I have a large number (20-50 GB) of reference documents that I need to
> add to a WSS project site. These documents are for research only and
> will not be edited, but they will be used in the collaboration process.
> I have considered hosting these files on a separate website and
> having the content indexed by the SP portal server (with the crawl for
> these documents running much less frequently than for the portal and
> WSS sites), but I would like to use a more integrated approach. I
> don't want to stick these documents in a document library because their
> content is indexed much more frequently and this would drasticly
> increase the size of the content DB. Is there any more elagant
> solution?
>
> Shawn Kovalchick
>

bamapookie
Wed Aug 17 12:59:01 CDT 2005

I was referring to a WSS site that is being used in collaboration for a
project. Not as part of a MS Project.

My first stab at a solution for the problem (I am trying out several
ways of doing this) is to store the documents in a separate file
system that is shared via IIS. I have the portal server index the file
share (so that it can retain permissions) and translate the file path
to a URL. My problem with this approach is that I now have to manage
this share separately, and I don't scale. :) I was wondering if this
might be a good use for a CMS that could then expose these static
documents to the WSS site for easy access by the site members.