⁠Karin Cheng

Improving the Library Search Experience for Students

Many AUAS (Amsterdam University of Applied Sciences) students stuggle to find relevant sources on the library website.

Role UX designer Time 3 months Prototype Figma prototype

Discover

1.1 Research methods

To gain a clear understanding of customer needs, bottlenecks, and business objectives, I combined multiple research methods. This allowed me to gather both qualitative and quantitative insights from different perspectives.

  • Survey (S): We distributed five questionnaires to graduating students to understand their pain points and motivations.
  • Interview (I): I interviewed a student to gain more in-depth insight.
  • Competitive Analysis (CA): Comparison with other libraries at other schools to gain inspiration and discover possible solutions.

Define

2.1 Design challenge

How could we help students find relevant sources for their research?

2.2 Persona

This persona represents a new student navigating the AUAS library website. He finds the interface cluttered and the search confusing, making it time-consuming to find and evaluate sources. As a result, he often avoids the library, relying on external platforms that handle these tasks more efficiently (see 3.4 Competitive Analysis).

Fig. 1 Persona Student

2.3 Customer Journey Map

The customer journey map shows a student’s experience using the AUAS library website during orientation week, highlighting key pain points in finding relevant sources.

Fig. 2 Customer Journey Map

I identified the main problems that hinder students from efficiently finding, evaluating, or using library resources. The most important issues are described below, along with their impact on the user experience.

2.3.1 Limited search information

Phase: Evaluate
Problem: Search result items only display titles and citation metadata, providing insufficient context (I). Without abstracts or keyword highlights, students must open each result and scan the item page to judge relevance.
Impact: Increases the number of steps and time required to find relevant sources; students may miss useful items or rely on platforms with richer previews.

Fig. 3 Result items

2.3.2 No contextual suggestions with search results

Phase: Evaluate
Problem: The website offers no recommendations or related sources in the results (O). Students must run multiple searches to find relevant information.

Impact: Most users only view the first three results, so missing contextual suggestions lowers efficiency. Research shows recommendations improve relevance ranking (from 4.5 to 3.0) and nearly double click-through rates (Carevic et al., 2018).

Fig. 4 Detail page without suggestions

2.3.3 Distracting layout and filters

Phase: All phases
Problem: Result items and filter panels include unnecessary metrics that distract from evaluating sources (O).

Impact: Students may feel overwhelmed or overlook relevant results, slowing down their search process.

Fig. 5 Filter

2.3.4 Ineffective exporting options

Phase: Save source
Problem: Sharing options are confusing and rarely used (I). Features like QR codes, Excel exports, and unfamiliar citation managers add clutter, while only citation support is consistently useful.

Impact: Students may ignore the options, waste time, or feel frustrated, leaving sharing needs unsupported.

Fig. 6 Exporting options

2.3.5 Poor mobile experience

Phase: All phases
Problem: The mobile layout is responsive, but it still feels cluttered. The navigation isn’t very clear, and using search results and filters on a small screen can be frustrating.
Impact: Students have a harder time finding and evaluating sources, which can make them less likely to use the library resources on their phones.

Fig. 7 Mobile screens without a strong hierarchy

2.4 Competitive Analysis

To compare how students find and use sources, I analyzed Google Scholar and PubMed. The focus was on three tasks: evaluating sources, discovering related content, and saving or sharing sources.

2.4.1 Evaluating sources

Google Scholar shows minimalistic citations in a single line with keyword-highlighted snippets, making relevance easy to judge. PubMed displays full citations with all authors and highlights keywords only in the abstract, taking up more space. The concise snippet approach of Google Scholar appears more effective for quick evaluation.

Fig. 8 Google Scholar Result item (left) PubMed Result item (right)

2.4.2 Discover related content

Google Scholar links to related articles on a separate page, but the connection isn’t always clear. PubMed lists similar articles at the end of the detail page with direct navigation, providing better context and a smoother exploration experience.

Fig. 12 Google Scholar Related articles page (left) PubMed Similar articles (right)

2.4.3 Save or share sources

Both websites allow users to save sources and generate citations. Google Scholar clearly lists multiple citation formats (Fig. 14), while PubMed shows only one style by default and hides other options, making it harder to use (Fig. 15). Providing clear and accessible citation options supports a more efficient research workflow.

Fig. 10 Google Scholar Cite (left) PubMed Cite (right)

2.5 MoSCoW

Below, I have listed requirements that give me direction and make it easier to make choices for my product.

 

