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%92081410065796@WUVMD.BITNET>
- Newsgroups: bit.listserv.cwis-l
- Date: Fri, 14 Aug 1992 11:01:28 EDT
- Sender: "Campus-Wide Information Systems" <CWIS-L@WUVMD.BITNET>
- From: Richard W Wiggins <RWWMAINT@MSU.BITNET>
- Subject: Re: Multiple Items/Navigation
- In-Reply-To: Message of Thu,
- 13 Aug 1992 10:57:21 +0200 from
- <pearcera@RS6000-1.COMPUTER-CENTRE.BIRMINGHAM.AC.UK>
- Lines: 15
-
- Gopher, of course, like many other systems, allows multiple links
- to the same item. The question then becomes how often such duplicate
- links should be used. I claim that lavish duplication can turn a
- hierarchical menu into an Adventure game -- am I in the twisty maze
- of passages all alike now?
-
- In my opinion duplicate links should be minimized, and an index of
- titles provided where possible. Here at Michigan State, Dennis Boone
- has added code to Gopher to provide such an index of titles -- you
- search by keyword, and you get a list of all items with that keyword
- in the title. So no matter where we've buried "Tickets" or "Phone"
- you'll be able to find it quickly, obviating the need for duplication.
- (The index code is working but not on our production Gopher service yet.)
-
- /Rich Wiggins, Gopher Coordinator, Michigan State U
-