Lesson plan

NoteCards

NoteCards was a hypertext-based personal knowledge base system developed at Xerox PARC by Randall Trigg, Frank Halasz and Thomas Moran in 1984. NoteCards was developed after Trigg's pioneering 1983 Ph.D. thesis on hypertext while at the University of Maryland College Park. NoteCards was built to model four basic kinds of objects: notecards, links, browser card, and a filebox. Each window is an analog of a cue card; window sizes may vary, but contents cannot scroll. Local and global maps are available through browsers. There are over 40 different nodes which support various media. NoteCards was implemented in LISP on D-machine workstations from Xerox which used large, high-resolution displays. The NoteCards interface is event-driven. One interesting feature of NoteCards is that authors may use LISP commands to customize or create entirely new node types. The powerful programming language allows almost complete customization of the entire NoteCards work environment.

Back to article

Article summary

NoteCards was a hypertext-based personal knowledge base system developed at Xerox PARC by Randall Trigg, Frank Halasz and Thomas Moran in 1984. NoteCards was developed after Trigg's pioneering 1983 Ph.D. thesis on hypertext while at the University of Maryland College Park. NoteCards was built to model four basic kinds of objects: notecards, links, browser card, and a filebox. Each window is an analog of a cue card; window sizes may vary, but contents cannot scroll. Local and global maps are available through browsers. There are over 40 different nodes which support various media. NoteCards was implemented in LISP on D-machine workstations from Xerox which used large, high-resolution displays. The NoteCards interface is event-driven. One interesting feature of NoteCards is that authors may use LISP commands to customize or create entirely new node types. The powerful programming language allows almost complete customization of the entire NoteCards work environment.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.