home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!bu.edu!wupost!zaphod.mps.ohio-state.edu!sdd.hp.com!nigel.msen.com!emory!europa.asd.contel.com!paladin.american.edu!auvm!MSU.BITNET!RWWMAINT
- From: RWWMAINT@MSU.BITNET (Richard W Wiggins)
- Newsgroups: bit.listserv.cwis-l
- Subject: Building a CWIS; distributed CWIS model
- Message-ID: <CWIS-L%92111111271369@WUVMD.WUSTL.EDU>
- Date: 11 Nov 92 17:11:32 GMT
- Sender: "Campus-Wide Information Systems" <CWIS-L@WUVMD.BITNET>
- Lines: 22
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- In-Reply-To: Message of Wed, 11 Nov 1992 10:05:32 EST from <JEFF@UTCVM>
-
- It's interesting hearing others use the term "evangelism" w/r/t building
- a CWIS. That's exactly what I tell people, even during the sermon.
-
- A lot of providers want to know if the CWIS is already THE place people
- go for information -- eg "If I post this document online now, can I be
- sure students will read it?" There are two answers to that: 1) You can
- never be sure anyone will read a document; we're just providing an
- alternative medium for delivering it. 2) We do expect that at a certain
- critical mass of information the community will think of the CWIS
- (Gopher in our case) as the first place to look for documents.
-
- As to distibuting CWIS information: Gopher certainly does allow true
- distributed CWIS deployment. While we are not discouraging other campus
- units from running their own Gophers, we do point out the costs and
- risks. If a Gopher on someone's desktop is down, users will not be able
- to get the data they need when they need it. All the "production" data
- in our central Gopher resides on server(s) in our machine room. We try
- to make e-mail and FTP avenues of updating convenient enough for the
- providers so that it's no harder to post on our central Gopher server
- than it would be to post on their own.
-
- /Rich Wiggins, Gopher Coordinator, Michigan State U
-