| 
|
QuoteRef: akscRM7_1988a
topics >
all references >
ThesaHelp:
ACM references a-e
ThesaHelp:
Thesa(tm) - a thesaurus of ideas
ThesaHelp:
references a-b
Topic:
examples of hypertext systems
Topic:
user-centered design
Topic:
hypertext nodes
Topic:
hypertext links
Topic:
hierarchical structures in hypertext
Topic:
outlines
Topic:
cross reference and hierarchical links in hypertext
Group:
user interface for hypertext
Topic:
tiled vs. overlapping windows
Topic:
information retrieval by following links
Topic:
interactive response time
Topic:
defensive programming
Topic:
user interface tool kits
Topic:
editor as the UserInterface
Topic:
execution of hypertext nodes
Topic:
modes in a user interface
Topic:
mouse buttons
Topic:
names defined by context
Topic:
current position in a user interface; cursor
Topic:
dragging with a mouse
Topic:
editing by cut and paste
Topic:
spatial metaphor in user interfaces
Topic:
scrolling a window
Topic:
attachment of hypertext links
Topic:
selecting with a mouse
Topic:
display of hypertext links
Topic:
problems with writing hypertext
Topic:
hypertext rhetoric
Topic:
types of hypertext links
Topic:
managing a Thesa database
Topic:
archiving Information in Hypertext
Topic:
frozen representation
Topic:
menus for a UserInterface
Topic:
size of hypertext nodes
Topic:
linearization of hypertext
Topic:
hypertext browser
Topic:
problems with disorientation in hypertext
Topic:
history list in hypertext
Topic:
hypertext nodes made of names
Topic:
searching hypertext
Topic:
user profile
Topic:
optimistic update for concurrency control
Topic:
security by access rights
Topic:
limitations of system security
Topic:
discussion groups, mail conversations, and teleconferencing
Topic:
using annotations in hypertext
Topic:
electronic news and blogs
Topic:
attachments to electronic mail
Group:
electronic mail
Topic:
mental models, consistency, and interface metaphors
Topic:
identifying the user interface with the system
Reference
Akscyn, R.M., McCracken, D.L., Yoder, E.A., "KMS: A distributed hypermedia system for managing knowledge in organizations ", Communications of the ACM, 31, 7, July 1988, pp. 820-835. Google
Notes
for full text of paper see akscRM7_1988
821 ;;Quote: ZOG and KMS used for over ten thousand person-hours while creating over fifty thousand frames
821+;;Quote: ZOG and KMS developed iteratively with scores of intermediate versions
821 ;;Quote: a KMS frame contains text, graphics and image items; maybe linked to another frame or program
822 ;;Quote: KMS items can be linked to another frame or to a program (or both)
822 ;;Quote: a KMS frame: title, tree items, command items, name, body, annotation items
822 ;;Quote: most KMS databases are strongly hierarchical
822 ;;Quote: the 'skeleton' for a KMS database is a multi-level hierarchy
822 ;;Quote: top levels of the KMS hierarchy is an index; lower levels represent documents and task-related groups of information
822 ;;Quote: KMS users freely supplement hierarchies with cross-references, comments, versions, and shared information
822 ;;Quote: KMS screen normally split into two page-size frames; full screen used for complex diagrams
822 ;;Quote: KMS users navigate by pointing at items linked to another frame; takes half a second
822 ;;Quote: KMS automatically saves changes when leaving a frame
822+ ;;Quote: KMS's UserInterface consists of an editor for manipulating frames and navigating
822 ;;Quote: create a new KMS frame by clicking on an unlinked item
826 ;;Quote: KMS programs often process a hierarchy of frames; e.g., a document is generated from a hierarchy
826 ;;Quote: KMS has a context sensitive mouse with button labels attached to the cursor
826+ ;;Quote: button labels for a mouse used by novices to learn a system and by experts subliminally
826 ;;Quote: KMS 'move' command attaches an item to the cursor; anything can be done before anchoring the item
826+ ;;Quote: move by cursor attachment eliminates a clipboard with cut and paste
827 ;;Quote: a KMS frame is empty space to be occupied; different from space in an editor
827 ;;Quote: space around items makes them easy to recognize
827 ;;Quote: empty space in KMS is useful for annotations
827 ;;Quote: KMS has a fixed frame, smaller than the screen; reduces reliance on scrolling
828 ;;Quote: source of a KMS link is a text item; the text item usually describes the destination
828 ;;Quote: over 90% of executed KMS commands by pointing at an item
828 ;;Quote: if Hypertext links embedded in text then phrases must fit; if linearization the phrase must be ordered correctly
828 ;;Quote: the destination of a KMS link is the whole frame; small frames make this sensible
828 ;;Quote: KMS has tree items (structural) and annotation items (associative)
829 ;;Quote: KMS can freeze a hierarchy of frames; whenever a frozen frame is modified, the original version is saved
829 ;;Quote: point-and-click is 90% of a user's interaction with KMS; twice as fast as menu selection
829 ;;Quote: KMS only provides a half-screen or full-screen display
829 ;;Quote: fast link following is the most important parameter for Hypertext; goal is quarter second; twentieth second is too fast
829 ;;Quote: following a KMS link replaces the current frame with a new frame
830 ;;Quote: KMS average frame is a kilo byte, large frame is 4.5 kilo bytes
830 ;;Quote: visual regularity of KMS frames makes it easier to perceive components and use frames
830 ;;Quote: KMS defines a linear view of a hierarchy of frames; otherwise breadth-first view of the hierarchy
830 ;;Quote: KMS does not have a graphical browser; multi-node views were available but seldom used in ZOG
831 ;;Quote: disorientation problem is minimal in KMS due to features that maintain orientation and allow re-orientation
831 ;;Quote: KMS flags previously used item
831 ;;Quote: KMS can search for text strings within a hierarchy of frames; produces a frame of titles
831 ;;Quote: users want to tailor their UserInterface
832 ;;Quote: KMS frames average two paragraphs of content
832 ;;Quote: KMS users rarely modify the same frame at the same time
832 ;;Quote: if update conflict, KMS creates a new frame for manual recovery
832 ;;Quote: KMS checks for update conflicts when frame is first modified
832 ;;Quote: informal locking in KMS by writing an 'in use' item
832 ;;Quote: owner of a KMS frame can make it read or write protected
832 ;;Quote: a KMS frame can be annotate only but most frames are left unprotected to encourage correction of typos
832 ;;Quote: KMS users grow a conversation rather than use electronic mail or bulletin boards
832 ;;Quote: ease of commenting encourages KMS users to comment, move comments, and comment on comments
833 ;;Quote: KMS bulletin board is a public frame of signed messages, perhaps linked to other frames
833 ;;Quote: KMS users have a mail box frame; messages created or appended to existing messages
833 ;;Quote: discussion frame started if several messages appended together
833 ;;Quote: KMS discussion frame if related comments; provides context for holding a conversation
834 ;;Quote: KMS annotations added directly to frame, much better than using a different frame; latter can be moved to a more appropriate frame
834 ;;Quote: like HyperCard, KMS includes a block-structured programming language with actions for creating and manipulating KMS structures
834 ;;Quote: use keyword annotations to control format for linearizing KMS hierarchies
834 ;;Quote: the data model underlying an interactive system determines its 'look and feel'
ThesaHelp: ACM references a-e (259 items)
ThesaHelp: Thesa(tm) - a thesaurus of ideas (13 items)
ThesaHelp: references a-b (396 items)
Topic: examples of hypertext systems (25 items)
Topic: user-centered design (65 items)
Topic: hypertext nodes (19 items)
Topic: hypertext links (45 items)
Topic: hierarchical structures in hypertext (19 items)
Topic: outlines (16 items)
Topic: cross reference and hierarchical links in hypertext (9 items)
Group: user interface for hypertext (5 topics, 110 quotes)
Topic: tiled vs. overlapping windows (21 items)
Topic: information retrieval by following links (23 items)
Topic: interactive response time (32 items)
Topic: defensive programming (22 items)
Topic: user interface tool kits (31 items)
Topic: editor as the UserInterface (10 items)
Topic: execution of hypertext nodes (21 items)
Topic: modes in a user interface (40 items)
Topic: mouse buttons (12 items)
Topic: names defined by context (36 items)
Topic: current position in a user interface; cursor (23 items)
Topic: dragging with a mouse (17 items)
Topic: editing by cut and paste (8 items)
Topic: spatial metaphor in user interfaces (33 items)
Topic: scrolling a window (9 items)
Topic: attachment of hypertext links (16 items)
Topic: selecting with a mouse (44 items)
Topic: display of hypertext links (15 items)
Topic: problems with writing hypertext (12 items)
Topic: hypertext rhetoric (17 items)
Topic: types of hypertext links (19 items)
Topic: managing a Thesa database (34 items)
Topic: archiving Information in Hypertext (6 items)
Topic: frozen representation (6 items)
Topic: menus for a UserInterface (31 items)
Topic: size of hypertext nodes (8 items)
Topic: linearization of hypertext (23 items)
Topic: hypertext browser (23 items)
Topic: problems with disorientation in hypertext (18 items)
Topic: history list in hypertext (26 items)
Topic: hypertext nodes made of names (13 items)
Topic: searching hypertext (17 items)
Topic: user profile (16 items)
Topic: optimistic update for concurrency control (35 items)
Topic: security by access rights (38 items)
Topic: limitations of system security (39 items)
Topic: discussion groups, mail conversations, and teleconferencing (29 items)
Topic: using annotations in hypertext (13 items)
Topic: electronic news and blogs (25 items)
Topic: attachments to electronic mail (4 items)
Group: electronic mail (12 topics, 170 quotes)
Topic: mental models, consistency, and interface metaphors (49 items)
Topic: identifying the user interface with the system (16 items)