| 
|
Topic: managing changes in hypertext
topics >
computer science >
database
Topic:
archiving Information in Hypertext
Topic:
change
Topic:
change notification
Topic:
database agents
Topic:
database change management
Topic:
database consistency and reliability
Topic:
managing a Thesa database
Topic:
problems with disorientation in hypertext
Topic:
using hypertext for cooperative work
Topic:
version control
Summary
Hypertext continually changes. How are readers notified of new content? How are versions identified? How are links updated?Change is inherent to hypertext. How do you allow change while maintaining some kind of structure? (cbb 4/07)
Subtopic: change notification
Quote: use versioning to preserve and update hypertext links [»ashmH9_2000]
Subtopic: site management
Quote: collaborating users should be notified when important events occur to nodes or links [»halaFG7_1988] Quote: ZOG 'find' command creates lists of all frames changed since a given date [»akscRM5_1984] Quote: users must be able to find all changes made by others to a Hypertext [»akscRM5_1984]
Subtopic: merging projects
Quote: STRUDEL separates site management and site structure with a declarative query language, and site presentation with a template language [»fernM10_1999]
Subtopic: updating links
Quote: the World-Wide Web was designed for merging independent projects without major or centralized changes [»bernT8_1994]
Subtopic: permanent link
Quote: use regular document updates to also update document links [»ashmH9_2000] Quote: use a forwarding note or gravestone for moved or deleted documents [»ashmH9_2000] Quote: use aliases to keep document links up-to-date [»ashmH9_2000] Quote: manual repair of broken document links; users can correct links themselves [»ashmH9_2000] Quote: notify users about modified document links; problem of identifying all known users [»ashmH9_2000] Quote: an application can test the validity of a link and correct the link if necessary [»ashmH9_2000]
Subtopic: relative link
Quote: permanent document links by disallowing change; e.g. legislative and judicial document collections [»ashmH9_2000]
Subtopic: computed link
Quote: use relative references to preserve internal links when moving a collection of documents [»ashmH9_2000]
Subtopic: authentication
Quote: compute links as needed, e.g., by searching for "Glasgow"; problems of incorrect context, jello view [»ashmH9_2000]
Subtopic: disorientation
Quote: a hypertext needs a fiducial system to tell which version is authentic; must avoid dangers of rewriting history or doctoring documents [»nelsTH_1974]
Subtopic: retrofitting internal anchors
Quote: even with a 500 node Hypertext, disorientation is likely; especially after change or heterogeneous structure [»halaFG7_1988] Quote: network changes makes it hard to find information in a Hypertext
Subtopic: premature organization
Quote: use embedded links to indicate the destination of a hypertext link; e.g., HTML's name=; cannot be retrofitted [»ashmH9_2000]
Quote: the static network of Hypertext links causes premature organization of rapidly changing information [»halaFG7_1988] Quote: NoteCards structures tend to be out of date with respect to user's current understanding of the information
[»halaFG7_1988]
Group: database (27 topics, 665 quotes)
Topic: archiving Information in Hypertext (6 items)
Topic: change (28 items)
Topic: change notification (19 items)
Topic: database agents (10 items)
Topic: database change management (12 items)
Topic: database consistency and reliability (15 items)
Topic: managing a Thesa database (34 items)
Topic: problems with disorientation in hypertext (18 items)
Topic: using hypertext for cooperative work (9 items)
Topic: version control
(34 items)