| 
|
QuoteRef: halaFG7_1988
topics >
all references >
ThesaHelp:
references g-h
ThesaHelp:
ACM references f-l
Group:
hypertext
Topic:
types of hypertext links
Topic:
hierarchical structures in hypertext
Topic:
searching hypertext
Topic:
implementation of hypertext databases
Topic:
using keywords to search hypertext
Topic:
problems with disorientation in hypertext
Topic:
managing changes in hypertext
Group:
problems with hypertext
Topic:
cross reference and hierarchical links in hypertext
Topic:
problems with writing hypertext
Topic:
problems with fragmentation in hypertext
Topic:
personal information
Topic:
expert users
Topic:
schemas for hypertext
Topic:
execution of hypertext nodes
Group:
object-oriented programming
Topic:
attribute-value pairs as information
Topic:
knowledge representation by frames
Topic:
archiving Information in Hypertext
Topic:
version control
Topic:
configuration management
Topic:
using hypertext for cooperative work
Topic:
shared information for collaborative work
Topic:
managing a Thesa database
Topic:
change notification
Topic:
hypertext rhetoric
Reference
Halasz, F.G., "Reflections on Notecards: Seven issues for the next generation of hypermedia systems ", Communications of the ACM, 31, 7, July 1988, pp. 836-852. Google
836 ;;Quote: NoteCards designed for idea processing and organizing information; provides a network of notecards with typed links
837 ;;Quote: a NoteCards link is typed by its relationship
838 ;;Quote: a NoteCards filebox provides hierarchical categorization for storing and retrieving notecards
838 ;;Quote: NoteCards has simple string and keyword searching
840 ;;Quote: Hypertext system dimensions are scope, browsing vs. authoring, and target task
840 ;;Quote: Hypertext systems show large differences in scale of databases and user population
840 ;;Quote: Hypertext's for authoring provide information structures for modification and creation by users
840+ ;;Quote: Hypertext's for browsing have few authors and many readers who explore an information space
841 ;;Quote: most Hypertext's are designed for a few applications
841 ;;Quote: NoteCards needs queries as well as navigational access
842 ;;Quote: even with a 500 node Hypertext, disorientation is likely; especially after change or heterogeneous structure
842+;;Quote: network changes makes it hard to find information in a Hypertext
842 ;;Quote: structure query matches subnets of a Hypertext
843 ;;Quote: in Hypertext no way to deal with groups of nodes and links as an entity
844 ;;Quote: a NoteCards filebox confuses reference relations between independent nodes with inclusion relations between a node and its components
844 ;;Quote: some writers have abandoned NoteCards in favor of outline processors since fileboxes can not be expanded or collapsed
844 ;;Quote: all Hypertext systems should support hierarchies of inclusion relations; these should be distinct from reference links
845 ;;Quote: the static network of Hypertext links causes premature organization of rapidly changing information
845 ;;Quote: many NoteCards users have trouble with segmenting ideas into cards, assigning a title, and filing into a filebox
845 ;;Quote: NoteCards structures tend to be out of date with respect to user's current understanding of the information
845 ;;Quote: experienced NoteCards users put all notes in one filebox and use a sketch card to form related piles; when stable, turned into fileboxes
845 ;;Quote: a virtual structure in Hypertext defines a view that is constructed procedurally
846 ;;Quote: a Hypertext virtual structure (views) requires a query mechanism
846 ;;Quote: NoteCards was used for CAI by script cards which controlled text display, student answers, and sequencing
847 ;;Quote: Hypertext, frame-based AI systems, and object-based systems are similar: typed, slotted, linked entities
847 ;;Quote: versioning is helpful for Hypertext but a branched version history causes difficulty for links
848 ;;Quote: PIE defines a layer as a coordinated set of changes to multiple objects; a sequence of layers is a context
849 ;;Quote: collaborative Hypertext needs simultaneous access and controlled interaction
849 ;;Quote: Hypertext requires simultaneous access to a common network
849 ;;Quote: collaborating users should be notified when important events occur to nodes or links
850 ;;Quote: rhetoric of arrival and departure needed to describe a link's relationship
850 ;;Quote: generic Hypertext is not well adapted to any specific task
ThesaHelp: references g-h (299 items)
ThesaHelp: ACM references f-l (241 items)
Group: hypertext (44 topics, 777 quotes)
Topic: types of hypertext links (19 items)
Topic: hierarchical structures in hypertext (19 items)
Topic: searching hypertext (17 items)
Topic: implementation of hypertext databases (17 items)
Topic: using keywords to search hypertext (26 items)
Topic: problems with disorientation in hypertext (18 items)
Topic: managing changes in hypertext (21 items)
Group: problems with hypertext (7 topics, 98 quotes)
Topic: cross reference and hierarchical links in hypertext (9 items)
Topic: problems with writing hypertext (12 items)
Topic: problems with fragmentation in hypertext (13 items)
Topic: personal information (40 items)
Topic: expert users (25 items)
Topic: schemas for hypertext (7 items)
Topic: execution of hypertext nodes (21 items)
Group: object-oriented programming (26 topics, 814 quotes)
Topic: attribute-value pairs as information (53 items)
Topic: knowledge representation by frames (18 items)
Topic: archiving Information in Hypertext (6 items)
Topic: version control (30 items)
Topic: configuration management (24 items)
Topic: using hypertext for cooperative work (9 items)
Topic: shared information for collaborative work (35 items)
Topic: managing a Thesa database (34 items)
Topic: change notification (19 items)
Topic: hypertext rhetoric (17 items)