2023-09-13 RS OST meeting notes

Attendees

@Kristen Van Vliet , UC Berkeley
@Jason Newborn , UC Davis (chair)
@Linda Michelle Weinberger , UC Irvine
@Demitra Borrero , UC Merced
[] , UC Santa Barbara
@Dawson Kelly (UCSC) , UC Santa Cruz
@Judea D'Arnaud , UC San Diego
@Ryan White , UC San Francisco
@Alison Ray (CDL) , California Digital Library (past chair)
@Amador, Alicia , UC Los Angeles
regrets: @Sabrina Simmons , UC Riverside; ;
guests: Helena Gagnon, UC Santa Barbara ; Ralph Horton, OCLC

Zoom URL: https://ucdavis.zoom.us/j/97976196284?pwd=K3MrREN2NUlGZmhEaGpBMzRRWFJmQT09

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions

	Item	Desired Outcome	Time	Who	Notes	Decisions	Actions
1	record meeting	make sure Jason records meeting	1	Jason
2	Vice Chair Volunteer	Ratify, and Thank Vice chair volunteer. Kristen Van Vliet from UCB has volunteered	5	Jason			JN: intro KVV on allchairs slack channel JN: send note about KVV VC to asksils-l
3	VDX / WSILL ISO desyncing (Aug 25 2023 incident)	Current status and update from Ralph	20	Ralph	Official OCLC statement coming this afternoon All ISO ILL users were affected (not just VDX - includes Alma, Relais, autografix etc). Table associated with ISOILL messages was altered & caused errors in all messages to all software using ISOILL. VDX specific effects: process handling ISO messages removed all requests, effectively un-ISOing all exisiting requests in VDX. Some sets of requests were ‘re-ISOed’ (checkins & requests). Other requests were unrecoverable and will have to be actively de-ISO and handled manually by UC ILL staff New requests after Aug 25 (~7am Pacific) should not be affected by disconnection on affected requests: VDX will still send NCIP to Alma, but WSILL will generate “unable to connect to database” error ILLReports should show status of request as represented in VDX regardless of ISO success/failure.		Ralph: add in VDX reports to identify sets of affected open requests UC ILLers: send in “VDX Problem Report”s for further questions and (especially) examples not included in pattern described followups: Alison: will request further followup with OCLC about problem Alison/Tipasa team: ask OCLC about how ISO issue impacts (would impact) Alma/Tipasa ISO integration
4	Consortial Block query emailed to Steven Burke (action step #1)	Described Service Case and asked for appropriate channel	5	Jason
5	Wrap up	Review actions and decisions	5		9/27/23: strategery meeting (work plan, priorities, etc.)
6	Bike Rack	Capture important topics for future discussion			items being kicked out to WorldshareILL at end of ROTA even though we have those items in our catalog (Demitra) [RS OST SC notes 5/1/23: hold for consideration post Tipasa implementation]: ‘pick up anywhere exceptions’: review shared messages, what would be next steps metrics on how often ‘pick up anywhere’ requests have to be changed to home campus (Jason) → may lead to: editing pu loc for this requests → may lead to: harmonizing bookbands
7		Total	x/x