Introduction
Now that we are in the digital age, there is a glut of information and more being created every second. The internet has enabled these phenomena as it is used as a creative outlet, storage site, and distribution center for information. However, the problem is whether said information is organized and stored in an easily retrievable way. If it is not, then it can be near impossible to find an ambiguously labeled image, video, text, or post. For information professionals, we have to be able to locate the right information for people quickly. We depend on information retrieval systems to do so. According to Reitz (2014), information retrieval is:
The process, methods, and procedures used to selectively recall recorded information from a file of data. In libraries and archives, searches are typically for a known item or for information on a specific subject, and the file is usually a human-readable catalog or index, or a computer-based information storage and retrieval system, such as an online catalog or bibliographic database. In designing such systems, balance must be attained between speed, accuracy, cost, convenience, and effectiveness.
Design
The design of an information retrieval system is predicated on who will be using it because it needs to be intuitive enough so that the user can navigate it without any confusion and can find what they seek. Weedman (2018) states that, “Both the content of the underlying collection of documents and the requirements for what the IR [information retrieval] system must do derive directly from the information needs of their users” (p. 122). For instance, libraries use information retrieval systems to catalog the materials they own in an Online Public Access Catalog (OPAC). The classification system a library chooses is dependent on the amount of detail they need. Public libraries are more general in scope, so they use the Dewey Decimal Classification system whereas academic libraries focus on specific fields of study, so they utilize the Library of Congress Classification system. Both of these systems have subject headings that start broad and narrow down into more specific categories. The metadata for each library item is put into a Machine Readable Cataloging (MARC) record. Taxonomies are the other method of organization for information retrieval systems. Retail websites use taxonomies to organize their wares into related categories. For example, clothes may be separated into men, women, boys, and girls sections. Then within those sections, there are categories for shirts, pants, outerwear, underwear, shoes, and accessories, which are further narrowed down into subcategories.
Query
Search queries are how a user navigates an information retrieval system to find the item or topic they are looking for. In a library’s OPAC the user can search for items by fields like keyword, title, author, subject heading, series, or some other field. The keyword search will yield information that can be found in any of the other fields, and it may pull up more results than a person can reasonably sift through. The user has a few options for narrowing their search results in this case. They can make their search perimeters more specific via choosing a field, putting in the exact information as it would appear in the record or use filters. OPACs have filters for format, content, audience, genre, topic, author, language, published date, and more. There may even be an option to use advanced search which has Boolean operators (AND, OR, NOT) and makes filters and fields more obvious. Alternatively, information retrieval systems may support truncation, wildcards, proximity operators, and phrase searching in their search queries too. On a retail webpage, there is a search bar that functions as a keyword search. Sometimes it may have predictive text to help people find the right term as they type. However, this type of taxonomic information retrieval system encourages the user to browse for information rather than to search for it. OPACs can be browsed as well, but the search function is much more robust.
Evaluation
Unwieldy information retrieval systems can make users frustrated and they may give up on trying to utilize them. Therefore, evaluating how user-friendly an information retrieval system is imperative to its success. Some evaluative questions could be: Does the user understand how to use the information retrieval system? Was the user able to find what they were looking for? How long did it take them? Did they need to ask questions? Did the terms they used to match the terms the system cataloged the items as? Is the user satisfied with their experience in using the system? Answers to these questions can help improve the design of information retrieval systems. Libraries want patrons to use their OPAC and to rely on library websites for information. This is only possible if the user is satisfied with the information retrieval system library provides. Similarly, retailers want customers to buy their products, so their taxonomic websites need to be fully functional and intuitive.
INFO 202 - Project 1: Alpha Prototype
This database my group created for my Information Retrieval System Design course demonstrates my competency in designing, querying, and evaluating an information retrieval system. Our database cataloged various yogurt brands for adult consumers to reference. The user could search for yogurts under fields for the base, price, texture, total fat, brand, total carbohydrates, type, and flavor. They could also narrow the search by field values. This project taught me how to design a database and how to choose what information would make the most sense to the user as they search for information. We also had a search function, and we evaluated it before we submitted our assignment for beta testing. I feel confident that I could repeat the process to build a database, with a search query function, and evaluate its effectiveness for my future profession.
INFO 202 - Beta Prototype Evaluation
My second piece of evidence is the evaluation of another group’s database that my group did for my Information Retrieval Systems Design course. We all had to exchange projects and judge how easy the database was to use, identify what worked well, and what could be improved upon. The group we evaluated created a database of kitchenware for cooking enthusiasts. It was interesting to see what other people did and having our work critiqued also allowed us to improve upon design flaws. Each group exchanged their evaluations with the group they measured and then we were allowed to edit our databases to make them more intuitive. This project gave me an insight into how user testing can go and the importance of evaluation.
INFO 202 —Project 2: Design Vocabulary for Target User Group
For this assignment my group designed vocabulary for a target user group for my Information Retrieval System Design course. Our target user group was San Jose State University students enrolled in the MLIS program following the public librarianship pathway. For ten academic journal articles relevant to the target group pertinent information was pulled from the article’s abstracts. We identified potential terms, grouped them by their likeness, and whittled the terms down to create a controlled vocabulary for each article. In the end, each article was only allowed to have five terms. This project taught me how the ins and outs of creating a controlled vocabulary for an information retrieval system. We had to evaluate the articles and design a controlled vocabulary for each.
Information Retrieval Systems are meant to be used and give the correct information to the user as soon as possible. A user should be able to navigate a system with ease and not have to ask questions about how to use it. Design is the first step in achieving this goal. As long as information retrieval systems are designed for users, then they will be more successful than those that do not. A query is an important function necessary for utilizing the system and getting information into the hands of the user. Evaluation is important for ensuring that users are getting a seamless experience, finding what they need, and making intuitive connections with the system.
Weedman, J. (2018). Lecture 3: Designing for search. In V.M. Tucker (Ed.), Information retrieval system design: Principles & practice (5.1 ed., pp. 119-139). AcademicPub/XanEdu.