Lotus (R1 2022) Release Notes

circulation-logs.collection.get

Before upgrading Okapi:

Upgrade mod-data-export-spring to 1.2.3 that has the permissions been fixed.

Set DB_ environment variables for mod-inventory. For details see RMB readme.

Note: This is about mod-inventory, not mod-inventory-storage!

Before upgrade:
Change all duplicate externalSystemIds.
This SQL lists only the duplicates:
SET search_path TO diku_mod_users;
SELECT left(lower(f_unaccent( jsonb->>'externalSystemId')), 600)
FROM users
GROUP BY 1
HAVING count(*) > 1;

Use User Keyword search to edit the duplicate externalSystemIds until the SQL query result is empty.

The admin user should have perms.assign.permissions-class of permissions to be able to hand-out permissions that are not owned already. See https://github.com/folio-org/mod-permissions#introduction

If migrating from earlier version mod-permissions, the admin users will automatically be assigned these. This is done in mod-permissions tenant operation itself . 

Browser vendors (Chrome, Firefox, Edge) restrict cookie usage across different sites resulting in SSO failure with "CSRF attempt detected" error message.

• statistical code doesn't exist: eeb7fef6-bd65-4cd8-81bc-1c2d91551b94: foreign key violation in statisticalCodeIds array of item with id=9428231b-dd31-4f70-8406-fe22fbdeabc2
• invalid input syntax for type uuid: "foo"

If there is an invalid statistical code id the migration neither fails nor cleans up the invalid id.

However, an item that was accepted in Kiwi can no longer been created in Lotus. Changing the list of statistical codes of an existing item fails unless all statistical codes exist; updating an item without changing the list of statistical code ids (= only changing other properties) always succeeds even if it contains an invalid statistical code id.

Before or after the migration:

Manually clean up invalid statistical code ids in all items.

Manually add missing statistical codes in Settings/Inventory/Statistical codes.

Inventory search supports now browse functionality by call number and subject.

The call number browse is based on the item record's shelving order and it covers browsing LC, Dewey Decimal, NLM, SuDoc and Local call numbers.

The subject browse is based on  the Subject field of inventory instance records. 

Browse functionality requires:

• granting Call number browse: View permissions  and Subject browse: View permissions
• Item's shelving order field need to be populated (by running migration scripts that are part of mod-inventory storage)
• full re-index with recreating indexes 

• Migration script information:  Async Migration. Guideline and Performance results

• Reindexing information: https://github.com/folio-org/mod-search#recreating-elasticsearch-index

Inventory search supports now MARC Authorities search and browse functionality for call number and subjects

Inventory search support search on All data properties across all three record types. 

mod-search indices will need to recreated as described here

This search is a powerful tool, but can have implications on performance.

IMPORTANT: See documentation here.

During the upgrade process.

The search option need to be enabled in the given FOLIO environment. See the mod-search README for details on how to configure.

• Subpermission changes: remove ui-users.loans.edit and add ui-users.loans.change-due-date
  • (It appears that ui-users.loans.edit was renamed to ui-users.loans.change-due-date in December 2020 - https://github.com/folio-org/ui-checkout/pull/566 - but the change did not happen in ui-users.loans.all)
• Remove from ui-users.loans.all the ability to:
  • declare an item lost
  • mark an item claim returned
  • mark a claim returned item missing
  • anonymize a user's loans
  • renew an item through override 
• Change the display name (and associated translations) for ui-users.loans.all to "Users: User loans view, change due date, renew"

• removing ui-users.loans.edit should have no effect 
• For users who currently have ui-users.loans.all assigned, if you need them to be able to continue to declare item lost, mark item claim returned, mark claim returned item missing, anonymize user loan, renew an item through override, you will need to assign those users that functionality with the additional individual permission for the functionality

There will be references to title level and title level requests in the Requests detail pane that cannot be suppressed or removed at this point. They will make sense and be functional with Morning Glory.

This migration includes breaking changes in the requests schema. Among other changes, fields "requestLevel" and "instanceId" are now mandatory. Affected modules are mod-circulation, mod-circulation-storage and edge-patron. Please see this page for more information. 

In Request details where a placeholder ID 00000000-0000-4000-8000-000000000000 is used to replace a missing holdingsRecordId and/or instanceId (to allow for data migration to complete), the following occurs:

existing item + existing holdings + existing instance = page loads normally
deleted item + existing holdings + existing instance = page breaks, something went wrong error
deleted item + deleted holdings + deleted instance = page breaks, something went wrong error

This should be considered at time of upgrade if you plan to export orders in edifact format with the Lotus release.

It can be adjusted post upgrade but you will likely have failed exports in the mean time and there is no easy way to "Re-export" orders in this release.

Starting with Lotus HF1 mod oai-pmh provides APIs for monitoring the harvesting process as documented in the READ.ME file.

Results of the performance tests when running multiple full harvests concurrently can be found here

The settings change  will required restarting the module

The relevant module descriptors will be updated for Morning Glory release

mod-kb-ebsco-java,

mod-pubsub