Records with no 901 values

Asked by George Duimovich on 2011-06-17

EG 2.0.6
PG 8.4

Probably a local data issue, but if so not sure how common this might be for other 1.6->2.0 upgrades.

I came across a record without an 901 system generated tag so we looked at how many others were in the system since the 2.0.6 upgrade. We found about 11,000 such records (or about 2% of our bibs):

select id from biblio.record_entry
where id not in (select distinct(record) from metabib.real_full_rec where tag = '901' and subfield = 'c')

Looking at a bunch of these records we can see one common thread is that they have empty 001 tags (no indicators / subfields). A snippet from the Flat Text Editor view of such a record looks like this:

=LDR 00881nam a22001937a 4500
=001
=005 20100520153539.0

If I view and then save the record in the Staff Client, the 001 and 901 values are populated.

Unless otherwise advised, I'll just proceed with re-ingesting them the 2.0 way: http://goo.gl/xFSRm

Question information

Language:
English Edit question
Status:
Answered
For:
Evergreen Edit question
Assignee:
No assignee Edit question
Last query:
2011-06-17
Last reply:
2013-05-19

This question was originally filed as bug #798702.

Dan Scott (denials) said : #1

And commit 77ac8a925ba5

Ben Shum (bshum) said : #2

Note, this was resolved during the 2.2-2.3 upgrade scripts and involves reingesting the bib records after upgrading to newer versions of Evergreen.

Can you help with this problem?

Provide an answer of your own, or ask George Duimovich for more information if necessary.

To post a message you must log in.