Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Functional AreaChange or AdditionConsiderationsAction requiredAction timingContact personCommentsRelated JIRA issues
Affected app or moduleWhat has been changed or added that should be noted for this releaseWhat challenges may arise related to this change or additionIf applicable, detail what action(s) must be taken hereWhen can the action be taken (before, during or after upgrade)User name of person that can provide additional detailName of user leaving comment: comment on what you encountered or ask a question @mention Contact personInclude issue link for bug fix, story or feature that applies
mod-source-record-managerCorrected the default MARC-to-Instance mapping for the 647 fieldIndividual tenants often adjust the default MARC-to-Instance map to include or exclude particular MARC fieldsReview each  tenant's production MARC-to-Instance default mappings, and adjust the 647 field: https://github.com/folio-org/mod-source-record-manager/blob/master/mod-source-record-manager-server/src/main/resources/rules/marc_bib_rules.json#L5648After upgradeAnn-Marie Breaux
MODSOURMAN-448
mod-source-record-managerIncreased the default limit for the number of reference values that can be looked up from 500 to 1000, and added a way to change the configuration in case a higher limit is needed. If a tenant has more than 500 values for particular settings (e.g. locations, funds), Data Import previously could only retrieve the first 500. That caused incorrect location assignments for libraries with 500+ locations. The default has been changed to 1,000, and a new variable created to allow for higher settings.

This limit is for data from this class (see constants from this class): https://github.com/folio-org/mod-source-record-manager/blob/86835f64a1f5e29e3350899b04807941327d54ec/mod-source-record-manager-server/src/main/java/org/folio/services/mappers/processor/MappingParametersProvider.java#L91 

As of v 3.1.3 there is a new property which defines the limit for retrieving data to fill mapping parameters for the data-import mechanism: "srm.mapping.parameters.settings.limit:1000" (default=1000).

This setting controls the number of items that will be retrieved from specific endpoints for Data-Import matching and field mappings. If a higher limit is needed by a particular tenant, the setting can be adjusted.

See more info in the README.md-file in mod-source-record-manager: mod-source-record-manager/README.md at master · folio-org/mod-source-record-manager (github.com)"

After upgrade

MODSOURMAN-535

MODDICORE-165

mod-source-record-storageIn Iris, an end point was added to allow searching MARC records. If the script to add records to the search was not run on your tenant for Iris, then it will be need to run for Juniper if you wish to use the search.The end point will only return results from MARC records added after installation of Iris. A script to retroactively process pre-existing records has  been developed, see MODSOURCE-276: Add existing records to the SRS Query API tableTo add records  that existed prior to  upgrade to the query search  see MODSOURCE-276: Add existing records to the SRS Query API table Script: https://github.com/folio-org/mod-source-record-storage/blob/master/mod-source-record-storage-server/src/main/resources/migration_scripts/fill_marc_indexers.sqlBefore or after upgrade, if never run before or if you have records that need to be added to the query search.

mod-service-interaction

To ensure that the widget definitions made available by mod-agreements and mod-licenses are available, mod-service-interaction should be initialised with the tenantParameter `loadSample%3Dtrue` specified.

On initialising the module for the first time

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-1778

mod-feesfinesUpon deployment make sure that automatic fee/fine types were added to the mod-feesfines database.  Otherwise automatic fine creation functionality will not work.To check, make a call to /feefines?query=automatic==true.  The response should contain 4 entries: "Overdue fine", "Lost item fee", Lost item processing fee" and "Replacement processing fee."

To check, make a GET call to /feefines?query=automatic==true.  The response should contain 4 entries: "Overdue fine", "Lost item fee", Lost item processing fee" and "Replacement processing fee." If response is empty, execute the following script manually and check again:

https://github.com/folio-org/mod-feesfines/blob/v16.1.1/src/main/resources/templates/db_scripts/populate-feefines.sql





mod-circulationAll Service Points must be associated with a Fee/Fine Owner at Settings>Users>Fee/Fine: Owners for overdue fines and lost item fees to work properly.  If an overdue fine/lost item fee is calculated for an item with a Location whose Primary Service Point is not associated to a Fee/Fine Owner, the overdue fine/lost item fee will NOT be charged to the patron.In the future we will have a Default Fee/fine Owner to be charged.  (See UXPROD-2278 for details.)




