Discovery UX Recommendation - Spring 2019
- Ian Chan (Unlicensed)
- Ryan Schwab (Unlicensed)
- Zacharry Williams (Unlicensed)
| Objective | Present a set of recommendations for improving the UX of CSU OneSearch |
| Due date | |
| Key outcomes |
|
| Status | IN-PROGRESS |
Problem Statement
Feedback from campus libraries and results of UX testing (as conducted by selected campuses) have revealed shortcomings in the user experience found within the OneSearch (Primo) interface.
Scope
Offer custom features to improve UX of OneSearch. Some features will be implemented as defaults while others would be optional.
Feature | Description | Implement as | Complexity | Implementation Timeline | Comments |
|---|---|---|---|---|---|
Add search links in left panel | Make it easier for libraries to insert links to other databases. | CENTRAL OPTION | LOW | August 2019 | This should be very easy to implement as a custom module -ZW |
| Display multiple locations within brief results | Much requested improvement that would highlight locations where an item is available. | NEEDS REVIEW | TBD | Documentation is very difficult to locate or non-existent. Not sure how its activated or configured. | |
| Pop-up 'tool tips' for facets | Provide helpful information for facet labels that are not readily understood by users. | LOCAL OPTION | HIGH | Implement locally | This is going to be very difficult, if not impossible. Their implementation is specifically hard coded for that item. This will probably need to have its own task force if we decide to implement it -ZW |
| Scopes dropdown on Primo home page | Highlights the availability of scopes. Many CSU do not offer the scopes on the Primo home page. Users typically don't land on the Primo home page unless they click the New Search menu option. | DEFAULT | LOW | August-September 2019 This change could be made during the semester | +1 to this. - Ryan |
| Scope dropdown on the left | Highlights the availability of scopes. CSU Chico CSUDH Impact on campuses with secondary scope dropdown? | CENTRAL OPTION | LOW | This will definitely cause issues for campuses with secondary scopes. It becomes very confusing, and it's probably best to keep them on the right. This could be implemented by default for all campuses except the ones with secondary dropdowns? -ZW Agree with Zach. This should be an option only, with a commented warning that its best used with single scopes only. - Ryan | |
| Secondary menu | Offer another horizontal menu in header region, in addition to built-in Primo header menu. This allows for displaying additional menu items if needed. Examples: | LOCAL OPTION | HIGH | Implement locally | This is going to be a huge headache, and will also probably need its own taskforce. Both of the example menus are very different, and there will be a lot of overhead in regards to maintenance and training for the campuses -ZW This is probably best implemented as documentation on this wiki, presenting some options, rather than a central package configuration. - Ryan |
| Relocate Send To menu | Moves the send to menu to the top of the full record display to improve visibility and reduce clutter in the availability and description sections. | OPTION | MEDIUM | August 2019 | If we implement this, it probably needs to just be an option for where it will be located so that campuses don't have to futz with javascript/css to reposition it. Another idea is to replace the side menu of the record display with the send to menu -ZW |
| Integrated chat pop-up | Make it easier for libraries to integrate chat widgets. | LOCAL OPTION | LOW | Implement locally | I am not sure how this will be integrated, to be honest. Most campuses have different chat vendors, with different methods of opening the chat. We'll need to have a meeting to discuss this one -ZW Yes, it's typically a drop-in bit of JS so we should leave it to individual campuses. Again, I think this is best completed as documentation rather than configuration. - Ryan |
| Display 'didn't find what you're looking for panel' at the bottom of search results | Offer options for users to obtain assistance or search offer databases if they are not finding what the sources that they need for their research. | OPTION | LOW | Implement locally | Looks like U Minn Libraries took it out. I like the idea of this, although maybe it would be hidden until the patron has gone through a certain number of pages? (Like 3-5 pages of results) -ZW I had the wrong link for UMinn. They still offer the panel. - IC |
| Activate autocomplete for search keywords | Make it easier for libraries to activate this feature. Ensure campuses are aware of this functionality. | OPTION | LOW | Activate locally | How does this get enabled? Is there a reason why it would not be wanted turned on? -ZW Campuses need to check their Primo Back Office settings. - IC |
| Lock filter icon always visible | Users are most likely not aware of this function. | DEFAULT | LOW | August 2019 | +1. I think this should be an option, but defaulted as on. - Ryan |
| Add automated Alma/PCI downtime notice | Would be based on https://github.com/LincolnUniLTL/warningnote | NEEDS REVIEW | LOW | Can be implemented in the Fall | Can be centrally hosted and managed |
Timeline
TBD
Milestones and deadlines
| Milestone | Owner | Deadline | Status |
|---|---|---|---|
| Draft recommendation | Ian Chan (Unlicensed) | IN-PROGRESS | |
| Request feedback | Ian Chan (Unlicensed) | IN-PROGRESS | |
| Finalize recommendation | Ian Chan (Unlicensed) | NOT STARTED | |
| Create implementation timeline | Ian Chan (Unlicensed) | NOT STARTED | |
| Hand-off to implementation team | Ian Chan (Unlicensed) | NOT STARTED |
Reference materials
Discovery UX Assessments to Review