expand_doc_bib_001 vs. fix_doc_001

Description

How does expand_doc_bib_001 differ from fix_doc_001 as far as adding the 001 field to a record being exported (for instance, by the print-03 Service)?
 

Resolution

expand_doc_bib_001 adds an 001 field to the record only if it doesn't already have an 001 field.  An existing 001 field *should* be the Aleph system number, but there have been cases where records had been imported and the 001 field from the incoming record was left as an 001 field (rather than being moved to some other field, such as an 035).  Thus, the exported record had that number rather than the Aleph system number.

In contrast, the default is for fix_doc_001 to overwrite any existing 001 field (with the Aleph system number).  The only case in which it doesn't do this is when "NO-OVERWRITE" (or "OVERWRITE-NON-NUMERIC") is specified in calling fix_doc.  The default is to overwrite. 

• Article last edited: 16-Aug-2016