mod-searchNeed to add a new environment variableModule can read Kafka messages from other envs

New environment variables should be added for mod-search.

ENV - The logical name of the deployment, must be unique across all environments using the same shared Kafka/Elasticsearch clusters. See details.

KAFKA_EVENTS_CONSUMER_PATTERN - regexp pattern for Kafka consumers to subscribe. 

Value for this property should be ({ENV}\.)(.*\.)inventory\.(instance|holdings-record|item)

Important! {ENV} should be replaced with the same value as the value for the ENV property. 

Example:

ENV: bugfest

KAFKA_EVENTS_CONSUMER_PATTERN: (bugfest\.)(.*\.)inventory\.(instance|holdings-record|item)




mod-source-record-storage“2020-09-09--15-00-fill-instance-hrid” migration script will no longer fail the upgrade in case MARC records with multiple "001" fields present in the DB.MARC records with multiple "001" fields might fail to update via data-import process or by quick-marc edit.

Run check_001_field_duplicates.sql script to find MARC records with multiple "001" fields, review and correct the data.

Before upgrade (or on a periodic basis in case data are imported to SRS bypassing data-import)

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyMODSOURCE-359

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyMODSOURCE-357

InventoryItem barcode is unique
We removed the item barcode changes from Juniper. They will ship with Kiwi.
Duplicate item barcodes fail the upgrade.
Upgrade error response mentions index name item_barcode_idx_unique.
mod-inventory-storage log mentions actual duplicate barcode.

Before upgrade:
Change all duplicate item barcodes.
Find them with this SQL:
SET search_path TO diku_mod_inventory_storage;
SELECT lower(jsonb->>'barcode')

FROM item
GROUP BY 1
HAVING count(*) > 1;

Use Inventory Item Barcode search to edit the duplicate barcode.

Before upgrade

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyMODINVSTOR-523

InventoryManual publicationPeriod migrationWhen migrating from Iris to Juniper HotFix#3 or later there is no automatic population of publicationPeriod. When migrating to Juniper GA, HotFix#1 or HotFix#2 publicationPeriod is automatically populated during migration.Manually populate publicationPeriod. Details: https://github.com/folio-org/mod-inventory-storage/blob/master/src/main/resources/templates/db_scripts/populatePublicationPeriod.sqlBefore or after upgrade

(MODINVSTOR-774, MODINVSTOR-806, MODINVSTOR-811, MODINVSTOR-812)

DashboardPopulate widget definitions

To ensure that dashboard has all the available dashboard widget definitions:

  • Assign a user the permission `servint.admin.action`
  • With that user, issue a GET to Okapi endpoint /servint/admin/triggerTypeImport - this will import all available widget definitions from modules that supply them
After upgrade 

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyERM-1778

StripesNodejs LTS version changed from 14 to 16yarn install fails when using Node 16: "gyp ERR! not ok"Pin the version of n to 14Before upgrade

Jira
serverFOLIO Issue Tracker
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyFOLIO-3323

Loan AnonymizationChanges to ensure that loan anonymization processes all open loans. 

Prior to Juniper bugfix the anonymization process only fetched 5,000 loans at a time, so if you had more than 5,000 loans that needed to be processed for anonymizing, it wouldn't get entirely through the process, introducing inconsistencies. 

A new approach was implemented:

  • increase number of checked loans to 50,000
  • increase interval between runs to 1 hour
  • increase guideline mem requirements for module

If the new approach is acceptable, no changes are needed.

If you want to increase or decrease the number of checked loans at a time, you can do it through an environment variable

If you want to increase or decrease the interval between runs, you can override that in Okapi

Note that the anonymization process needs to finish one run before beginning the next run in order to minimize inconsistent behavior. That should be factored into your considerations if you want to change the number of loans and interval. There is significant discussion of the ramifications in the comments of

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyCIRC-1178

After upgrade
SME questions about this are best directed to the #resource-access channel on Slack

Jira
serverFOLIO Issue Tracker
serverId6ccf3fe4-3301-368a-983e-20c466b11a49
keyCIRC-1178

mod-data-importSet the chunk size valuemod-source-record-storage might crash with OOM during the Update import of 5,000 records if chunk size parameter is left with default value of 50 recordsfile.processing.buffer.chunk.size system property should be set to 5

...