Vandelay matches and merges to deleted bibliographic records
Bug #1817739 reported by
Rebecca Miller
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Evergreen |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
During MARC batch import, matches are being made to deleted records in the catalog. Items in the queue are not imported. No import error is produced.
I would expect that Vandelay either ignores deleted records or asks to reactivate them.
Inspect Queue screenshot attached.
Evergreen version: 3.2
OSRF version: 3.0.?
PostgreSQL: 9.5.14
Linux: Lubuntu 16.04.5
Revision history for this message
| Rebecca Miller (ocsmiller) wrote | #1 |
Revision history for this message
| Tiffany Little (tslittle) wrote | #2 |
| Changed in evergreen: | |
| status: | New → Confirmed |
Revision history for this message
| Robert J Jackson (rjackson-deactivatedaccount) wrote | #3 |
| tags: |
added: cat-importexport silentfailure removed: vandelay |
To post a comment you must log in.
I tested this on our 3.2.4 system and can confirm.
How I tested:
1. I uploaded a file with 2 bibs.
2. Once uploaded, I deleted the matched BibA.
3. I searched by TCN to confirm that the bib was really deleted.
4. I uploaded the same file.
5. BibA is now revived and is not deleted.
Interestingly, because I am normally an Acq person, I tried this same process using Load MARC Order Records and it did *not* match to deleted records. Instead it created a new autogenerated record; it did not revive the deleted bib. I have no idea where the split between MARC batch import and LMOR happens, but figured I'd add my observation for additional info.