2023-09-08 Meeting notes

Attendees

Gem Stone-Logan, California Digital Library;
Sean Claudio, UC Irvine
Jackie Gosselar, UC Berkeley
Joshua Gomez, UCLA, UX Subgroup
Douglas Worsham, UC San Diego
Jessica Kruppa, UC Riverside, Chair
Jess Waggoner, UC Santa Cruz
Zach Silveira, UC San Francisco
Zoe Tucker, UC Los Angeles
Jared Campbell, UC Davis
Joe Ameen, UC Merced
Michael Craig, UC Santa Barbara

Not Present

Meeting Recording: https://drive.google.com/drive/u/0/folders/1HHdEBRm0_L3LJICWgH_X-nSIG-jReKkR

	Item	Est Time	Desired Outcome	Notes	Decisions / Discussion	Actions

	Item	Est Time	Desired Outcome	Notes	Decisions / Discussion	Actions
1	Sharing and Updates	5	Share any Discovery related information from other SILS groups	All-Chairs: Would like a list of biggest issues with Primo VE. OT: Discussed Patron dashboard (see agenda item below) Negotiation committee: Joshua is on the committee so likely will be coming back with questions for our group.
2	Slack Questions	5		From Sean: Hi all, does anyone understand what the "Allow Authentication for Customized List of Institutions - Consortia Only" feature from the August release does? Sean reached out to Ex Libris and they didn’t really have much more information than what the release notes said.		Done: Gem will ask on consortial alma listserv
3	UX plan going forward	5	Confirm group feels this is the correct approach.	Current status: While it would be interesting, we don’t have the resources right now to do a comprehensive UX review. In addition, several of the UX problems UCSC identified are things we can’t customize on our own (would need to involve Ex Libris) UCLA is also finding it very difficult to implement desired changes. UCSC also have a local Primo VE/UX group and will keep surfacing issues as they find them. CDL: Peripherally related, we’re working with Ex Libris on discussing the WCAG Level A/AA issues UCB just started working on inclusive UX research also. Hoping to begin focus groups next year and have findings next spring/summer.	Handle UX requests individually as they came up. If necessary, create small teams to do initial research.
4	Strategizing of Primo VE enhancement requests	5	What priority should this have?	Added to the work plan (row 13)	Expanded initial scope to include reviewing other ways to advocate for UC needs. Set priority as high.
5	User Dashboard	10	Initial campus feedback. Determine next steps, if any.	OT feedback: Interest but also concerns. Questions are in the notes and includes things like ongoing maintenance. General oversight governance. Some campuses feeling burned by past integrations. Also accessibility questions. UCB developed the RLF tool which they’re still maintaining but are stuck with the maintenance for 10 years. Discovery discussion: No campuses or CDL are able to commit developers for the user dashboard project at this time. However, everyone is interested in the concept.	UCLA should do what makes the most sense for them, without additional development support from other campuses, but the Discovery group is interested in occasional updates.
6	Primo VE release schedule next steps	25	Review what has currently be added to decision page (will be drafted before meeting).	Draft “Practice and Documentation”	Use the rest of the meeting time to review the draft, jot notes, and come back to discuss at the next Discovery meeting.
7	Next Steps	5	Review Primo VE release practice and documentation draft and discuss in our 9/22 meeting.
8	Parking Lot			Next Primo VE release meeting: November 17 Worldcat Links (tentatively talk about this September 22)