home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!MSU.BITNET!RWWMAINT
- Message-ID: <CWIS-L%92081516325326@WUVMD.BITNET>
- Newsgroups: bit.listserv.cwis-l
- Date: Sat, 15 Aug 1992 17:26:12 EDT
- Sender: "Campus-Wide Information Systems" <CWIS-L@WUVMD.BITNET>
- From: Richard W Wiggins <RWWMAINT@MSU.BITNET>
- Subject: Re: Re:Cwis's with access to local libraries
- In-Reply-To: Message of Wed, 12 Aug 1992 08:50:56 EDT from <CCRMMUS@MCGILLM>
- Lines: 26
-
- >I came away from the INFORMA conference with ideas that could
- >explain your observations. The connection to the campus library
- >system does get a site into potential turf wars. This is because
- >most CWIS's are being run by computing centers...................
- >....
- >There is no technical reason why it cannot be done today. There
- >are, however significant people problems that have to be overcome
- >before this can be realized.
-
- I don't see how putting the Library system(s) on the CWIS can
- lead to turf wars. There can be contention over who gets put
- where on the root menu, and who manages the CWIS overall, but
- simply pointing to something in a menu system doesn't imply
- you've taken over ownership of it.
-
- Indeed, in the Gopher community, there is discussion of ways to
- allow the user to see who the actual owner of each item is, and
- to allow the user to provide direct feedback to that information
- provider.
-
- Anyhow, the best answer to avoiding contention is to have a broad-
- based committee resolve policy and menu design issues, and to be
- sure that appropriate library staff are involved. After all they
- have been classifying information for years.
-
- /Rich Wiggins, Gopher Coordinator, Michigan State U
-