Missing migration script to populate Effective location for holdings without items

Description

Overview:
The effective location on the holdings record is not populated for holdings without items. This bug seems to affect only libraries that went live before Juniper release (R2 2021) when the effective location property was added to the holdings record ().

If the holdings record was updated through UI or API call the effective location is populated but if the record has not been touched since Juniper release, the effective location is missing.

Holdings effective location is being used by OAI-PMH for harvesting location in case items records are not present.

Interested parties:
Chalmers and other libraries that went live before Juniper release.

Possible work around:
Edit each holdings record via UI or API call.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Kyle Felker September 6, 2022 at 1:18 PM

The reference script, noted above, it basically a copy of the script that does this within the module. Looking at that should tell you how the effectiveLocationId is calculated.

Aanand Srivastav September 6, 2022 at 10:40 AM


Could you please let us know how can we found the value of effectivelocationId. If we update the effectivelocationId value with some existing value then it will be same for each holding records.
cc:  

Kyle Felker August 11, 2022 at 6:19 PM

Bug fix release for this is being released as we speak. There is also an operator script on the wiki under inventory->inventory scripts

Magda Zacharska August 4, 2022 at 12:07 PM

I don't think we need bug fix releases for older flowers but having bug fix release for MG and script that system operators can run would be great (in that order).

Marc Johnson August 4, 2022 at 8:16 AM

Thank you for reporting this.

I've done some brief investigation and I think I know the cause of this (an incorrect version in the database upgrade script configuration). I've asked for follow up on interpretation of this for confirmation.

We have options in terms of resolution:

  • Bug fix release for Morning Glory which runs the same script

  • Script that system operators run to do the same

  • Bug fix release for older flower releases

It might be that we need a combination of these. What are your thoughts on what is needed?

cc:

Done

Details

Assignee

Reporter

Labels

Priority

Sprint

Development Team

Prokopovych

Fix versions

Release

Morning Glory (R2 2022) Bug Fix

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created August 3, 2022 at 2:39 PM
Updated September 6, 2022 at 1:18 PM
Resolved August 11, 2022 at 6:19 PM
TestRail: Cases
TestRail: Runs
Loading...