2022-11-09 RS OST meeting notes

Attendees

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

	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	Review/Discuss OCLC’s Extending Tipasa Alma integration document	Identify any clarifying questions needed from document Identify any choice points to make from document Consider any next steps	?	all		“API contacts” will meet again with OCLC for more clarity about “APIs”
3	Tipasa timeline: adding in go/nogo points	Add in 1-2 (or more??) go/nogo decision points (eg. after pilot ends)	7ish	all		slotted in go/nogo dates in timeline	@Alison Ray (CDL) 1st tipasa rs ost go/nogo decision on jan 25 agenda Jan 19, 2023
4	Tipasa Pilot temperature check	Understand how people are feeling about Tipasa so far… testing, integration, confidence Overall temperature is cold		Tipasa Piloters	ILL Request transfer has been tested in R & B sbs, varying level of success some testing between sandboxes what comes through via ill request transfer?? → please send any summary of deficiencies to rs-ost-l * patrons don’t link (OCLC says this is expected behavior) → nogo for this integration * Patron email not coming through general disappointment in ability to test (limitations in environment: supposed patron interactions, other integrations not available to test possible test (for Tipasa to Alma): complete patron account in tipasa, then Need two “ncip” profiles in Alma, one for Alma-> Tipasa, and another for the Tipasa → Alma (NCIP info & Tipasa configuration)
5
6
7	Wrap up	Review actions and decisions	5				@Alison Ray (CDL) ask on rs-ost-l about meeting nov 23 Nov 9, 2022
8	Bike Rack	Capture important topics for future discussion			‘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 is the “randomized” part of the rota building actually randomizing things? Jason has a hunch that within the geographical groups it’s creating them alphabetically. (discovered in reviewing schedule c report) NRLF/SRLF rejected stuck at B/LA follow up: SH’s ‘guide’; test with what B/LA see; more escalation with ExL (scott, Mallory, Jason, patrick) ExL’s solicitation to “contribute to the Resource Sharing Directory”. Kind of a huge thing that we should think about? (Mallory) → maybe after P2P investigation…
9		Total	x/x