DISC (Go Live) Rename UC-eLinks

Legend: not started IN PROGRESS STALLED decided

Recommendation

We recommend renaming UC-eLinks to “Get it at UC” and restyling the button to depict the new name and incorporate branding aspects of UC Library Search.

Open

Open

Reasoning

• We will no longer be using the SFX link resolver, thus the user flow for accessing full text or request options from the link resolver will change. A new name will help set expectations for a new experience.

• Highly transparent and meaningful link resolver names are more usable, particularly to novice users (such as new undergraduate students)

• It is preferable to use a button rather than a plain link when possible because initiating the link resolver is performing an action, and UX design best practices suggest buttons should be used in such cases

Background

We will no longer be using the SFX link resolver in favor of the built-in Alma link resolver. This will change the user experience for accessing full text or request options.

Users generally encounter the UC-eLinks button in Abstracting & Indexing databases such as PubMed and Web of Science or research tools such as Google Scholar. (See “Where will you see the UC-eLinks button?” for a more comprehensive list.)

As the new Alma link resolver will also be used for submitting interlibrary loan requests from Worldcat, users will also encounter the new button in that interface.

UC-eLinks (SFX) vs Alma Link Resolver User Flow

When users click the current UC-eLinks button, the SFX link resolver will either connect them directly to the full text of an item or to a menu where from they can get it online (if available), check local availability for the item, request it, or Ask a Librarian.

When users click the new Get it at UC button, the Alma link resolver will use an OpenURL to connect them to a Primo record for the item. From this Primo record, the user will either be able to click a View Online link to access the full text of the item or use the “Request through Interlibrary Loan” link in How to Get It to request the item.

Since the user flow will change with our implementation of Alma/Primo, we can help set user expectations for this new flow by renaming the button.

Environmental Scan Results

We consulted “SFX Label & Options Menu -Comparative Analysis” by Kat Hagedorn (2006). Hagedorn scanned SFX labels across 9 institutions and found that most labels included the term “find it.”

We completed a new scan of these 9 institutions and found that very little had changed since the 2006 study. Only the University of Michigan had made a substantial change, relabeling from “SFX @ M” (indexes) and “Find It!” (SearchTools) in 2006 to “MGet It.” We also found that Indiana, which was recorded as “[not available]” in 2006 is now “IU-Link.” The majority of labels continued to include the term “find it.”

Literature Review Summary

We reviewed 4 articles or white papers on the topic of link resolver usability. In our review of these sources, we found that:

• Meaningful and recognizable labeling for link resolver links/buttons is essential for usability

• Labels relying on recall may have poor usability even among advanced (ie. Faculty) users

• “Get It” and “Find It” are both viable and usable options with “Get It” being slightly preferred by users (in the reviewed literature)

• Including the institution name in the link label is a common practice

We also reviewed Nielsen’s 10 Usability Heuristics and some relevant portions of recent LibKey usability testing at UC Santa Cruz (in connection with the Nomad browser extension) and found that:

• “The design should speak the users' language. Use words, phrases, and concepts familiar to the user, rather than internal jargon.”

• Users are concerned about site security/trustworthiness and having the term “UC” in the link label might help alleviate these concerns

Working assumptions:

• We will be using the Alma link resolver rather than SFX after Go-Live

• CDL has the resources available to change the UC-eLinks name and button

Dependencies

• Need to give local stakeholders adequate time to update existing instruction and outreach materials that refer to UC-eLinks

• Need to give local staff adequate time to coordinate with local/Tier 3 database providers

• Need to give local staff adequate time for testing

• Need to give CDL staff adequate time to coordinate with database providers.

• Need to give CDL staff adequate time for testing

Questions to consider

Should we rename UC-eLinks as part of our implementation to Alma/Primo?

If we do rename, should we restyle the button as well?

What link resolver names are used at peer institutions?

How does the link resolver name impact usability?

Options considered

Action Log