NetNews Usenet Archive 1992 #26/NN_1992_26.iso/spool/bit/listserv/cwisl/1103

Text File | 1992-11-10 | 1.9 KB | 36 lines

Comments: Gated by [e-mail]
Path: sparky!uunet!stanford.edu!unixhub!fnnews.fnal.gov!overload.lbl.gov!zeus.ieee.org!europa.asd.contel.com!paladin.american.edu!auvm!EMORYU1.CC.EMORY.EDU!LIBCGF
Return-Path: [e-mail]
Message-ID: <[e-mail]>
Newsgroups: bit.listserv.cwis-l
Date:         Tue, 10 Nov 1992 16:35:11 -0500
Sender:       "Campus-Wide Information Systems" <[e-mail]>
From:         Charles Forrest <[e-mail]>
Subject:      Re: Justification for CWIS
Comments: To: "Campus-Wide Information Systems" <[e-mail]>
In-Reply-To:  <[e-mail]>
Lines: 22

In response to Karl Bridges,
    The little I know about CWIS's suggests to me that developing a
CWIS is a way of making information accessible in machine-readable or
networkable form, which might not otherwise be available that way. A group
has been building a gopher, and our systems librarian suggested the other
day that since any gopher could talk to any other gopher invisibly, the
kind of information on CWIS could be delivered by individual gophers all
over campus--to other gophers on campus, or anywhere else.
    But I just wonder how many of the units that might be in a
position to supply cwis-able information--schedules of events, notices of
meetings, whatever--would be in a position to "gopher-ize" that
information themselves. Perhaps someday, but it might be that the way to
package a CWIS right now is as a way-station on the path to a network
where information is exchanged desktop-to-desktop, with little in the way
of "central" information services.
    Good luck.

--
FROM - Charles Forrest           VOICE  404-727-0137
       Woodruff Library            FAX  [phone]
       Emory University         BITNET  libcgf@emoryu1
       Atlanta, GA   30322    INTERNET  [e-mail]