2023-08-25 Meeting notes

Sharing and Updates

5

Share any Discovery related information from other SILS groups

All Chairs: Briefly discussed priority of duplicate ebooks. RM is also working on ETDs which have duplicates. Should we first spearhead figuring out what the impact of duplicates are on users?

• UCSC did a usability study back in 2018 and found it a big problem with faculty due to trust in the system

• UCR also is hearing frustration about this, specifically with CDI records. They are getting fewer reports but it might just be because people are giving up, not because they like how it’s working.

OT did not get a chance to look at the user dashboard proposal at their most recent meeting.

Slack Questions

5

FYI from UCSC: Hi all, wanted to share a small UI change we’re making. We have had reports of a “REGISTER” button appearing sometimes when folks are looking at the holdings of other UC campuses listed in a record. We have decided to use CSS to hide this button.

Follow-up to Jackie’s post about screen reader issues/interpreting the VPAT results: Our contract says that Ex Libris will meet Level AA of WCAP 2.0 . We’re waiting on a response from Ex Libris to see how they want to discuss our concerns.

FYI: early strategizing of Primo VE enhancement requests

5

Once we have a plan for handling Primo VE releases, would it make sense to talk about strategizing Primo VE enhancement requests?

• Are there enhancements already at the campus level we should support?

• Do we want to create any consortium enhancement requests? If so, we should schedule time to work on this.

• Other issues around enhancements?

Interested in the general idea but not limiting to just the official enhancement requests.

Gem will put on work plan so we can evaluate when ready.

Primo VE release schedule next steps

30

Draft a decision page

Based on the text in the work plan, it seems this falls into three categories:

• Scheduling time quarterly to meet and discuss upcoming enhancements

• Best practices for updating Primo VE configuration to be resilient to core updates

• Regression testing which could include

  • Custom code (though right now this varies a lot by campus) - Custom code in particular is a concern

  • Testing past Ex Libris fixes to make sure they still work

Does this feel like the right scope?

Verify that at this point we’re focusing on the quarterly feature releases?

We’ll focus on the quarterly updates and reconsider if the monthly becomes a problem.

Scheduling time quarterly, during existing Discovery meeting time.

We get the release notes really late for testing. Definitely not before it’s already released in the sandbox. Some things needs to be indexed before testing which could make testing hard.

Ex Libris is being better at keeping new features off by default. But because of the timing it is hard to be proactive.

We’ll plan to work on testing the meeting after the production release. Note: we can still have earlier meetings if we’re aware of a huge change happening.

The regression testing would need to be campus by campus. However, we can write up some suggestions about how campuses can approach this.

Next meeting we’ll get more into the details of how we want to approach this (for example, read release notes ahead of time and come ready to flag concerns or read release notes in the meeting, or other approaches)

Gem will map out which of discovery’s meetings correspond with the quarterly releases and figure out somewhere to post that.

Next Steps

5

September 8 Meeting:

• Planning to talk about the User dashboard project.

  • Are your campuses preliminarily interested in this?

  • Gem will report back about what she learned at CDL.

• Prime VE release schedule discussion

  • Flesh out our general approach with more specifics

• Are we ready to discuss how we want to incorporate UX into general discovery meetings?

Parking Lot

Next Primo VE release meeting: November 17

Discuss how we want the UX subgroup to function

Worldcat Links (may be related to UX subgroup)