2023-03-01 RS OST meeting notes

record meeting

make sure Alison records meeting

1

Alison

Discuss & Decide on Tipasa project plan outline 2023/2024

Discuss any new feedback from stakeholders, local staff

note/make any changes needed to the decision page

vote!

20

all

We voted! Still need Sabrina’s vote.

Next steps for Tipasa transition (discuss shape of ‘testing phase’)

who/what/when/etc

what sort of ‘starting’ document? (charge? decision page??)

20

all

Need to create a testing doc.

Charge creates structure for internal use and also provides milestones, making it so the project doesn’t slip by and defines when the project would be “at risk”. The “what” and “when” can be a little looser.

Propose that testers define the testing logistics.

Who (interested parties):

UCR, UCB, UCI, UCSB, UCLA, CDL (as liaisoning)

What:

test delivery of OCLC’s fulfilment of gaps; identify any other use cases needed, aside: consider if another sb is needed (for RLF, UCLW??)

When:

whichever is sooner: when gaps are filled or October 2023

Wrap up

Review actions and decisions

5

Bike Rack

Capture important topics for future discussion

‘pick up anywhere exceptions’: review shared messages, what would be next steps
metrics on how often ‘pick up 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…

x/x