Known Issues
General
App | Known issue | Workaround | JIRA issue | Product Owner |
---|---|---|---|---|
Title level requests | Recalls are unevenly distributed when there is no item to page and there is at least one item that is not checked out but is "available" for a recall to be placed upon |  | @Stephanie Buck | |
Inventory (mod-search) | Call number browse using call number prefix/suffix in search string doesn't show an exact match | Do not use prefix/suffix as a part of search string for call number browsing | @Christine Schultz-Richert | |
Inventory | Effective location (item) facet: In this release, if items on a single Instance have call numbers of different call number types, when browsing by a specific type, the locations of all items on that Instance will appear in this facet. |  | @Christine Schultz-Richert | |
Inventory | Effective location (item) facet: In this release, when call numbers have a type and a custom location, they will not show in call numbers (all) option. Will be addressed in future refactor. |  | @Christine Schultz-Richert | |
Bulk edit | Query tab has been hidden until the backend work is completed. |  | @Magda Zacharska | |
FQM/Lists | FQM queries can be very slow, depending on many factors. This is most visible in the new Lists app. | Avoid using the "contains" operator for string fields. Instead, prefer the "=" and "starts with" operators when possible. Also, provide as many filtering criteria as possible when creating queries. |  | @Kathleen Moore |
Inventory | Call number browse: If the call numbers on holdings on different instances contain the same first 10 characters of the shelving order, the preceding records will not be returned |  | @Christine Schultz-Richert | |
Settings > Circulation > Fee/fine > Overdue fine policies. Accordion: Reminder Fee | When viewing the new accordion Reminder fee, the first five selection options are frozen:
This is new work being worked on for Quesnelia (R1 2024) |  | UXPROD-4478: Hebis: Implement Reminder Fees for German Libraries (Quesnelia) Closed | @Florian Ruckelshausen@Charlotte Whitt |
Settings > eholdings > Create a new Knowledge base configuration | Customer ID and password fields are auto-populated with FOLIO login details due to Chrome browser not autocomplete = off. See https://bugs.chromium.org/p/chromium/issues/detail?id=914451 |  |  | @Khalilah Gambrell @Denys Bohdan |
ECS: Inventory > Call number browse | In member tenants, when users select a tenant in the Held by facet for a tenant other than the one that created created the call number will result in the placeholder being placed at the top of the results list regardless of alphabetical order. |  | @Christine Schultz-Richert | |
ECS> Loading authority records and adding a tenant | If shared authority records are already loaded into the central tenant and a new member tenant is added, shadow copies are not created in the new member tenant so users cannot link shared MARC bibs to shared MARC authorities. | Ensure all member tenants are created before loading shared MARC authorities. | MODELINKS-171: Spike: Implement data propagation for new consortium member tenantsOpen | @Christine Schultz-Richert |
Circulation/inventory | We have observed performance issues in operations which involve publishing Kafka-events on Orchid and Poppy Bugfest environments. Processes such as check-ins, check-outs, requests, loan updates and others would occasionally freeze for 10-20 seconds. | The issue was fixed by pointing Bugfest environment to a dedicated Kafka cluster instead of the one shared by 40+ environments. If you observe similar issues on your environment, and you are using a shared Kafka installation which is under high load, please consider using a dedicated Kafka. |  | @Alexander Kurash |
ECS: Inventory > Search | Effective location (item) & Held by facets
| Users may have to click the "+More" button more than once to see the remainder of entries. | UIIN-2725: consortia environment - facets not populating - held by, effective locationClosed | @Christine Schultz-Richert |
Inventory > Instances | After migration to Poppy, it has been occasionally observed that Instance Matched IDs fell out of sync, which can lead to multiple ‘ACTUAL’ state underlying records. | Script can be run to clean up inconsistent Matched IDs and record states: Clean up records with inconsistent matched id values | MODSOURCE-666: Create script to clean up records with inconsistent matched id valuesClosed | @Ryan Taylor |