Date
, 10am-11:30am
Attendees
Lisa Ngo, UC Berkeley
Jared Campbell, UC Davis
Ellen Augustiniak, UC Irvine
Sharon Shafer, UC Los Angeles
Elizabeth Salmon, UC Merced
Michael Yonezawa, UC Riverside [Today’s Notetaker]
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 | |
---|---|---|---|---|---|---|---|
1 | Updates from other SILS groups | Share relevant items | 15 min | Josephine Sarah | PPC: Suggests that Discovery FG reach out to consortia to inquire what they decided to do with their NZ. RMFG: appreciates our local 856 bibliographic data feedback that we’ve provided them to help consult on their decision page Special Meeting: PMs, Caitlin, Neil, co-chairs of Discovery, EUOS, and Fulfillment to discuss how the groups can align our work flow and decisions. EUOS: Josephine presented Discovery’s work timeline to EUOS on Monday (10/5). Discussion continued re: branding the SILS “ecosystem” and how that relates to Discovery’s determination of whether or not we will name Primo VE something other than “Library Search” after VG testing. How do you feel about having to name the “ecosystem”? If you are interested in a logo and name besides just e.g., UCLA Library Search, UCSD Library Search, etc. OR a unique name/brand which is still desirable by others as well. The recommendation of what to name the “ecosystem” and SLIS should be data-driven and research-informed. | Questions to ask other consortia:
| Who has contacts at other consortia to ask questions of at least four names for PPC. Email Josephine Tan (Unlicensed) with names of at least four contacts. For CARLI NZ https://www.carli.illinois.edu/products-services/i-share/alma/network-zone-guidelines As Ping for PASCAL contact information? DFG should consult for Fulfillment and RMFG as needed. EUOS, branding the entire project “ecosystem”. Based on the environmental scan, only one had an actual name for Primo VE. EUOS would like to message by January 2021 and was thinking of knowing what to message in November. Maybe in December but an actual name is not necessary to message something new is coming. |
2 | Vanguard Buddies Check-in | Offer feedback and suggestions | 15 min | All | Do all buddies have Discovery admin access now? Suggestion: the non-VG buddy shares screen and tests functionality & VG tester takes any necessary screenshots to capture and notates in the Google doc of their campuses Vanguard Discovery Testing Notes |
| If anyone would like more admin access to inquire with their VG buddy or local IC. |
3 | Discovery Work Flow Plan Roadmap | Evaluate timeline for more accurate dates | 15 min | All | Work Flow Plan link on our Discovery Confluence homepage. Jess walked through the deliverables. |
|
|
4 | Primo VE naming & logo | Discuss our status of whether or not we want to name Primo VE anything other than “Library Search” | 15 min | All | |||
5 | Consulting on RMFG’s next Decision Pages | Review and collect our feedback to help ERM with their next two Decision Pages | 15 min | All | Josephine Tan (Unlicensed) will share e-mail regarding what is being asked for 10/13 Vanguard action item. Detailed notes by Ellen in “feedback” for 856 field added as suggestions. | Questions to keep in mind:
|
|
6 | Homework | Prepares team for next meeting | All |
| |||
7 | Parking Lot/Q&A | Save these issues for future discussion & comments |
|
|
|
|
Our feedback needed to provide for the RMFG’s Decisions
Decision Page | Priority vote (1-3) | Consulting group feedback due |
1 | 10/7 | |
1 | 10/13 | |
1 | 10/13 | |
1 | 10/21 | |
1 | 10/21 |