2023-04-12 RS OST meeting notes

record meeting

make sure Alison records meeting

1

Alison

items being kicked out to WorldshareILL at end of ROTA even though we have those items in our catalog

Is UCM affected moreso than other campuses?

See if there’s something to be changed in UCM’s config? (Alma and/or Primo)

15ish?

Demitra

Requests were submitted and then ended up in VDX but when placed again in Alma they went through just fine.

March 2022 we updated settings (Local Profiles) to address this issue but it wasn’t a 100% fix.

Merced seeing a recent uptick in the issue.

Berkeley tried to spot check and figure out what’s going on with this issue but couldn’t see a pattern or any specific issue. Kristen thinks it’s that patrons are requesting from bad records.

San Diego suspects older records are being used for requests. Not seeing a ton of requests like this.

Santa Cruz saw lots of little reasons why things ended up in the Not Supplieds when they tracked a while ago:

‘wrong’ records: no identifiers; ebook records; FRBR-ized records showing a crummy record first

The ‘blank ill form’ also influences how (and if) item can be found for AFN

Demitra will go on a fact finding mission and come back to the group.

update on P2P config

just an update

5

Mallory

small team met earlier & went through ExL’s instructions to set up P2P in SF & M sandboxes.

next step (after configuration): send some test requests through.

When someone has to leave the team and we have some advanced notice of departure

Should there be overlap so the person can onboard projects gradually?

5

Scott

We can address as things come up. In some cases a brain dump and one meeting overlaps should be sufficient.

In the case of UCSB we can slowly transition SB off the Tipasa project since we have adequate coverage on that project.

Place to share code-y things and/or analytics (like JCN’s analytics example shared via email…)

Come up with a spot (other than/in addition to email) to share analytics

12ish?

Alison

Maybe email is good enough????

Analytics: shared folders? (Catalog > Shared Folders > Community > > Reports > Consortia > UCS > ILL and Resource Sharing)

XSLT: github? (wait until there’s an example to showcase github)

Stuff stuck at LA/Berkeley that already went to RLFs

show and tell reports!

Jason

Built a set of nesting reports that identify things rejected by an RLF and then went to LA or Berkeley. Will identify things that fall into this category immediately.

Run one report for each pair/region (1. Berkeley/NRLF 2. LA/SRLF)

Should be able to run reports as-is but if you

But also beware! Sometimes LA DOES have a copy to supply.

Jason putting in shared analytics folder (breadcrumbs above)

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