We have discovered that Evergreen's bib merge process does not account for acquisitions lineitems linked to the merged (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 merged the linked record for the affected lineitem into another record. Evergreen should include a check for these and update them to the "master" record along with everything else that happens during a bib merge.
We have discovered that Evergreen's bib merge process does not account for acquisitions lineitems linked to the merged (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 merged the linked record for the affected lineitem into another record. Evergreen should include a check for these and update them to the "master" record along with everything else that happens during a bib merge.
Evergreen 2.11.1
OpenSRF 2.4.1
Ubuntu 14.04 LTS
PostgreSQL 9.4