Page Comparison

mod-source-record-manager

Changes to the default MARC Bib-to-Instance map:

1. Added support for the 880 alternate script fields
2. Revised mappings for 541, 542, 561, 583 fields to set the Staff only checkbox based on value in 1st indicator

MODDICORE-114

MODSOURMAN-377

Organisations who need these processes to run will have to schedule them from outside the system

Configuration needed by the hosting provider

• a user that has permissions to invoke these processes
• a scheduled task that logs in as the user and invokes the relevant process

Organisations will likely need to schedule these processes separately meaning two separate tasks and schedules are likely to be needed (separate users may be used for each process)

New External Endpoints

• POST /circulation/scheduled-age-to-lost (permission needed: circulation.scheduled-age-to-lost.post )
• POST /circulation/scheduled-age-to-lost-fee-charging (permission needed: circulation.scheduled-age-to-lost-fee-charging.post )

No body needs to be provided to make requests to either of these endpoints.

Further documentation is available at How to Schedule Age to Lost Processes

manualblocks.collection.get

REINDEX instance_pmh_metadata_updateddate_idx;
REINDEX item_pmh_metadata_updateddate_idx;
REINDEX holdings_record_pmh_metadata_updateddate_idx;
REINDEX audit_instance_pmh_createddate_idx;
REINDEX audit_holdings_record_pmh_createddate_idx;
REINDEX audit_item_pmh_createddate_idx ;

Since 1.3.0 version OKAPI_URL environment variable is required for the module.

On installing/starting the module in the tenant, include

cleanSupplementaryDocs%3Dtrue

in the tenantParameters.

e.g.

/_/proxy/tenants/diku/install?tenantParameters=cleanSupplementaryDocs%3Dtrue

If tenant plans on using Automated Patron Blocks feature AND full event synchronization has not been performed before, follow steps outlined in Q3 2020 (Honeysuckle) Release Notes.

Table snapshots_lib records should only contain status values of 'ERROR' or 'COMMITTED' for jobs which are no longer executing - the following manual script can be run to adjust values:
```
UPDATE <tenant_id>_mod_source_record_storage.snapshots_lb SET status = 'ERROR' where status not in ('COMMITTED', 'ERROR');
```
User story has been added for this cleanup to happen as part of migration to Hotfix 3

This script should NOT be run if DI jobs are currently actively in progress 

Before or After Upgrade

(DI Jobs not running)

DO $$
BEGIN
  RAISE notice 'Script for populating missing Instance HRIDs in SRS started';
  
  UPDATE <tenant>_mod_source_record_storage.records_lb rec
  SET instance_hrid = arr.item_object->>'001'
  FROM <tenant>_mod_source_record_storage.marc_records_lb ind, jsonb_array_elements(content->'fields') with ordinality arr(item_object, position)
  WHERE
    rec.id = ind.id
    and rec.instance_id is not null
    and rec.instance_hrid is null
    and arr.item_object ? '001';

  RAISE notice 'Script for populating missing Instance HRIDs in SRS finished';
END;
$$;

```

UIU-2120

There were two bugs discovered in the Iris BugFest after the test cases had been passed and just before Iris was to be released.  They were caused by changes to the code in BugFest that adversely impacted what had already been tested.   As there are easy workarounds, the two bugs will not be fixed until the Juniper (R2 2021) release.

Bug 1:  When checking in a claimed returned item, the "suspended" lost item fees are not being cancelled (UICHKIN-252)

Bug 2:  When resolving a claimed returned situation, the lost item fees are not cancelled if they have had a transfer made before they were claimed returned (UICIRC-570)

We also have a bug that was found earlier that we were unable to fix for the Iris Release.

Bug 3: For aged to lost items that are claimed returned, and then returned by patron, if the Lost Item Processing Fee is not refunded the Payment Status should be updated to "Outstanding" (UIU-2129)

Bug 1:  The "suspended" Lost Item Fee and Lost Item Processing Fee (if there is one) remain suspended after claimed returned item is check in.  Given they are "suspended", the patron is not being held liable for the fees.  The library is able to waive the "suspended" lost fees to remove them from the "suspended" status.

Bug 2:  The "suspended" Lost Item Processing Fee appears in the Closed Fees/Fines tab, so the patron is not being held liable.  This should not be a problem at all for libraries that don't transfer fees/fines or don't do it quickly.

Bug 3:  This only impacts you if your institution is using aged to lost processing and do not refund the Lost Item Processing Fee if a lost item is returned.   The Lost Item Processing Fee will remain as "Suspended claim returned."  It can be paid with this status, but more likely you will want to waive the original Lost Item Processing Fee and create a new one as a manual charge.

UICHKIN-252

UICIRC-570

UIU-2129

Overdue fines not charged when charging overdue fines by the minute over periods when library is opened then closed

For invoice and invoice-line adjustments, enter them manually after the rest of the invoice has been imported.

For invoice lines that do not match to purchase order lines, 1) delete the invoice line, and add the invoice line manually, based on finding and linking the purchase order line manually. Or 2) review the matchpoints in the invoice data, and manually edit each purchase order lines to include those matchpoints manually, Then delete the imported invoice, and re-import it. This time the incoming invoice-lines should match to the corresponding purchase order lines.

The workaround is not use the Courses: All Permissions set, and instead assigned Courses app users a mix of the segmented permissions that allows them to have desired create/edit functionality:

Courses: Add and edit courses' reserved items
Courses: Add, edit, and remove courses' reserved items
Courses: All permissions
Settings (Courses): Can create, edit and delete course settings

The Courses: All Permissions set is fixed as of the Juniper release, so permissions can be reverted at that point.