2022-05-11 meeting notes

Attendees

@Patrick SHANNON (Unlicensed) , UC Berkeley
@Jason Newborn , UC Davis (vice chair)
@Linda Michelle Weinberger , UC Irvine
@Sandra Farfan-Gracia , UC Los Angeles
@Demitra Borrero (Demitra Borrero), UC Merced
@Sabrina Simmons , UC Riverside
@Mallory DeBartolo (Unlicensed) , UC Santa Cruz (note taker)
@Peter Devine , UC San Diego
@Scott Hathaway , UC Santa Barbara
@Ryan White , UC San Francisco
@Alison Ray (CDL) , California Digital Library (chair)

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions
1	record meeting	make sure Alison records meeting	1	Alison
2	upcoming meetings: 5/18: ILL CKG (no RS OST) 5/25: RS Analytics subgroup	FYI on schedule	2
3	Preferred Pickup Location error issue	Case 05312761 “Preferred Pickup Location Error When Patron Chooses Owning Campus as Pickup”	5	Alison	ExL aiming to fix in December. This is a long way off for something labeled as “critical” in phase 4. AFN won’t let you select a book owned by a library to pick up at that same library. For example: if you are a Davis patron and there is a book you want from LA and you want to pick it up at LA you will not be able to make that request. May not be as critical because the pick up anywhere is so wonky and confusing that it’s not as apparent of a problem. We aren’t hearing mass outrage about this. Still needs to get fixed though.
4	think about what a meeting with OCLC might look like. What would be included in that meeting agenda?	Tipasa requirements oclc meeting agenda	40	all	idea: prioritize requirements that need discussion with OCLC	more resources: ?ExL people with Tipasa integration knowledge (in particular ‘last resort’ config) ?other Alma library using tipasa as ‘last resort’. Can be any library using Alma Resource Sharing (ask on Alma-L list or consortia list?)	@Alison Ray (CDL)find ExL docs that Alma can send requests to Tipasa as 'last resort'May 20, 2022 @Alison Ray (CDL) make draft email other Alma library using tipasa as ‘last resort’. Can be any library using Alma Resource Sharing May 27, 2022 @Alison Ray (CDL) email Eric F about meeting agenda & vague timeline for meeting late June or early July May 13, 2022
5	Page entries on the Resource Sharing form are only sent when enumeration fields are populated with information.				This is the one where “volume” is required to put the request into the workflow that allows a request to go into the Deliver Digital Documents queue (rather than wither and die in the Digitization Department for Institution). Looks to be fixed (according to case 05323953). Needs testing!		@Jason Newborn (not tipasa) try out testing primo resource sharing form in Primo/Alma sb; then coord testing meeting with select testers; follow-up on listserv
6	Wrap up	Review actions and decisions	5
7	Parking Lot	Capture important topics for future discussion			RS Retrospective: Fulfillment Network discussion (Joe Ferrie guest) Jun 1, 2022 ‘pu anywhere exceptions’: review shared messages, what would be next steps metrics on how often ‘pu anywhere’ requests have to be changed to home campus (Jason) → may lead to: editing pu loc for this requests → may lead to: harmonizing bookbands Why do some digitization requests go to the “Digitization Dept for Institution” queue? It means they can’t get filled in Alma and then get kicked out to VDX - see 4/6/22 meeting notes for more info. (Scott)
8		Total	x/x