MARC Editor Leader field allows removing, replacing, but not adding characters

Bug #1769363 reported by Jane Sandberg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

On 3.1, using the Web client

If you want to change a character in the LDR field, you can't just delete it and add a different character in its place. You have to select it and type over it instead (or go to the flat text editor).

This is a little tricky in cases in which the fixed fields aren't displaying because LDR/06 (Type) is invalid.

I'm not sure what the desired behavior is here. It does seem sensible to protect this field against invalid values, but I don't know what the best way to distinguish between valid and invalid edits would be.

Tags: cataloging
Revision history for this message
Eva Cerninakova (ece) wrote :

I am not sure if my observation refers to the exact same problem:
We were unable to add value to fixed field in some incorrect bib records, that did not have had created corresponding field before. E.g., we were not able to save the country code to field 008 using the grid or MARC text editor - the value always disappeared after saving. However, if the field had been created using right click option "Add 008" and then the value was added, the value was saved.
The behavior was the same in the web client of 3.1.4 and 3.3.0.

Revision history for this message
Jason Boyer (jboyer) wrote :

Eva, your situation is different, if there's not already an 008 in the record editing the fixed field grid at the top of the record doesn't cause one to be inserted, so that's why the values you enter are just lost. If you add an 008 (even if it's entirely empty) then editing the grids at the top will work as expected. Making the fixed field editor smart enough to insert a new 008 if there isn't one present would be a good bug if one hasn't already been entered.

This bug is specifically about the LDR line manually (which is affected by editing some of the FF grid, but not most of it) and I've checked on our local install and can repeat the problem so I'm marking this bug confirmed.

Changed in evergreen:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.