maintain_control_numbers() can GIGO identifiers all the way into the bit bucket

Bug #1517120 reported by Galen Charlton on 2015-11-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The maintain_control_numbers() stored procedure, when presented with an incoming MARC record that has multiple 001 fields, will fail to copy any of the identifiers into 035 fields. For example, consider the following record:

001 ocm12345678
001 ocm12345678
003 OCoLC

The end result would be

003 $OU
... and no 035.

While this is an example of GIGO -- the 001 field is not repeatable -- simply dropping existing identifiers is not an optimal result. Better would be to either not change the record at all or to just willy-nilly copy the old 001s/003s into 035 fields, even when there are more than one 001 field.

Evergreen master

Erica Rohlfs (erohlfs) on 2015-11-17
Changed in evergreen:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers