Nolana (R3 2022) Release Notes

When can the action be taken (before, during or after upgrade)?

If applicable, detail what action(s) must be taken here

Is this action required for the next release?

When upgrading upgrade Okapi to the latest 4.14.x version, at least 4.14.10.

v4.14.9 has a bug that sometimes closes the HTTP connection before the response has been sent.

Versions before v4.14.8 have a Hazelcast vulnerability: https://nvd.nist.gov/vuln/detail/CVE-2022-36437

Update to the default MARC Bib-to-Inventory Instance MAP:

• Existing mapping for 590 (Local note) updated so that 1st indicator = 0 triggers "Staff only" indication. Any other 1st indicator does not.

If you would like to review the mapping change first, go to https://github.com/folio-org/mod-source-record-manager/blob/master/mod-source-record-manager-server/src/main/resources/rules/marc_bib_rules.json and search for 590. Review that section of the rules, and then if that handling is wanted for a particular library tenant, add that section to their equivalent map.

After upgrade, library may want to review their local default MARC Bib-to-Inventory Instance map, and decide if they want to add this revised mapping into it.

Follow the instruction to update the rules.

Edit: UICIRC-766
View: UICIRC-767

Julie Bickle 

Permission ui-tenant-settings.settings.enabled - display name "Settings (Tenant): View" has been made invisible

The permission is used to grant basic view to Settings > Tenant but grants no other functionality. It implies that you can use it to give view-only access to content in that area, which is not the case. Making the permission visible: false removes that confusion.

Recommend removing "Settings (Tenant): View" from any users prior to upgrading to Nolana.

You can also remove the permissions after upgrade by enabling Settings > Developer > Configuration > List invisible permissions in add perm menus and then editing the relevant user records.

Update your users' permissions and/or permission sets, as required. 

Recommend removing "Settings (Tenant): View" from any users prior to upgrading to Nolana.

Actual cost will not be fully implemented for Nolana.  It is recommended that you wait until Orchid to start using actual cost. 

If you start using actual cost in Nolana, the “Lost items requiring actual cost” processing page will not be available for billing.  This means that you will need to bill actual cost via a manual fee/fine that will NOT change Item status from “Declared lost”/”Aged to lost” to “Lost and paid” when the fee is paid. 

If you started using actual cost in Nolana, when Orchid is implemented you will need to you will need to mark items as “do not bill” on the “Lost items requiring actual cost” processing page if fee was billed manually.  The "Lost item fee policy" includes a setting For lost items not charged a fee/fine, close the loan after <interval>.  Using this setting to "expire" actual cost lost items will eliminate the need for this if you set the <interval> to a smaller time period.

Permissions provided by ui-calendar 7.x have been updated to more specific ones; most notably, this includes the ".all" permission.  Administrators may want to go through user's permissions and re-evaluate what is necessary with these new specific permissions.

The database schema used for mod-calendar has been overhauled, however, no special action is required.  As part of the upgrade from 1.15.0, all existing data will be transformed and preserved.  If you are not already on mod-calendar 1.15.0, we recommend upgrading to it before upgrading.  Be sure you are upgrading to the latest version 2.3.1 as previous versions would migrate certain exceptional situations incorrectly.

We recommend going through the calendars post-migration and ensuring that all exceptions transferred as expected; exceptions that were not fully contained within a calendar (for example, calendar 01-01-2022 to 12-31-2022 and exception 12-25-2022 through 01-02-2023) may result in a calendar shown as an "Orphaned exception" in the interface or, if there are multiple exceptions/calendars for a date, it may not be transferred at all.  System administrators can also search through the container logs for more information about what exceptions were associated with which calendars (which will display error messages if any exceptions were orphaned or dropped).

After the migration, institutions may desire to clean out historic calendars (this was impossible in the previous interface); this can be easily accomplished with the new purge feature.

 Use MARC authority app 

• Add loadReference=true to tenantParameters 

When initially enabling mod-inventory-storage for a tenant a few locations and location units (institutions, campuses, libraries) can automatically be created. Before Nolana loadReference=true triggered this, from Nolana on loadSample=true is needed.

Adjust scripts that expects them as reference data.

During the upgrade process before reindexing

Set environment variable INDEXING_DATA_FORMAT = json

Mapping rules were changed. It's required to update default mapping rules in the database. 

Apply after mod-source-record-manager upgrade. Please do the following actions. 

1. Call endpoint PUT {{okapi.url}}/mapping-rules/marc-authority/restore
2. To apply mapping rules changes to migrating authority records - run this standalone application - Marc Authorities update instructions (Recommendation to run during non-working hours) 

If library contains more data in the specified settings override the property "srm.mapping.parameters.settings.limit" (default=1000) when mod-source-record-manager is deployed.