 | |  |  | 

The big problem with database-searching applications is that the user receives little feedback. Consider, for example, novice users starting to use Microsoft Word. The users want to right-justify a paragraph of text. Their efforts, either successful or unsuccessful, will be immediately apparent on the screen: The paragraph is either correctly justified or it isn't. However, a good-quality or a poor-quality search query used over a large database may retrieve 5,000 records, whether good or poor. How is the chemist to know whether the search query was effective and efficient? That is, how does the chemist know that the search query retrieved all and only the relevant records? View both works by Grayling, Trevor View all 350 works published by Technical Communication Online |
 If We Build It, Will They Come? A Usability Test of Two Browser-based Embedded Help Systems http://www.ingentaconnect.com/content/stc/tc/2002/00000049/00000002/art00008
access restricted (by the publisher) to members/subscribers/customers only
peer-reviewed
Grayling, Trevor Technical Communication Online 2002
Abstract: The big problem with database-searching applications is that the user receives little feedback. Consider, for example, novice users starting to use Microsoft Word. The users want to right-justify a paragraph of text. Their efforts, either successful or unsuccessful, will be immediately apparent on the screen: The paragraph is either correctly justified or it isn't. However, a good-quality or a poor-quality search query used over a large database may retrieve 5,000 records, whether good or poor. How is the chemist to know whether the search query was effective and efficient? That is, how does the chemist know that the search query retrieved all and only the relevant records?
|
 |
 |  |