home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!IBM3090.BHAM.AC.UK!PEARCERA
- Via: uk.ac.birmingham.computer-centre.ibm3090; Mon, 27 Jul 1992 12:09:12 +0100
- Message-ID: <27_Jul_92_12:09:25_BST_#5982@UK.AC.BHAM.IBM3090>
- Newsgroups: bit.listserv.cwis-l
- Date: Mon, 27 Jul 1992 12:09:25 BST
- Sender: "Campus-Wide Information Systems" <CWIS-L@WUVMD.BITNET>
- From: PEARCERA@IBM3090.BHAM.AC.UK
- Subject: Menu organisation
- Lines: 44
-
- The system at Birmingham also allows direct entry to any menu. In practice
- this is restricted to those menus which can be considered to be the
- starting point of a data sub-tree. In theory, this can be provided for
- every menu within the tree. Thus users don't have to 'start' at the 'top'
- and work their way down.
-
- This may well have an underside to it in that frequent callers, knowing
- precisely what they want, become less and less aware of what the tree
- looks like. (The MAP Document provides a very simple overview of the tree
- structure; the ANCHORAGE Command tells the caller where in the tree they
- are curently located.)
-
- I wonder if this raises a question about how structures are modified.
- If the caller is not required to proceed in a 'top-down' fashion, then
- it is not difficult to imagine how regular callers could be 'left in the
- lurch' if faced with a rather different-looking structure. But then,
- it's bad form to make too many radical changes, isn't it??????
- /\/\/\/\/\/\/\/\/Original message\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
-
-
- Date: Mon, 27 Jul 92 10:38:57 BST
- From: Chris Bayliss <C.B.Bayliss@UK.AC.BHAM>
- Subject: Menu organisation
- Sender: postmaster@uk.ac.bham
- To: ccc_cwis_blcmp.prj@UK.AC.BIRMINGHAM
- Original-Sender: BAYLISCB@uk.ac.birmingham.computer-centre.ibm3090
-
- Experience at Birmingham has shown that some items (including menus)
- can belong in more than one place in the tree, as different users
- will reasonably expect to find the information in different places,
- depending on the nature of their search for information.
-
- The ACSIS system solves this problem by allowing links across the tree allowing
- an item (including a menu) to be present in more than one place, without
- duplication of information.
-
- For example, Campus Mail Services and the NRS (Name Registration Scheme) menus
- are each included as items in each others menu. This can be useful for the
- user searching for mail addressing information who sees the NRS as a subset of
- mail addressing information, whilst allowing the NRS section to reside under
- the Remote Facilities subtree.
-
- The user will not necessarily be aware of the cross linking, as they will
- have found their information by following a set of menus in the normal manner.
-