Ramsons (R2 2024) Changes and required actions
- Pavlo Smahin
- Stephanie Buck
- Natalia Zaitseva
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. |
mod-search | Implement indexing for inventory locations |
| Locations reindex needed after the upgrade. | Under the hood when specifying resourceName=location the reindex for libraries, institutions and campuses will be started as well automatically. | @Viacheslav Kolesnyk , @Pavlo Smahin |
mod-inventory-storage | Holdings’ |
| No action. | API major versions updated for
| @Viacheslav Poliakov (Unlicensed) , @Pavlo Smahin |
mod-inventory-storage | Instance’s |
| Async migration execution is required after the upgrade. Could work in the background. POST /inventory-storage/migrations/jobs
Body:
{
"migrations": [
"publicationPeriodMigration"
]
}To track status of migration execute the endpoint: GET /inventory-storage/migrations/jobs/<jobId>To validate that migration is finished SQL script could be executed: SELECT 1 FROM <tenant>_mod_inventory_storage.instance WHERE jsonb -> 'publicationPeriod' IS NOT NULL LIMIT 1;If nothing returned then migration was successful. | API major vers ions updated for
| @Pavlo Smahin |
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. |
|
| @Pavlo Smahin |
mod-search | New re-index process implemented for instance records. |
| After the upgrade use new API to index instance records.
| Instructions can be found in: https://github.com/folio-org/mod-search/tree/v4.0.0?tab=readme-ov-file#indexing-of-instance-records | @Pavlo Smahin |
Inventory, SRS, Data import | Default MARC-Instance mapping rules were updated to add:
|
| After upgrade follow the instructions to update the mapping rules. |
| @Ryan Taylor, @Kateryna Senchenko |
Automated patron blocks |
|
|
|
|
|
SIP2 | Setting Up SIP2 for Multiple Tenant-Specific Ports
|
| If any SIP2 customer (e.g. MeeScan) wants to use the feature of using multi tenant for specific port then below configurations settings can be applied https://github.com/folio-org/edge-sip2?tab=readme-ov-file#setting-up-sip2-for-multiple-tenant-specific-ports |
| @Gurleen Kaur1 https://folio-org.atlassian.net/browse/SIP2-150 |
INN-Reach | Redesigned ongoing record contribution to be aligned with the initial contributed outbox pattern design. |
|
|
| https://folio-org.atlassian.net/browse/UXPROD-4860 @Tim Auger |
FOLIO DCB/OpenRS | Modify the logic for creating a virtual service point (for pickup locations) and link up the default calendar. Also, modify default values of the calendar |
| Coordinate the DCB development that populates the creation of the SPs. Coordinate roll-out into production. |
|
https://folio-org.atlassian.net/browse/MODDCB-119 @Tim Auger |
Requests, Staff slips |
|
|
|
| @Anne Ekblad |
Automated patron blocks | Before Ramsons release, running automated patron block synchronization of any scope (“user” or “full”) would result in losing accumulated patron block data related to lost items for affected patrons. This may have affected libraries that use automated patron blocks with condition “Maximum number of lost items”. In order to rebuild lost data and recalculate patron blocks in these libraries it is recommended to run full patron block synchronization: In case if potential data loss is limited to specific patron(s), a user-level sync can be executed instead: Both calls will return an ID of the sync-job which can then be used to monitor job’s progress: |
|
|
| @Stephanie Buck |