Must

  • The user can find and evaluate relevant, useful sources efficiently.
  • The product complies with WCAG 2.1 accessibility standards.

 

Should

  • The user can provide feedback on the usability or relevance of a resource.

 

Could

  • The user receives personalized suggestions.

Develop

3.1 Morphological Chart

This method breaks down key user tasks and lists multiple solution ideas for each. It helped me explore design options in an organized way and find the most promising directions for the redesign.

Each solution in the chart is numbered, and the corresponding numbers are shown in the sketches below for clarity.

  • Fig. 12 Home page (left) Search (right)
  • Fig. 11 Result page (left) Detail page (right)
  • Fig. 13 Citation LoFi wireframe

3.2 Impact/ Effort Matrix

Together with Zoglo - Core Developer Contao CMS, we mapped out the ideas in an impact/ effort matrix to determine which ideas to implement. I decided to only design ideas that are high impact & low effort and low impact & low effort (left side).

Fig. 14 Impact/ Effort Matrix

3.3 Usability Testing

I conducted seven usability tests. Participants had varied backgrounds, including students, a recent graduate, and professionals.

Fig. 15 Usability testing

Deliver

4.1 Final Design

In this redesign, I improved the usability and key interactions while keeping the overall look consistent with the current library website. This way, the design still feels familiar to users, but the main issues found in testing are solved.

4.1.1 Limited source of information

Problem: Titles alone make it hard for students to judge relevance.

Initial design: Abstracts were initially truncated to two lines. Usability tests showed students still had to click into the detail page too often (Fig.23).

Refined design: Full abstracts are displayed inline with a ‘Show more’ link, allowing students to quickly evaluate relevance without navigating away from the results page (Fig. 24).

Fig. 16 Snippet description (left) Expandable description (right)

4.1.2 Contextual suggestions

Problem: The website provides no related sources, forcing students to perform multiple searches.

Initial design: ‘Cited by’ and ‘References’ were initially on the right side of the page. Tests revealed that they were distracted from the abstract, the most important element.

Final design: Contextual suggestions, including ‘Cited by,’ and ‘References,’ are displayed below the abstract, keeping focus on the source while offering easy access to related content.

Fig. 17 From suggestions on the right of the page (left) to suggestions at the bottom of the page (right)

4.1.3 Distracting layout and filters

Problem: Cluttered filters and unnecessary metrics distract users from evaluating sources. The original filters included hidden “exclude” options, which confused users.

Final design: Filters are simplified and organized, combining similar types and keeping only necessary categories. Unused metrics are removed, and only relevant sharing options remain. This creates a cleaner, more focused layout.

Fig. 18 Filters Final design

2.4 Streamlined citation export

Problem: Sharing options are confusing and unused, and citation options are buried.

Final design: Users can now choose their preferred citation manager or LaTeX editor, with file formats (RIS or BibTeX) clearly labeled. This streamlined approach reduces confusion and supports their workflow efficiently.

Fig. 19 Citation

4.1.5 Responsive design

Problem:On smaller screens, the layout is crowded, hierarchy is unclear, and navigation, results, and filters are hard to use.

Final design: The mobile layout now has clear spacing and hierarchy. Titles, results, and filters are readable, usable, and visually consistent across devices.

Fig. 20 Responsive mobile wireframes

4.2 Reflection

Usability testing showed that the redesigned library search allowed students to complete 6/7 tasks successfully. Inline abstracts and contextual suggestions helped users evaluate sources faster, while simplified filters and sharing options reduced confusion and improved workflow efficiency. Overall, small, user-centered changes made the library search experience significantly more usable and intuitive.

4.3 Reference List

Carevic, Z., Schüller, S., Mayr, P., & Fuhr, N. (2018). Contextualised browsing in a digital library’s living lab. The ACM Digital Library.
https://doi.org/10.1145/3197026.3197054
Optimizing my online stationery shop
karin-cheng@hotmail.com
LinkedIn

Amsterdam, The Netherlands

Privacy Policy
Privacy Settings

Privacy policy

This website uses cookies to enable certain functions and enhance the experience.

Protects against cross-site request forgery attacks.

Retention period: This cookie will only remain for the current browser session.

Saves the current PHP session.

Retention period: This cookie will only remain for the current browser session.

Collection of statistics on website usage

Provider: Google Ireland Limited, Google Building Gordon House, 4 Barrow St, Dublin, D04 E5W5, Irland
Retention period: You can find out more about the storage period of the cookie here https://policies.google.com/privacy.