2020-09-01 Meeting notes

Date

Sep 1, 2020, 10am-11:30am

Attendees

Lisa Ngo, UC Berkeley [Today’s Notetaker]
Jared Campbell, UC Davis
Ellen Augustiniak, UC Irvine
Sharon Shafer, UC Los Angeles
Elizabeth Salmon, UC Merced
Michael Yonezawa, UC Riverside
Heather Smedberg, UC San Diego
Josephine Tan, UC San Francisco (co-chair) [Today’s Timekeeper]
Jess Waggoner, UC Santa Cruz (co-chair)
Sarah Houghton, California Digital Library
Chizu Morihara, UC Santa Barbara

Not attending

Discussion items

DISCOVERY VISION: We strive to design and implement the best possible discovery and delivery experience for our end users using data-driven decision making. We envision a network zone experience that will allow users to discover library materials across UC collections without sacrificing relevant results. As such, the default search and results interface should prioritize the success of typical users while providing additional functionality for more advanced users.

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions
1	Updates from other SILS groups	Share relevant items	10 min	Josephine Sarah	The SILS Working Group created a privacy agreement and is ready for Vanguard testers to sign PPC provided guidance in filling out the Testing Worksheet for PPC suggests that Discovery FG will be making decision in Vanguard testing to see how NZ for Primo VE will display	Testing the NZ for Primo VE user interface (Discovery NZ of PrimoVE testing tab) will be dependent upon working with groups such as Resource Management.	All: Fill out the Data Security Acknowledgement form
2	Primo VE User Interface for Vanguard Decision Page	Review edits made in last meeting & further flush out Recommendations and Reasoning section & Dependencies section	40 min	All	See Primo VE User Interface Decision Page for Vanguard Draft notes Facets: recommendations need to be discussed regarding facets, default facets shown, facet labels, etc. Suggestion to survey UC campuses on Alma/Primo to see what is default (out of the box) and what changes campuses have made, or survey CSU campuses to see how they display; may inform configuration recommendations Campuses with Alma/Primo can look at their analytics and share facet usage information	Look over decision page and send approval or comments to Josephine
3	Functionality Testing Checklists	Determine which functional group within each VG campus' implementation team should test which functionalities Test cases?	40 min	All	Refer to existing checklists: ExL Go Live Readiness Checklist Jess’s Functionality Checklist CDI testing: CDI implementation and configuration will be handled locally, but it’s unclear whether it’s discovery or another group who should be testing. We need to reach out and make sure each local Vanguard has a group tasked with working with the CDI. Sharon has shared UCLA’s functionality testing scripts for Voyager on Confluence.	Homework: Each Vanguard campus should discuss with their local implementation groups who should be responsible for CDI configuration, implementation and testing for their campus (yellow CDI tasks on Testing Worksheet). Homework: Vanguard campuses look at Testing Worksheet for PPC and assign responsible party for completing the testing (can all be local discovery team or different team(s)).
4	Homework	Prepares team for next meeting		All			All: Look at ExL’s Primo VE Customization Best Practices All: Continue with self-paced Primo VE training All: Continue with self-paced Alma Essentials
5	Parking Lot/Q&A	Save these issues for future discussion & comments			Configuration Determine plan for MELVYL and Related SILS Services ExL Go Live Ready Checklist Ebook ILL lending as it relates to discovery and limiting to availability.