2022-07-06 RS OST meeting notes

Attendees

@Patrick SHANNON (Unlicensed) , UC Berkeley
@Linda Michelle Weinberger , UC Irvine
@Scott Hathaway , UC Santa Barbara
@Mallory DeBartolo (Unlicensed) , UC Santa Cruz, note taker
@Peter Devine , UC San Diego
@Sabrina Simmons , UC Riverside
@Ryan White , UC San Francisco
@Alison Ray (CDL) , California Digital Library (chair)
regrets: @Sandra Farfan-Gracia , UC Los Angeles, @Demitra Borrero (Demitra Borrero), UC Merced, @Jason Newborn , UC Davis (vice 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	reminder: next week Tipasa Two-Wednesday with OCLC		30 seconds	Alison
3	discussion of next steps from work plan item “which hybrid model should RS OST investigate - direct FN and/or P2P”		40		(from RS retro discussion 2022-06-01 meeting notes ) assumption: testable in sandbox (both direct fn & p2p) assumption: test independent of external broker (VDX vs Tipasa) next step: make a test plan How to configure either or both of these? Do we test separately or together? Communication with Fulfillment Group: Alison and Jason meet regularly with FG chairs and can communicate with them about this project. Good to involve FG as a courtesy and also they are front line folks so it’s good for them to know what’s happening. Direct FN might impact discovery so they might need to be pulled in. Does a project subgroup make sense for this project? → yes who could be on this group? maybe 1/2-2 hours/wk; first: define/untangle config & stub test plan. Mallory; Alison; Sabrina ask again after config/test plan stub for more testing action. Useful note on timing: consider config after the sandbox refresh so we don’t do a bunch of work on it and then it disappears.
4	Thunder trio for hybrid model	concrete next steps & where to document where: GDrive folder what: user documentation (how it would work, maybe exl videos - end to end workflow stuff) → ask alma community? write up qs for ExL (Steve B.) relevant config pages → first step of ‘stub test plan’ → which model to test first? df or p2p?? → → further down the line, how to test, test cases, etc etc drop what might be useful into notes doc			useful for trio: read only permissions (gen sys admin)		@Alison Ray (CDL) make sf case of qs about direct fulfillment networkJul 13, 2022
5	Wrap up	Review actions and decisions	5
6	Parking Lot	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 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) (item 5 of 2022-05-11 meeting notes )Page entries on the Resource Sharing form are only sent when enumeration fields are populated with information (Jason) special collections ‘special case’ uses falling into VDX: unclear how to fill this need within SILS architecture (should this use case get added to work plan?) (Alison/Jason)
7		Total	x/x