DITF April 12, 2024 Meeting

Linked data group

Update: Proposal being sent to STIM and COLD for 2 new exploratory groups - 1 for ULMS/MARC and 1 for DigRepo/other-metadata - to be supported in AY 2024/25. These groups to come up with proposals for time and funding needs to train CSU library teams in AY’s 25-30

Discussion:

CH: getting the issues on COLD’s radar, especially with new deans - it’s finally coming! it’s actually here! All the campuses will need to be involved. For May COLD meeting
CL: Is this more on the Repository or Alma side?

HC: resource types and how will this effect us? It' will be interconnected
CH/JS: So how do we control what the data is that is being brought in

CO: Reference highlight is turned on at Baker - only campus doing it – pulling in reference from Wikipedia

Relevancy ranking and view settings (See spreadsheet)

Update: None from Jill - she did not get around to sending that email.
Any new testing from all of you?
CH: discover anything interesting from Support ticket review?

Discussion:
CL : Change the score and and see the date range - Institution boost didn’t work within a certain date range - test title “Immense World” - boost changes when you add the date range parameter and it changes not in the way we’d expect. She’s putting in a ticket.

Title/portfolio matching

Update: ERM group found a solution that works for e-resources which come from, or can be put into collections. The solutions involve changing ViewIt settings for e-resource collections to eliminate
CH: discover anything interesting from Support ticket review?

Discussion:

fuzzy title matching was recommended to everyone: Jill has long explanation on why this is not a sufficient solution for short titles although it has potential to help with long ones.

Looking forward to hearing updates from ERM

Parameters to turn on in ViewIt or Display Logic

Support cases

CH: Support cases related to GTI (43 cases) - 9 times, ExLibris fixed something - 1 time ran DeDupe index - 5, fix in a release - A LOT of we can’t fix it.

General view settings

Other services: Newspaper search, Highlight reference, etc.

CL: Personalized search - changes search ranking - problem is that it isn’t obvious
It’s a recommendation from ExL, but mostly makes things confusing

Voice search - really low - but is it needed for accessibility? CW: doesn’t think it’s necessary because the site is already optimized - not need for compliance

To-do for CH: look at which schools have which boxes checked in the main view

Open

Other ideas

Discussed use and integration of LibApps modules into OneSearch

CW told story about test done as SacState where a “Unicorn party” was put on the calendar through LibCal. The team forgot it was there as a test, and students asked the reference staff about it wanting to attend. So SacState team turned it into a real thing that they hold every semester.

Central package

HC does a lot of local coding and updates that she tests in the Dev environment. She used to use the Central Package code on GitHub to revert or get updates but it’s been moved

– Follow-up 4/22: CH discovered that CO didn’t want to have a presence on GitHub anymore so they moved to the package to a more secure site. CH gave this information to HC

Faceting

Update: SJSU doing UX Cafe-style testing in two weeks to get student feedback on facets. Will be held on 4/24, Jill will report back

FRBR and Dedupe

Update: Jill experimenting in SJSU test view

Resource and material type

Update: For secondary resources we’re going to do one more presentation for RMFC groups and then go forward with copying over agreed upon resource types.

Addendum

Norm rules for search and discovery

From discussion on 4/18 after Secondary resource type forum

CW brought question to team regarding display of MARC 130 over MARC 245 as title information in OneSearch. This started a discussion about the use of 130 as uniform title and why the NZ group originally added it to the title norm rule. Discussion resulted in two action items:
1. plan