2022-11-02 RS OST meeting notes

record meeting

make sure Alison records meeting

1

Alison

Update from “which hybrid model” lightening team

• Definitely ruled out direct FN (too much impact on patron workflow)

• Next project: configuring P2P (assumption? high priority b/c reduces things falling out of AFN)

  • needs another partner for configuring & testing (either non-sb Tipasa (M or SF), or would limit Alma/Tipasa testing for piloter); NZ involvement not recommended b/c of simultaneous different test in different IZs (some investigation on configuration started)

  • Getting ExL’s help/assistance/guidance with configuring

  • Timeline? What coord with Tipasa golive? start now? how much effort? how often?

25

Sabrina, Mallory, Alison

what needs do we have for tipasa patron interface (what is “My ILL Requests” being used for now)

Get a set of hypothetical use cases for potentially utilizing (or decommissioning use of) separate extra-consortial requests

15

All

Wrap up

Review actions and decisions

5

Bike Rack

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

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…

Total

x/x