In today’s digital world most research is done with information retrieval systems, most notably: databases. Libraries buy subscriptions to databases that store journal articles and content on specific topics or specialities. There are also full text databases, online public access catalogs (OPACs) and web search engines; but databases do the heavy lifting when it comes to research. Each database organizes their collections based on their own set of user design and end user purposes (UX). Finding the content the user wants, and only the content the user wants and how well and easily this is accomplished is a matter of how well it was designed, and how users must query the database to locate the content. This means that the ability to evaluate a database and to understand the database, is essential to working with one of the most highly used tools in our day and age.
The world of information is vast and ever changing, with many barriers to information such as pay walls, poor UX design, or inconsistently controlled vocabularies. Access to information and specifically detailed research, is no longer about searching through physical books, but searching through endless databases, thus understanding how these online collections work can help librarians navigate and utilize these databases to be the best information professional possible. While I have used databases for my research in every course at SJSU, there are five pieces of evidence that I feel demonstrate my understanding of how databases are designed, and the principles behind querying and evaluation of databases. In INFO 202 we created a database prototype, we chose a subject, defined target users, and created an alpha and beta prototype using controlled vocabulary and an attributes list. We also had four assignments on controlled vocabulary for a target user group, and how to set up a database using card sorting and data structures. Finally in 202 we evaluated and re-designed a website around the principles of UX, design and searching. In INFO 210 I approached this same topic from a searching perspective of principles of querying by evaluating a database with RUSA guidelines. And finally in INFO 240 I designed a website using HTML5 and CSS, evaluating and designing it with a target user in mind. I am also currently working as an intern at the CSUF reference desk answering reference questions using the CSUF databases. These pieces of evidence demonstrate my proficiency in understanding the specific principles of design, querying and evaluation of databases and their importance in the field of information science. Going forward I believe I will utilize these skills to design, evaluate and use databases for future queries.
Design is about creatively approaching an information retrieval system from an end user perspective, weeding out potential problems and creating solutions in order to design a system interface that the user can -without struggle or confusion- seamlessly interact with (Tucker, 2021). As Clark mentions, “If library and information services are indeed design artifacts, then information professionals need to explicitly harness principles, techniques, and methods of design to create more robust and successful tools and services” (2018, p. 281). These principles have to be harnessed for effective use. Creating and designing information retrieval systems means having a deep understanding of how to search, how to use the information, and how the information will be stored and retrieved, while also keeping in mind a user-friendly interface that requires no formal or at least limited knowledge of these principles. When something is well designed it will aggregate all the content desired and disseminate anything irrelevant, with precision and accuracy. Precise recall means the database aggregates all content the user wants, while disseminating anything that is irrelevant and this is the ultimate goal of a well thought out design often utilizing controlled vocabulary to standardize terms, and attaching attributes to records with defining characteristics to improve this process (Weedman, 2018).
Learning principles of querying techniques made me a better researcher and better at creating my initial research questions. One of the most useful and universally employed sophisticated searching techniques is that of Boolean phrases with the three operators: AND, OR and NOT. It is important to know how to phrase a question as it will influence what is and is not recalled. It is also important to “fit my search to the system” by recognizing that different information systems are set up with different users and purposes in mind, so I must have a search strategy that fits the database (Weedman, 2018). Understanding “threshold concept theory” with four concepts: information environments, information structures, information vocabularies and concept fusion along with properties of visioning and profound ontological shifts, show how diverse and complex querying is within our technology savvy world (Tucker, 2015). There are four strategies for search expertise I learned in INFO 202: operators and limiters, pearl growing, controlled vocabulary and citation tracing; which taught me how a simple single google search is rarely proficient. Understanding how language and data affect the precision of what is retrieved has given me a greater understanding of the importance of controlled vocabulary to eliminate ambiguous language and improve consistency and accuracy. Understanding these innerworkings has broadened my understanding of the complex relationship between information and retrieval and the strategies to conquer it. The ultimate result of my understanding these principles of querying is that I get what I want from my search with efficiency and precision!
When looking at, and evaluating databases I must take into consideration the principles of design and querying along with those of user design/user engineering (UX). Much of this evaluation process requires a series of questions: Does the information retrieval system function and fulfill its purpose as an information retrieval tool? Is the controlled vocabulary creating usable accuracy and precision in what it recalls? Is the format of the database set up for a user experience that is self explanatory? Are there visual aids to show hierarchies, indexes, glossaries and how to cross reference data? Is the information self-evident? There is a natural human assumption that we all approach a problem the same way, and that our way is the sensible way. In actuality we all approach things differently so we must design databases with this understanding of human behavior and evaluate them on how we actually use them (Krug, 2014). To create search engine optimization we have to evaluate our databases for relevancy, recall, precision, discrimination and usability with an understanding of the short life cycle of the technology we utilize (Weedman, 2018).
Description: 202 Database Prototype was a project with WebDataPro where we chose a subject to create a database prototype around, defined our target users, in this case, new wine drinkers who were curious but on a budget, and then created a database designed to simplify this information and guide the user toward a new wine for them to try that they would like. We created general rules for our fields: name, type, required (for the search), definition and rule associated. We also created an infographic with instructions on how to read a wine label. I co-wrote and edited the statement of purpose, multiple individual rules, and was the team leader for this project.
Justification: This is an example of how I assessed and created a database, the thought process that goes into the design of the user group and their needs, their behavior, as well as the specific controlled vocabularies used for the different fields and attributes. We used evaluation methods in our design period by asking for feedback from team members who were similar to our target user group, bringing in elements of user design. This taught me how to design, and evaluate a database, and to think of principles of how the user will search for items in the process.
(Scroll through the document below to see screenshots of the database.)
Description: For INFO 202 We had three assignments associated with controlled vocabulary, card sorting, and designing a data structure and attribute list. These assignments helped us understand how the information was perceived and how it could be organized so it could be retrieved for future use.
Justification: These three assignments show clearly my understanding of how to identify attributes, and build a data structure, in my example using socks. In the controlled vocab design basics I took a group of concepts, and distilled it down to the best term for each group, and then created a final controlled vocabulary list. We took records of articles, assigned descriptors, and using this same processes drafted terms that would become a vocabulary list based on concepts in the academic articles. This is the same process many databases go through, and I now have an understanding of how to create user friendly controlled vocabulary and the basics for designing a database.
Description: For INFO 202 we were asked to pick a library website and evaluate and possibly redesign it. We chose: Auckland Library website, I wrote the executive summary, edited the other sections, and was team lead and facilitator. We did many evaluations and redesign suggestions as a group, having long zoom discussions on usability, end-user demographics and doing many of the content decisions and restructuring on the zoom together. We evaluated the advantages and disadvantages to the current website, prepared a redesign based on our evaluation and user experience focusing on creating more descriptive main category labels to make navigation easier and avoid user fatigue.
Justification: In this assignment we explored principles of design, user design and evaluated the usability of the entire website. We then took our knowledge of how databases work, how users query, and redesigned the website based on these principles. Evaluating and redesign is something that I may be asked to do in my future career as a librarian. Websites are often being re-evaluated and redesigned and having this skill and understanding of how to design, query and evaluate information retrieval systems to best serve my community is now part of my skill set.
Description: For INFO 210 I evaluated and analyzed an information transaction using RUSA guidelines of general visibility/approachability, interest, listening, inquiring, searching and follow-up. I also looked at the direction of scholarly and library reference content in the 21st century with the influence of technology, AI/bots, and databases. I also shadowed the CSUF Reference Desk and observed and analyzed their reference services using RUSA guidelines and how they utilized their databases.
Justification: The RUSA guidelines are an excellent place to start when understanding user design for the reference interview. I saw how users approached a query, how the librarian evaluated their information needs, and chose the best database and search terms to fulfill the user’s needs.
Description: I designed a website from scratch, evaluated its effectiveness based on how well it communicated the information presented.
Justification: Sometimes I will need to create or present information without having any scaffolding. This was a great project to encourage me to learn how to create an information system from nothing using the theories of user design.
INFO 240: Information Technology Tools & Applictions Demo of Website I built using HTML5, CSS, and a little JavaScript.
As we continue to traverse the never ending deluge of new technology, we must keep in mind the principles of design, querying, and evaluating databases and other information retrieval systems. Information is power, but it must be findable, retrievable and usable or it is lost forever. If it takes ages to find a single record because the system was poorly designed, or the user does not know how to best ask for the record then the design and system has failed. Everything relates back to the end user and their ability to actually satisfy their needs with the system created.
Krug, S. (2014). Don’t make me think, revisited. 3rd edition. New Riders.
Tucker, V.M. (2021) Information retrieval system design: Principles & practice (6.1 Ed.). AcademicPub.
Tucker, V.M. (2015). Sharpening the search saw: Lessons from expert searchers. School of Information Student Research Journal, 5(1). https://doi.org/10.31979/2575-2499.050102 retrieved from https://scholarworks.sjsu.edu/ischoolsrj/vol5/iss1/2
Weedman, J. (2018). Information retrieval: Designing, querying, and evaluating information systems. In Information Retrieval System Design: Principles & Practice (6.1 ed.). Ed. Virginia M. Tucker. AcademicPub.