May/June 2022 ULMS Update
- brandon dudley (Unlicensed)
Project Management
Discussions with Ex Libris regarding Top Issues continue. We are seeking to receive responses from all outstanding issues by mid-July.
ELUNA 2022 sessions were held over May. Presentation materials are available here.
ULMS Committees will turn over on July 1st of this year. Committees will form over the rest of the summer and start meeting at the beginning of the fall semester. Thanks to those of you who were interested in joining a committee!
Analytics
Working Group
The group is exploring ways to help with Rapido Analytics for the CSUs (either the Rapido groups or the Resource Sharing Functional Committee). Chris shared a good set of already existing Rapido OOTB Analytics at /Shared Folders/Rapido/Reports and /Shared Folders/Rapido/Dashboards.
Jung Ah, Brandon, and Christina H met with Ex Libris product management on April 27, 2022 about COUNTER/SUSHI reported issues from the CSUs. The meeting was very productive and should improve COUNTER/SUSHI issues in the Alma product for all.
However, there has been no activity on the top 3 Analytics issues given to Ex Libris since our last meeting and since our follow-up with those that gave us more detail on those issues. Our reported issues were:
Analytics for Alma & Primo VE configuration changes and who changed them, retaining the whole history of each field change;
Reporting from Primo Analytics too limited;
Reporting on NZ-managed e-resources too limited
We had great accomplishments on cleaning up the wiki and getting the Analytics folders clean and reorganized. We did a review of GreenGlass vs. Ex Libris Analytics and the pros and cons for each. We continue to share recent free outside webinars and training opportunities on Analytics and Assessment on the wiki home page for all the CSU (and the world) to use. We kept up with CSU Analytics & Assessment questions in Slack, on the listserv, and through email. Also not listed on the goals: we created a survey to get information about the top issues for Analytics across the CSUs, followed up on those issues, and also to get interest in training & future webinars.
There was a helpful recent discussion (May 2022) on ALMA-L about backing up Analytics reports and protecting Analytics reports from deletion and overwrite through permissions. The committee will make a wiki page with this information and recommendations.
The Resource Sharing group reported that some of the reports & dashboards needed to be updated to reflect the new name for Humboldt State University (Cal Poly Humboldt) as the data was now incorrect for that institution. SOme have been fixed but others may need to be modified.
Resource Management
Working Group
The Local Fields in Alma & Primo VE page at Confluence has been updated to show the list of all local fields (extensions) used by the campuses who reported their local extensions' usage.
The NZ Management Group has completed the update of the NZ normalization rule for all incoming bibliographic records in the NZ per the Inclusive Description Task Force's Recommendation. This normalization rule will now transform "illegal immigration" into "immigration" and "noncitizens" and instances of the term into "undocumented immigrants." No other action from campuses is required at this time except to report if this transformation does not take place.
The Top Three Resource Management issues and Ex Libris' comments were discussed. Ex Libris offered information on working/advisory groups that are addressing the quality of metadata/records and CDI support (CZ Management Group, CDI Advisory Group, dedicated CDI Team). One of the future goals of the RMFC is to gauge the level of participation and bandwidth the CSUs could have to participate in or contribute to these other working groups.
The Inclusive Description Task Force is working on an inclusive cataloging statement and accompanying reporting form. The Task Force is also working on procedures to handle outdated American Indian subject headings. The RMFC and Brandon have been informed and work will continue in the upcoming year.
ERM
Chancellor’s Office
Updated NZ licenses with updated subscription information
End of FY purchasing
Retired the old SFX/Alma Merged/Shared collection list
Data can be collected a couple of ways in Alma
Duplication of tasks that are no longer needed.
Worked with ERM working group on a new public note for journals that do not have complete full text
Note to users to use ILL to submit a request
Not all journals have full text access to articles, even if it falls within FT coverage dates
Added DEI collections from EBSCO, ProQuest, and Adam Mattew, to the NZ
Resources paid for by the CO
Working Group
Summer projects
Update ULMS ERM wiki
Setup Alma Agreements tool
Licenses
Is there an easier way to get licenses approved by procurement on campus?
Jessica mentioned that she’ll bring this up to the new License manager at the CO’s office. .
Resource Sharing
Chancellor’s Office
Rapido went live on June 13. A HUGE thank you to the resource sharing community for all the hard work to make this happen. A special thanks to Joe Gerdeman (LA), Stacy Caron (Fullerton), and Meghan Weldon (Humboldt) for their work during the Rapido development phase.
Working Group
Worked with Chris to modify Rapido pull slips.
Identified a need to review and support community clean up of lost and overdue items.
Identified a need to work with fulfillment on the walk in user policy.
Fulfillment
Chancellor’s Office
Continued to work with the Fulfillment Committee on policy development
Working Group
Reviewed the feedback from Ex Libris regarding the “In Transit” issue and decided there was not further feedback to give
CSU Walk-In Policy
Discussed with Steering Committee about turning the recommendation document into a formal policy
Reviewed document for feedback from FFC members
Chair and Vice-Chair will be meeting to work on finalizing the document
In June the FFC reviewed the CSU Walk-In User Policy and updated it to be reviewed and sent out the listservs when the new committee begins.
Discovery
Chancellor’s Office
Continue to work with ExL for responses on Top Issues
Working Group
LibKey Demo: The product has some nice features, but the group had reservations about implementing a third party tool to provide functionality that should be a part of Primo VE. This could be a deterrent for Ex Libris to allocate development resources towards improving Quicklink and Unpaywall services if a third-party tool already exists. We will ask the vendor about pricing and technical specifications for implementing the product.
Customer Satisfaction Survey: the DFC put forth the top 3 discovery issues to Ex Libris and have already received some initial feedback from Ex Libris. The issues put forth were:
uResolver Matching Issues: title-based matching continues to produce incorrect links on records
Features Not Working as Expected: LC Browse Search, Date Newest facet, Search within, Ranking and performance features either don't work as expected, or have limited configuration options or documentation.
Inadequate Analytics for Assessing Performance and Usage of Primo VE: lack of web usage statistics makes it difficult to determine where and how users access Primo VE.
Quick Links: Some campuses have turned Quicklink functionality on, but discovered that they are also a part of newspaper search and are not being proxied. A salesforce case has been filed and Ex Libris indicated it should be fixed by November 2022.
Discovery Open forum: The DFC hosted our final open forum for the year, with a focus on discovery changes as a result of implementing Rapido. Chris Lee provided an overview of the changes to the discovery UI/UX that will need to be configured to implement Rapido. Details of the changes are available online at Discovery and Rapido .
The DFC continues to work with Ex Libris on the discovery satisfaction survey top-3 issues. The issues presented to Ex Libris are:
uResolver matching issues
features not working: lc browse search, date newest filter, journal search, ranking, performance issues
inadequate analytics for assessing performance and usage of Primo VE
Ex Libris has provided some initial answers and acknowledges that some issues are being addressed via salesforce cases.