Functional Area | Change or Additions | Considerations | Action timing, | Comments | Contact person, | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Affected app or module | What has been changed or added that should be noted for this release | What challenges may arise related to this change or addition | 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? | Name of user leaving comment: comment on what you encountered or ask a question @mention Contact person | User name of person that can provide additional detail. | ||||||||||||||||||||
Authorities | Authority deletion moves authority records to the archive and marks MARC authorities as DELETED. By default, the retention policy for archived authorities is deletion after 7 days. |
| |||||||||||||||||||||||
Settings > Circulation > Fee/fine > Overdue fine policies. Reminder Fees | Enhancement of the business logic for scheduling Reminder fees is implemented. Possible to set up and send reminders to patrons via as printed mails. | The print jobs are running once every 24 hours. This is set in the Okapi timer. | Access via the Users app to the Patron notice print jobs. Two new user permissions has been introduced
| ||||||||||||||||||||||
Users (Profile Pictures) | When enabled Profile pictures can be attached to user records, either with a link to an externally hosted image, or by uploading a local file. Images are stored in the database by default, but can be configured to use Object storage. Supported file formats: jpg, jpeg, png To enable profile pictures functionality, set the maximum allowed file size, and for details on configuring Object storage, follow the instructions included in the mod-users readme documentation. |
|
| ||||||||||||||||||||||
Search, Inventory | To make mod-search consume all types of changes for instances, holdings, items, and changes related to bound-with functionality it has a consumer with a default Kafka topic pattern: (${ENV}\.)(.*\.)inventory\.(instance|holdings-record|item|bound-with) | If the library requires the default behavior of mod-search, please ensure that the KAFKA_EVENTS_CONSUMER_PATTERN is either omitted from the environment variables or is set to the same value as the default pattern. | |||||||||||||||||||||||
Acquisitions | This is only relevant for people directly using the mod-finance or mod-finance-storage transaction API. | Replace deprecated calls if needed, before Ramsons. | |||||||||||||||||||||||
Data export |
...
This is only relevant for libraries that custom scripts to export inventory data. In Quesnelia, Imod-data-export migrated from RMB to to spring and two contracts in API |
...
calls have been modified:
|
...
|
...
|
...
|
...
|
...
| Re-test existing scripts against Quesnelia version of mod-data-export |
...
to ensure no updates are needed |
|