Principle 1. Help the user develop an understanding of the operation of the interface and the search process.
A well-designed interface provides assistance to the information seeker so that the person can map his or her knowledge of the topic into the system. This assistance can take a number of forms.
Principle 2. Provide information to help users judge the value of continuing a search path.
System designers should keep in mind that many people have slow network connections and that almost everyone is short on time. Thus, any clues provided to help information seekers determine the value of continuing a particular search path are useful. It might be the case that they would more readily find their search terms if browse lists were provided both in alphabetical order and as a hierarchy of subject-related search terms. These arrangements reflect different ways of thinking about the associated list.
The hierarchical list is arranged by content area with alphabetical ordering for each subcategory. If searchers were looking for a textbook for a physics class, they could find physics under either "p" in the alphabetical list or under "science" in the hierarchical list. If the search terms are only presented in alphabetical lists, as shown in Figure 3, finding the correct label for a concept can be an arduous task. Currently implementation of hierarchical lists is under development at ENC in order to provide an alternative to the alphabetical browse lists.
Another classic way to help users judge the value of continuing a query is for the system to provide the number of records associated with each vocabulary term. Knowing that there are only two records associated with Distance learning is a potent clue as to how much information the person might find on this topic in this database (Figure 3).
Results lists need to be structured in such a way that the contents of the returned record are clear (Figure 4). The information most important to the audience should be clearly displayed in the summaries. This guides the information seeker not only in selecting which records might be of interest, but also whether the search resulted in the types of information desired. The search query should be visible while scanning retrieved results.
Principle 3. Assist the user in refining the search query or search topic.
The designer can use a number of techniques. First, provide clear and simple instructions, a Help page for those interested in query construction and the ability to reset or erase a query. In addition, summarize the query on the results page so that the information seeker can be reminded exactly what was searched. Another function that is becoming popular in some engines is to generate a list of related search topics in response to a query.
Principle 4. Avoid complex navigation.
A trade-off exists between having users scroll down a page as they complete a longer query form or designing the screen so that the query fits on one page. Further complicating matters is the wide range of monitors in use today. At ENC we tried to develop a flexible workspace that minimized scrolling or paging around. As can be seen in Figures 2 and 3, frames divide the screen into work areas. As the query is constructed, terms selected appear in the middle box. The information in the bottom frame changes based on users' selections.
Principle 5. Make the system actions explicit to the information seeker.
Instructions placed near related controls show functional grouping. Analogies using familiar objects guide many interfaces. Many people intuitively know what to do when presented with a form to complete. Boxes suggest areas to type into and buttons suggest places to click. Place functions near the object acted upon. For instance, Search and Reset buttons should be placed near the query in order to suggest applicability.
Summarizing terms included in a query is a common standard for results lists, but few systems indicate whether or how Boolean operators were employed. In order for a user to understand the system's actions the query construction needs to be clarified. Sometimes this information is available through the Help pages, but frequently it is not made explicit, leaving the user to guess how the results were obtained. Not only should the information seeker see the terms used in the query, but also the operators used to form the query.
Principle 6. Provide verbal labels suggestive of meaning.
We attempted to select verbal labels that were highly suggestive of the intended meanings and functions of their associated objects. Each window has a heading which signifies the type of information associated with it. Each button is labeled with the action that will occur if it is pressed. Finally, the label for each box describes the type of information that should be entered into it. Labels such as "Grades" and "Cost" clearly suggest the contents of a category. Alternatively, labels such as "Other" do not. Even "Help" can be misleading when the context is confused. For instance, in Figure 4, will "Help" take you to the description of the Home page or to more information on query construction? An information seeker might become confused in this particular case because whether the label refers to global and local navigation is ambiguous.
Marie Shuttleworth is librarian at Eisenhower National Clearinghouse, Ohio State University, 1929 Kenny Rd., Columbus, OH 43210; 614/292-7784; e-mail: email@example.com
Phil Smith is professor, Cognitive Systems Engineering Laboratory, Institute for Ergonomics, Ohio State University, 210 Baker Systems, 1971 Neil Avenue, Columbus, OH 43210; 614/292-4120; e-mail: firstname.lastname@example.org