Records with no 901 values
This bug report was converted into a question: question #229221: Records with no 901 values.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Invalid
|
Medium
|
Unassigned |
Bug Description
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.
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://
Changed in evergreen: | |
status: | New → Incomplete |
status: | Incomplete → Confirmed |
importance: | Undecided → Medium |
Changed in evergreen: | |
status: | Confirmed → Invalid |
I believe we encountered this as well, and unintentionally created a (semi-?)duplicate bug. See bug 927900 for more details.