Evergreen

batch volume transfers need to take acq into account

Bug #1691784 reported by Chris Sharp
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Medium
Unassigned

Bug Description

EDIT: this bug originally assumed the problem was with bib merges, not volume transfers

We have discovered that Evergreen's batch volume transfer process does not account for acquisitions lineitems linked to the empty-of-volumes (now deleted) record. Here is the acq workflow:

1) User uploads a file of MARC records via the Load MARC Order Records UI.

2) User attaches acq copies to those lineitems.

3) User activates order and is greeted with "[JavaScript Application] Event: 1228:BIB_RECORD_DELETED -> The requested bib record is marked as deleted"

Investigation revealed that between steps 1 and 3, a cataloger at another library batch transferred volumes from the linked record for the affected lineitem into another record. Evergreen should include a check for these and update them to the transfer destination record along with the "delete the now empty bib" step.

Evergreen 2.11.1
OpenSRF 2.4.1
Ubuntu 14.04 LTS
PostgreSQL 9.4

See original description
Tags: acq
Chris Sharp (chrissharp123)
Changed in evergreen:
importance: Undecided → Medium
Revision history for this message
Bill Erickson (berick) wrote :

This sounds a lot like bug #849143.

Revision history for this message
Chris Sharp (chrissharp123) wrote :

Bill,

I misread the logs - it turns out to be volume transfers from one bib to another (which deletes the bib if left empty by the transfer) that caused the problem here. Thanks for the link to the older bug which let me know that my original premise was incorrect!

Chris

summary: - bib record merges need to take acq into account
+ batch volume transfers need to take acq into account
description: updated
Kathy Lussier (klussier)
Changed in evergreen:
status: New → Confirmed
Revision history for this message
Kathy Lussier (klussier) wrote :

"Evergreen should include a check for these and update them to the transfer destination record along with the "delete the now empty bib" step."

I just want to clarify the desired process in cases where the volume transfer does not result in an empty bib that gets deleted.

If a volume is transferred to another record with copies that started in acq, the link to the lineitem / PO (I'm not quite sure where these link in the database) should also be updated even if that source bib record is not deleted. The initial copy may have been attached to the wrong record, causing the cataloger to transfer it to the correct one. That acq information should go along with the copy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.