ACQ - Load MARC Order Records throws BIBLIO_RECORD_ENTRY_NOT_FOUND

Bug #1709148 reported by Patrick Gardella
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Incomplete
Undecided
Unassigned

Bug Description

Evergreen: 2.12.0
OpenSRF: 2.5.0
PostgreSQL: 9.1.23
Linux: Ubuntu 12.04.5

Steps to recreate:
* Create a MARC file using WorldCat
* Execute Load MARC Order Records
* Change the queue
* Click upload - Wait for error

What happened:
When we use Load MARC Order Records, we get a "Event: 1501:BIBLIO_RECORD_ENTRY_NOT_FOUND" error in the staff client. This happens *every time* we try to import a file and there is already a MARC record in the system that needs to be overlaid. The vast majority of the time the existing bib record also has existing copy records. In fact I don't think there has ever been an exception.

After filling out the correct text fields, the file Upload button is pressed to initiate the import. A progress bar appears, and then the error message window appears.

What should happen:
The list should import and the PO should be created.

Comments:

I see that this error is thrown in two files:
/OpenILS/Application/AppUtils.pm
/OpenILS/Application/Search/Biblio.pm

Calling the same code that I see in each, except via srfsh, I get resulting data back.

AppUtils:
request open-ils.cstore open-ils.cstore.direct.asset.copy.retrieve 524727 {"flesh": 3, "flesh_fields": { "bre": ["fixed_fields"], "acn": ["record"], "acp": ["call_number"]}}

Biblio:
request open-ils.cstore open-ils.cstore.direct.biblio.record_entry.search { "id" : "524727" }

Nor do I see any errors or warnings in the logs during the time of this load.

Revision history for this message
Patrick Gardella (patrick-gardella) wrote :
tags: added: acq
Revision history for this message
Tiffany Little (tslittle) wrote :

Patrick, when you're doing your upload, are you using any values in the Record Match Set or Merge Profile fields?

tags: added: acq-loadmarc
Changed in evergreen:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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