For MARC21 validation support validation error messages should be displayed inline for each field, instead of current pattern with toast notifications.

To kick off UI work related to MARC validation without waiting for BE implementation to be completed, we can implement inline error messaging for current validation approach, which could then be integrated with new BE validation.

Assumption: even though MARC Holdings validation approach will stay the same after (meaning MARC Holdings records will be validated on UI) - we will show validation error messages inline, however there will be no warn messages, or help icons.

Requirement 1: Hit any Save button (or use the Save shortcut key) Then run MARC validation rules

• IF there are no MARC validation rules errors THEN proceed with saving record. Same as current behavior and workflow.

• IF there is a MARC validation rule error(s) THEN display error(s) inline AND shift focus to first field with error.

• IF there are validation errors and the user doesn’t fix any of them THEN they can click any Save button again AND will continue to see the same error messages

Requirement 2: Display MARC rule validation error inline

• See mockup 2 (DO NOT implement the inline error messages as shown on the mockup. Please implement the messages that are noted in this requirement.)

• Inline error message format: Show error icon (red exclamation mark) <<Error type Fail/Warn>> : Error message

• Per field, multiple error messages may display inline

• DO NOT show Field Help icon (for Bibs and Authorities this information will come from BE validation and will not be available for Holdings)

• Show Field Help icon is a separate requirement for MARC Bib and MARC Authority records, as we may implement later based on release scope

• IF a field does not display and it is required then display as a toast notification: Show error icon (red exclamation mark) Fail : Record cannot be saved without field <<field number>>.

Requirement 3: No change to authority linking messaging display (including messaging to handle race conditions)

Requirement 4: No change to validation rules