error handling when attempting to save MARC record with invalid tag could be friendlier

Bug #1402820 reported by Galen Charlton
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Wishlist
Unassigned

Bug Description

When attempting to save a bib record that contains an invalid tag number (e.g., "65="), the Evergreen staff client displays an error message like this:

Error creating MARC record.

DATABASE_QUERY_FAILED
The attempt to query to the DB failed

The error originates from a data validity check in MARC::Record as invoked by one of the database triggers invoked when a row is inserted into biblio.record_entry. The check itself is fine, but the way that the error is presented to the user is less than ideal:

- the MARC editor doesn't highlight the offending tag number
- the error message doesn't make it clear that the problem has to do with the user input

Potential ways to improve this:

- do a bit more client-side validation
- pass a bit more information up the line

Evergreen master

Revision history for this message
Andrea Neiman (aneiman) wrote :

Still an issue in the webclient, only the error is simply "Could not save the record!" which, while marginally more friendly than DATABASE_QUERY_FAILED, is not as nice as Galen's suggested approaches.

Changed in evergreen:
status: New → Confirmed
tags: added: usability wishlist
removed: ux
tags: added: webstaffclient
tags: removed: webstaffclient wishlist
Gina Monti (gmonti90)
tags: added: error-handling
tags: added: ux-error-messages
tags: added: ux-form-validation
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.