Validation for MARC Field mapping syntax for Instance, Holdings, Item profiles

Purpose: To ensure that field mapping syntax is validated when entered into the field mapping profile details, by creating form client validation rules and procedures (applies to UIDATIMP-15, UIDATIMP-290, and UIDATIMP-292, so far)

As a staff person
I want to know that the MARC field mapping details I enter are formatted correctly
So that the import errors are minimized

Scenarios

1. Scenario 1
   • Given the field mapping profile details section when the incoming record type = MARC of any kind
   • When a User enters MARC fields/subfields or default values in the mapping fields of the profile
   • And presses Save
   • Then validate that the syntax has been entered correctly
2. Scenario 2 good that it checks capitalization too
   • Given the field mapping profile details section when the incoming record type = MARC of any kind
   • When a User enters default values in the mapping fields of the profile
   • And the field has a dropdown list of reference values associated with it
   • And presses Save
   • Then validate that the entered default value is one of the values from the dropdown list, enclosed in quotation marks
3. Scenario 3
   • Given the field mapping profile details
   • When the user presses Save, and the MARC field mapping syntax and defaults are valid
   • Then allow the field mapping profile to be saved
4. Scenario 4
   • Given the field mapping profile details
   • When the user presses Save, and the MARC field mapping syntax and defaults are not valid
   • Then do not allow the field mapping profile to be saved
   • And display all errored fields in the red error state with this error message below the field: Please correct the syntax to continue
   • And position the cursor at the top-most field that has a validation error
5. Scenario 4
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

See attached wireframe

Review with OleksiiKuzminov if questions about any syntax scenario details

Syntax available on Syntax tab of https://docs.google.com/spreadsheets/d/17kCccovBR-RAVK-coW7fpXvJfaRmYA2mUHoVLSF9Spo/edit#gid=141717922

Other syntax notes: