2022-09-14 RS OST 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
@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)
guest: Dawson Kelly, UC Santa Cruz
regrets:
Item | Desired Outcome | Time | Who | Notes | Decisions | Actions | |
---|---|---|---|---|---|---|---|
1 | record meeting | make sure Alison records meeting | 1 | Alison |
| ||
2 | UCLA membership change | let RS OST know UCLA membership shift coming up | 1 | Sandra |
|
|
|
3 | UCLA guest spot for RS Analytics project team | discuss and decide adding in UCLA analytics expert from UCLA | 2 | Sandra | Aileen Madrano guest spot for RS A PT No objections to LA guest spot. |
| Sandra: send contact info to Alison @Alison Ray (CDL) add UCLA guest spot to RS A PT Sep 28, 2022 |
4 | Anonymization flaw workaround page (delay anonymization to gather AFN digitization reports) | Review edits; confirm if good to send to ‘consulting’ groups review next steps (steps after ‘consulting groups’ feedback) | 7 | RS A PT |
|
| |
5 | review Tipasa test plan | completing Tipasa sbs: populate with 10% holdings; three options: *random, *make query collection, *send ocns OCLC asks “Stacy would like to start the deeper discussion of how the API-part of the Tipasa-Alma interop will work. Like, what patron data is going back and forth, and do we have what we need to match for NCIP, and potentially for notifications? “ - someone from 1-3 of testers who have used/are using Alma user API &/or NCIP information to talk with OCLC YES! forward any Tipasa/OCLC meetings to anyone you want how to get “non-cohort” access to “Replace VDX with Tipasa” g-folder (also if they need to just ‘view’ or also be able to ‘edit’) config instructions for alma sb instances | 20 | testers: LA, R, I, SD, SB, D, and B | How to ensure a mix of holdings? Peter submitted, along with his request to use the 10% random holdings, to include a variety of material types. When we test interoperability between Alma and Tipasa we’ll need to know what 10% of our holdings are in Tipasa. How are the sandboxes linked? Test plan will provide more details but broad strokes for now:
OCLC is seeking more information about the API we developed re: patron data sharing via NCIP. Alison pulled in Joe on that conversation and will look to schedule a one-time meeting with other UC subject matter experts via the SILS Ops group. To invite other attendees to Tipasa meetings forward the invite to them! If people need access to the Replace VDX with Tipasa google drive folder email Alison their email and what level of access they need (view or edit) |
|