2023-12-01 Meeting notes

Attendees

  • Gem Stone-Logan, California Digital Library

  • Sean Claudio, UC Irvine 

  • Jess Waggoner, UC Santa Cruz

  • Zach Silveira, UC San Francisco

  • Jared Campbell, UC Davis

  • Douglas Worsham, UC San Diego

  • Joe Ameen, UC Merced

  • Zoe Tucker, UC Los Angeles

  • Jessica Kruppa, UC Riverside

 

Not Present

  • Jackie Gosselar, UC Berkeley

  • Michael Craig, UC Santa Barbara

  • Joshua Gomez, UCLA, UX Subgroup


Meeting Recording: https://drive.google.com/drive/u/0/folders/1HHdEBRm0_L3LJICWgH_X-nSIG-jReKkR

Item

Est Time

Desired Outcome

Notes

Decisions / Discussion

Actions

Item

Est Time

Desired Outcome

Notes

Decisions / Discussion

Actions

1

Sharing and Updates

10

Share any Discovery related information from other SILS groups

LG:

  • Considering shared documentation options, particularly now that UCSD is sunsetting where they currently keep their public documentation. So they’re interested in having a systemwide conversation around sharing documentation.

OT:

  • UCB noticed there’s a bug with Primo VE on mobile where when typing a query the text starts to overlap (06969846)

  • There’s a cataloging quirk with the 590 local extension when using the space bar (06957497)

  • Clarifications from Ex Libris about what timelines from Ex Libris means:

    • when far off dates are given, ExL may not have actually looked at the issue yet

    • “pending release” - currently in QA

    • “version commitment” - not as firm as “pending release” but pretty solid

  • At the support meeting we also discussed real time updated on linked accounts (06961548)

  • Discussed the current status of the Signature Success meeting with Adriana which included presenting our beefs document. Adriana has requested we prioritize. Currently NZ functionality and IZ/NZ integration is listed as top followed by insufficient support and limited documentation.

  • Discussed the proposal for expanded NZ access but we ran out of time so will be discussing it more at the next meeting.

  • UCSC is interested in a best practices doc for Kanopy kbase. They’ll start and then share with everyone.

All-Chairs:

  • ERES is working on creating a “Best practices for writing a support ticket” doc and then will sharing it with the other subteams.

  • RM has submitted a proposal to expand NZ access which will go to OT. They’ve also restricted the ability to add 590s to NZ bib records. They’re planning an all-UC sharing session on bib maintenance in January.

  • Fulfillment is pausing until January.

  • Resource Sharing: Author field is not populated in resource sharing form.

  • Group discussed a problem in acquisitions with interested users holds getting canceled. This appears to be a behavior change from the past, prior to migration, so we’re going to submit a consortia ticket for it.

  • Group discussed the format and agenda for State of the Town Hall. Each subteam will do a 2-3 minute update on what they’re group is working on. This will likely happen toward the end of January.

Accessibility update: No updates since last time.

 

 

2

Slack/General Questions

5

 

Work around for Newsbank articles.

  • Michael wasn’t able to set this up in the IZ because it’s for an NZ resource.

  • Gem set it up in the NZ sandbox but we don’t see any difference. Gem created a ticket with Ex Libris to ask how it’s suppose to work (06972573) but hasn’t heard back yet.

  • No one else has tried this workaround yet.

 

 

3

Exclude CDI eBook Discussion

25

Preparing for information sharing with E-Resources OST.

  • Question: Are we trying to harmonize or create a pros/cons document?

    • We need a better understanding of the pros/cons before we know whether it makes sense to try to harmonize.

  • Summarize what we’ve found in our testing so far

    • UCM: This setting did excluded some records and the results seem a little tighter but haven’t come to any specific conclusions. Don’t think a lot is being excluded that we want to see but do have a bias toward want to see everything even if that isn’t the users' preferred display.

    • UCSC: Love the idea of getting duplicates because they do feel it’s a problem for user experience. Still concerned about missing records found in a handful of cases. Would like to work with e-resources librarian more to find the pattern. Definitely finding missing records.

    • UCLA: Haven’t seen any issues yet. Would like to collectively see problems and maybe identify greater patterns. Reignited the filter by availability discussion. (Currently not filtering by availability.)

    • UCR: The current default search scope has everything everywhere all at once. In the spirit of what the user can get right now, made the UC Riverside catalog search scope which has filter by availability and currently excludes the CDI ebooks – not default and it is still creating some confusion. The users that get directed to the more restricted scope tend to be happier about it. Aren’t having complaints about things not showing up. Personally prefer removing the CDI ebooks.

    • UCD: Default filtering by availability. For the most part, pretty happy with the reduction in duplication. Haven’t found a specific example of stuff going missing that they want. Still trying to figure out why some titles dedup and others don’t (Access Medicine – but parsed into multiple sub collections – CDI also parses into sub-collections). Would like to be able to give an explanation of what the behavior is.

    • UCI: Already has this on.

  • Discovery Summary: Generally we like the reduction of duplication from the user perspective but still have concerns about why some things are missing and haven’t been able to find a pattern yet. Also sometimes seeing things duplicated when not expecting them to duplicate.

  • Ask eres if there are additional areas they feel they need to test or consider

    • Note about testing: make sure testing both with excluding and not excluding in sandbox – talk to your discovery person – due to inconsistency with how CDI work in the sandbox.

  • Request eres evaluate CDI vs CZ record quality and determine

Specific asks for eres:

  • Help us figure out the patterns we don’t understand.

  • Double check we’re not missing anything

  • Provide feedback about record quality in CDI vs CZ.

 

 

4

Next Meeting

5

 

We are going to meet December 15:

  • Recap of discussion with eres

  • Come up with specific NZ/IZ Primo VE problems.

 

 

5

Next Steps

5

 

 

 

 

6

Parking Lot

 

 

Report on feature testing: January 26

Next Primo VE release meeting: February 23.

 

 

 

 

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