FIXME error blocks first attempt at saving a bib record with a newly added 006/007 field
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Undecided
|
Unassigned | ||
2.3 |
Fix Released
|
Undecided
|
Unassigned | ||
2.4 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Evergreen 2.3.x
OpenSRF 2.1.2
PostgreSQL 9.1
Ubuntu 12.04
After using "Add/Replace 006" or "Add/Replace 007" and filling in the 006 or 007 field, a user clicks on "Save Record." A FIXME error appears saying the "record not likely updated. DATABASE_
The user clicks the "Check here to confirm this message" box and "Okay." The user then has to go correct the MARC tag which has been replaced with "undefined"-usually one of the first fully editable MARC fields (i.e. 010 or later). Once corrected, then the user can "Save Record."
Ideally, the user should be able to "Add/Replace 006" or "Add/Replace 007" without having to correct another field because it's tag is replaced with "undefined."
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
Fix in http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ paxed/lp1187402