Kiwi (R3 2021) Release Notes

The permission "Check Out: View Loans" was introduced in Iris to better control the link on the patron information panel to loan information. The permission was added to support the following behavior:

• if a FOLIO user had "Check Out: All Permissions" but did not have "Check Out: View Loans", they would see the number of open loans, but it would not be a link to view them in Users.

However, this led to undesired behavior:

• if a FOLIO user had "Check Out: All Permissions" and "Check Out: View Loans" but did NOT otherwise have permission to view loans in the Users app, they would see the number of open loans as a link, but clicking on the link would open a blank FOLIO screen.

Before upgrade.

If you assigned "Check Out: All Permissions" to a FOLIO user but do not want them to be able to get a link to see loan information:

• Ensure the FOLIO user does not have "Check Out: View Loans" assigned to them.

If you assigned "Check Out: All Permissions" to a FOLIO User and  you want them to be able to get a link to see loan information:

• Ensure the FOLIO user has "Check Out: View Loans" assigned to them.
• Ensure the FOLIO user also has "Users: User loans view" or "Users: User loans view, edit, renew (all)" assigned to them.

The permission "Check Out: View Requests" was introduced in Iris to better control the link on the patron information panel to loan information. The permission was added to support the following behavior:

• if a FOLIO user had "Check Out: All Permissions" but did not have "Check Out: View Requests", they would see the number of open requests, but it would not be a link to view them in the Requests app.

However, this led to undesired behavior:

• if a FOLIO user had "Check Out: All Permissions" and "Check Out: View Requests" but did NOT otherwise have permission to view the Requests app, they would see the number of open loans as a link, but clicking on the link would open a blank FOLIO screen.

Before upgrade.

If you assigned "Check Out: All Permissions" to a FOLIO user but do not want them to be able to get a link to see request information:

• Ensure the FOLIO user does not have "Requests: View" assigned to them.

If you assigned "Check Out: All Permissions" to a FOLIO User and  you want them to be able to get a link to see request information:

• Ensure the FOLIO user has "Check Out: View Requests" assigned to them.
• Ensure the FOLIO user also has "Requests: View" assigned to them. You could also assign one or more of the following: "Requests: All permissions," "Requests: View, create," or "Requests: View, edit, cancel"

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.

To delete all (!) duplicate barcodes from a test system: 

SET search_path TO diku_mod_inventory_storage;
UPDATE item SET jsonb = jsonb - 'barcode'
WHERE lower(jsonb->>'barcode') in (
  SELECT lower(jsonb->>'barcode')
  FROM item
  GROUP BY 1
  HAVING count(*) > 1);

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

• 019$a and 035$z mapped to Instance Identifier type = Cancelled System Control Number 

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

Note that this change relies on new default Identifier type values available in Kiwi, in Settings/Inventory/Instances:

• Cancelled system control number

See the instructions on how to update the rules

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

• 024/Ind1=1, $aq mapped to Instance Identifier type = UPC
• 024/Ind1=1, $zq mapped to Instance Identifier type = Invalid UPC
• 024/Ind1=2, $aq mapped to Instance Identifier type = ISMN
• 024/Ind1=2, $zq mapped to Instance Identifier type = Invalid ISMN

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

Note that this change relies on new default Identifier type values available in Kiwi, in Settings/Inventory/Instances:

• UPC
• Invalid UPC
• ISMN
• Invalid ISMN

See the instructions on how to update the rules

Starting with Kiwi release Inventory search will be powered by Elasticsearch:

• up to five language specific analyzers can be set up on the tenant level:
• search by all inventory records files

Exact hit count 

After the setup of language analyzers and  search by all fields the re-indexing is required. Also, the re-indexing is recommended after the initial installation or the upgrade to  the Kiwi release. While running re-indexing the recreateIndex property should be set to true For more information regarding the re-indexing please see here.

Through the support of MinIO data export is now hosting agnostic

External storage for generated MARC records should be configured to MinIO server (if needed) by changing ENV variable AWS_URL. In addition, the following ENV variables can be specified: AWS_REGION, AWS_BUCKET, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY.

Viachaslau Khandramai 

Magda Zacharska 

Before upgrade.

Reference data should be added during an upgrade (by default) 

The institutional users that is associated with API key will need to have following permissions:

• "inventory-storage.inventory-hierarchy.updated-instances-ids.collection.get"
• "inventory-storage.inventory-hierarchy.items-and-holdings.collection.post"

Periodically run:

REINDEX index audit_item_pmh_createddate_idx ;
REINDEX
xxxx=> REINDEX index audit_holdings_record_pmh_createddate_idx;
REINDEX
xxxx=> REINDEX index audit_holdings_record_pmh_createddate_idx;
REINDEX
xxxx=> REINDEX index audit_holdings_record_pmh_createddate_idx;
REINDEX
xxxx=> REINDEX index holdings_record_pmh_metadata_updateddate_idx;
REINDEX
xxxx=> REINDEX index item_pmh_metadata_updateddate_idx;
REINDEX
xxxx=> REINDEX index instance_pmh_metadata_updateddate_idx;
REINDEX
xxxx=> analyze instance;
ANALYZE
xxxx=> analyze item;
ANALYZE
xxxx=> analyze holdings_record;
ANALYZE

This will be a training issue for users that create or receive orders. Ideally they are alerted to the change before production is upgraded. However, there are no time-sensitive technical requirements

Note: Users will now be able to add pieces in the receiving app for all orders. However, when synchronized with order quantity. Adding a piece will increase the quantity of the order and in turn the cost and any encumbrances.

mapping_rules db table may contain default (not customised) versions of mapping rules for MARC records alongside the customised mapping rules

MODSOURMAN-744 - Getting issue details... STATUS

circulation-logs.collection.get

Before upgrade:

Do NOT install Okapi >= v4.13.0 (Lotus version).

Install Okapi < v4.13.0 (Kiwi version).