Important Upgrade Considerations
This section outlines all changes that require special consideration for customers in production. Configuration changes may be needed to prevent operational interruptions. See checklist for guidelines on how to fill this out.
Changes and Required Actions
New Apps
Removed Apps
Permissions Updates
| App | New Permissions | Deprecated Permissions | Product Owner |
|---|---|---|---|
| Dashboard | Dashboard: Dashboard Administrator | ||
| Bulk edit | Bulk edit: In app - Update user records |
Known Issues
General
| App | Known issue | Workaround | JIRA issue | Product Owner |
|---|---|---|---|---|
| Users | Mail notices do not get sent to proxy, even when that value is selected, but get sent to sponsor | Currently no work around; this is new work to do the back-end of what is visible in the UI. | julie.bickle | |
| mod-inventory-storage | Authorities update through quick-marc are applied to mod-search records with a delay of 1 update | Remove DB_HOST_READER , DB_PORT_READER environment variables from mod-inventory-storage. Next authority update will be successful. | MODINVSTOR-1006 | Khalilah Gambrell |
| Export Manager | Files generated by following jobs are available only for several hours due to AWS Identity and Access Management (IAM) instance profile settings:
| Repeat exports again | Magda Zacharska | |
| Bulk edit | Intermittent error "Something went wrong" after rearranging columns while editing holdings record. The error occurs on the Are you sure form before any changes are committed. | Restart bulk edit. | ||
| mod-search | boundWith flag is not updated in mod-search | For mod-search either remove KAFKA_EVENTS_CONSUMER_PATTERN env variable so that the default ($ENV\.)(.*\.)inventory\.(instance|holdings-record|item|bound-with) is used, or add bound-with to your custom pattern. | MSEARCH-458 - Getting issue details... STATUS | |
| Title level requests |
| No known workarounds. | CIRC-1683, CIRC-1684, CIRC-1693 | Stephanie Buck |
| Purging a tenant | After disabling modules with purge option for one tenant other tenants get this error: " ERROR: function f_unaccent(text) does not exist (42883)"This affectes only modules where environment variable DB_MAXSHAREDPOOLSIZE is set. | After disabling modules with purge option restart all modules where environment variable DB_MAXSHAREDPOOLSIZE is set. | RMB-955 - Getting issue details... STATUS | Julian Ladisch |
| All | RMB-348 - Getting issue details... STATUS was implemented to split reading and writing traffics into separate database nodes. While it's working for some workflows (check in/out, MARC BIB/Authority Data import Creates and Updates), it is buggy in other workflows. These are: Acquisition, Data Export, Data Import of MARC Holdings. Additionally in very rare circumstances when a failover happens between the database nodes, such as when the write node fails over to the read node (the read node now becomes the new write node and vice versa), the storage modules may still cache the old addresses so they may continue to write to what is now the new read node or that the old write node has gone out of service). | Remove A workaround for the failover issue is to create an AWS lambda (or some process that listens for failover events) that restarts the RMB storage modules to create new connections to the new database nodes | MDEXP-576 - Getting issue details... STATUS MODINVSTOR-1019 - Getting issue details... STATUS | Martin Tran |
| NCIP | When the acceptItem service is called, if the pickupLocation contains '/' the service will fail:org.z3950.zing.cql.CQLParseException: expected boolean, got '/' | Use the patched version of the module: https://github.com/folio-org/mod-ncip/releases/tag/v1.12.3 | MODNCIP-54 - Getting issue details... STATUS | |
| ERM | When you view a License in the License App that has a linked Agreement, on viewing the "Agreements linked to this license" the Agreement information does not display (only the 'License link status' displays) | Currently no work around; the issue is fixed in mod-agreements 5.5.x | ERM-2638 - Getting issue details... STATUS | Owen Stephens |
Additional known issues
Notes on functionality
PO Release Presentations
| Presentation | Presentation date | Presenter | SIG meeting (link) | Notes |
|---|---|---|---|---|
| Acquisitions | November 1, 2022 | Dennis Bridges | Agenda and Meeting Notes#:~:text=Demo%20Nolana%20Release%20highlights | |
| ERM: Agreements | November 2, 2022 | Owen Stephens | ERM-SIG: | View slide 2-4, and recording from 10:14-37:10 (includes Dashboard 13:45-17:45) |
| Dashboard | November 2, 2022 | Owen Stephens | ERM-SIG: | View slide 2, and recording from 13:45-17:45 |
| Bulk edit | November 10, 2022 | Magda Zacharska | Bulk edit related recording starts at 26:20 |
Post-Release Hotfixes
Hot fix release #1 - RELEASED AT APRIL 20
Tickets list
Modules list
New Features
Nonfunctional Requirements (NFR) Features
Closed Bugs
All Closed Bugs and Stories
Remaining Open Bugs at Time of Release
Support Period
Assuming the FOLIO support policy remains unchanged, Nolana will be supported with critical security and bug fixes until Poppy (R2 2023) release (around April 2023). With the Nolana release Lotus has reached end of life and is no longer supported.