07207893: Reopen 07029351: Issue of Course Icon not displaying on records is persisting
Case Number | 07207893 |
|---|---|
Case Title | Reopen 07029351: Issue of Course Icon not displaying on records is persisting |
Date Opened | Jun 26, 2024 |
Date Resolved/Closed |
|
Resolution |
|
Time Between Dates |
|
Case Description
The Course Indicator is not displaying on all appropriate records. This was originally reported in ticket 07029351.
Despite the June 2024 release to fix this problem, the issue persists in some records and we cannot isolate the cause.
When we navigate to affected records using "Display in discovery" through the Alma interface, each record displays the Course icon as expected.
When we navigate to these records through the Everything search scope in Primo VE, only the 2020 version displays the Course icon.
When we navigate to the records through the Course Reserves search scope in Primo VE, all three records display the Course icon as expected.
We need the Course icon to appear on all appropriate records in all search scopes.
Summary
Issue: The fix for the problem reported in 07029351 did not, in fact, fix the problem.
Support's Response:
Explanation that the fix primarily addressed records owned by the current institution (IZ) and that sorting by NZ owner was not currently supported.
User Concerns:
The initial fix did not address the issue for records linked to the NZ, impacting collaborative networks.
The suggestion to submit sorting by NZ owner as a product idea implied a lack of initial design consideration for collaborative networks within Primo VE.
The user expressed concern that the experience for collaborative networks was inferior to that of individual institutions.
Case Comments
User | Created | Comment |
|---|---|---|
6/26/2024 2:02 PM | Hi Jessica, Thank you for these examples. I am going to attach these to the original issue for Development team to review. Thank you, Natalia Entin | |
8/12/2024 1:40 PM | Hi Jessica, Development team have investigated this behavior and provided the following clarification regarding the 'sort_by_owner_group' parameter. When that parameter is set to true, the IZ records that are not linked to the NZ will be preferred in DEDUP and FRBR groups. For IZ records that are linked to NZ, the sorting will be done randomly by the NZ regardless of the IZ owner of the linked record. In examples provided in this case, all records are linked to the NZ and can not be sorted by the owner institution and therefore the preferred record is not the IZ course reserve. The ability to sort by the owner of the NZ record would need to be submitted as a Product Idea as Primo is not currently designed to provide that option. Natalia | |
8/12/2024 2:55 PM | (The following is not your fault, Natalia. You're just the messenger here. You've been great on all of these tickets. /thumbsup)
We made it clear in our discussion on February 22, 2024, that this problem was affecting Network Zone records, and we needed a solution that worked within a Collaborative Network. The fix only applying to IZ records shows that the development team missed the mark and didn't address the core issue reported in ticket 07029351. This isn’t a minor enhancement—it’s a critical functionality that has been fixed for everyone except Collaborative Networks. Our user experience (and the experience of our library patrons) shouldn’t be worse simply because we’re part of a collaborative network. The statement that “the ability to sort by the owner of the NZ record would need to be submitted as a Product Idea as Primo is not currently designed to provide that option” suggests that Primo VE was never designed to support collaborative networks. If so, that would be a fundamental oversight when developing a product that integrates exclusively with Alma. Given that Alma effectively manages collaborative environments, we expected Primo VE to support collaborative networks without us having to request basic functional parity with individual institutions. The current situation is unacceptable, and I strongly urge the development team to prioritize fixing this issue so that all users, including those in collaborative environments, have equitable access to the product’s features. | |
8/13/2024 11:54 AM | Hi Jessica, Thanks very much for the feedback. We are taking it to the Primo VE Product Management team and will update after we review it with them. Thank you! Jack Boettcher | |
9/24/2024 4:12 PM | Hi Jessica! I am attaching this case to an open issue in development together with case 07207975. Thank you! |
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu