home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!uvaarpa!darwin.sura.net!gatech!paladin.american.edu!auvm!CLARKU.BITNET!EMCDERMOTT
- X-Envelope-to: pacs-l@uhupvm1.bitnet
- X-VMS-To: IN%"pacs-l@uhupvm1.bitnet"
- Approved-By: Public-Access Computer Systems Forum <LIBPACS@UHUPVM1.BITNET>
- Message-ID: <01GTYXEIJW7S9N5T2P@vax.clarku.edu>
- Newsgroups: bit.listserv.pacs-l
- Approved: NETNEWS@AUVM.AMERICAN.EDU
- Date: Tue, 26 Jan 1993 11:06:13 CDT
- Sender: Public-Access Computer Systems Forum <PACS-L@UHUPVM1.BITNET>
- From: EMCDERMOTT@CLARKU.BITNET
- Subject: Gophers in Libraries
- Lines: 19
-
- ----------------------------Original message----------------------------
- I'm also sending this message to LIB-REF.
- Here at Clark we are just about to load PC Gopher II on some of our OPAC
- workstations. We are planning to use the Gopher as a menu to our own PAC
- as well as other sites, library news, etc. We'd like to know if anyone else
- out there has experience in using Gopher, specifically as a menu system for
- library resources. Some of our concerns: Because Gopher can connect one to
- almost anywhere in the Internet, with a high degree of ease, will we find
- patrons are tying up our OPAC workstations? How can we prevent this? Do
- we want to prevent this?; Do we need to worry about security problems? Will
- our patrons be tempted to change configurations or use the computers for non-
- library related work? How can we prevent this?
- Primarily we are interested in finding out who has experience with
- using Gophers in a library setting. Thanks in advance for your input.
-
- Ed McDermott
- Goddard Library
- Clark University
- emcdermott@vax.clarku.edu
-