2022-04-13 meeting notes

Attendees

  • @Patrick SHANNON (Unlicensed) , UC Berkeley

  • @Jason Newborn , UC Davis (vice chair)

  • @Linda Michelle Weinberger , UC Irvine

  • @Demitra Borrero (Demitra Borrero), UC Merced 

  • @Sabrina Simmons , UC Riverside 

  • @Mallory DeBartolo (Unlicensed) , UC Santa Cruz (note taker)

  • @Scott Hathaway , UC Santa Barbara

  • @Ryan White , UC San Francisco

  • @Alison Ray (CDL) , California Digital Library (chair)

  • regrets: @Peter Devine , UC San Diego ; @Sandra Farfan-Gracia , UC Los Angeles 

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

(standing item for 2nd Wednesday): Tipasa

make new (gdoc, gsheet, or confl page)? to record requirements

Discuss / brainstorm requirements of Tipasa

45

all

What are we doing with this “requirements” document?

  • This is a list of features that we would value in a VDX-replacement. Does this still stand? Define “what do we need Tipasa to do?”

  • Will eventually meet with OCLC to talk about how they integrate with Alma. We need to come to that meeting prepared to ask for what we need Tipasa to do and see how OCLC can meet those needs.

  • Do we need to define what might happen if Tipasa fails to meet minimum requirements?

Group reviewed line items in the RS OST Tipasa requirements doc, added and edited.

Alison made a copy of the “Deal Breaker Product Requirements…” to live in the RS-OST gdrive.

 

Next Tipasa Two-wednesday discussion: think about what a meeting with OCLC might look like. What would be included in that meeting agenda?

 

3

 

 

 

 

 

 

 

4

Wrap up

Review actions and decisions

5

 

 

 

 

5

Parking Lot

Capture important topics for future discussion

 

 

Next Tipasa Two-wednesday discussion: think about what a meeting with OCLC might look like. What would be included in that meeting agenda? May 11, 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

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)

 

 

 

6

 

Total

x/x

 

 

 

 

 

The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu