home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #26 / NN_1992_26.iso / spool / bit / listserv / cwisl / 1102 < prev    next >
Encoding:
Text File  |  1992-11-10  |  879 b   |  19 lines
  1. Newsgroups: bit.listserv.cwis-l
  2. Path: sparky!uunet!utcsri!newsflash.concordia.ca!garrot.DMI.USherb.CA!uxa.ecn.bgu.edu!cfkfb
  3. From: cfkfb@uxa.ecn.bgu.edu (Karl Bridges)
  4. Subject: Justification for CWIS
  5. Message-ID: <BxILCq.2y7@uxa.ecn.bgu.edu>
  6. Summary: What does CWIS do that network can't?
  7. Organization: Educational Computing Network
  8. Date: Tue, 10 Nov 1992 19:12:24 GMT
  9. Lines: 8
  10.  
  11.   I'm currently developing a grant proposal for a CWIS system for
  12. our university.  The question that comes up and for which I don't
  13. have a very articulate answer is:  What does a CWIS do that a network
  14. doesn't?  Basically, I think that a CWIS represents an easier way
  15. of accessing information e.g. it's simply one of a number of ways that
  16. an organization "packages" information to better serve its users.
  17. Has anyone else run across this question and how did you answer it in
  18. your particular situation?
  19.