2022-04-06 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	kick off Resource Sharing Alma Analytics	decide ‘all of rs ost’ or ‘subteam’ - pick members if subteam pick leader/driver of project what is most immediate next step?	20	steering committee	Basically make a copy of ILL Reports in Alma. Schedule C may be a good place to start. Role needed: Designs Analytics Interest expressed by: Linda Michelle Sabrina Patrick Sandra - project lead! Scott Alison Peter/Debbie Cox Timeline for project - not sure. Maybe a good topic for first meeting. Dependency: UCOP stats deadline - how firm is that? (SSM investigating with UCOP contact) Identify priority of specific reports identify needed documentation (eg. how to see reports from the nz)		@Sandra Farfan-Gracia set the first meeting & agenda for ‘resource sharing alma anayltics’ project team.
3	kick off Replace VDX with Tipasa	decide ‘all of rs ost’ or ‘subteam’ - pick members if subteam pick leader/driver of project what is most immediate next step?	20	steering committee	Everyone participating. Alison will lead project. Next steps: Everyone look at the folder of stuff CDL put together about this project (see “Replace VDX with Tipasa” folder in Gdrive, also linked on project page). Specifically, carefully go over product requirements Reschedule the presentation/meeting OCLC had back in December	vdx replacement as a standing monthly agenda item (2nd wednesdays)	@Alison Ray (CDL) add ‘tipasa requirements’ to 4/13/22 rs ost agenda Apr 7, 2022
4	Problems with journal issue or article requests				Sabrina has identified an issue where Physical Loan requests are being passed from Alma to VDX and WSILL as CNR requests. This is probably happening everywhere. Maybe due to OpenURL or perhaps the existence of page numbers or other data in specific fields? E-mail resourcesharinghelp@cdlib.org to look at IVEA Sometimes the RLFs (and perhaps other UC lenders too) will create a request on their end as a lender to fill a request that came from them but won’t attach to the original request. This is a fine way to go about things but if this happens lenders need to inform borrower so they can update/cancel the original borrowing request.
5	Digitization request that goes to the “Digitization Dept for Institution”				Sometimes requests come through that can’t get filled via Deliver Digital Documents. How do they get there? We understand that when a request is submitted via the request form and don’t have anything in the volume field it’ll go into the “full digitization” workflow. But volume is a required field in the request form. May be a staff initiated request? Possibly a local hold request converted to resource sharing?
6	Wrap up	Review actions and decisions	5
7	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 Adding UCs into the automatic rota in WSILL - what do we think of this? Is it helpful in filling requests that fall out of the AFN? (Mallory) 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