Data Import setting for MARC field protection - part 2: Add rows

Purpose: To allow the tenant to add other protected fields to the Data Import MARC field protection settings

As a staff person importing MARC records
I want a way to protect library-specific MARC fields from updating
So that I can make sure that important information is not accidentally deleted from existing SRS records during updates

NOTE See Settings/Orders/Closing purchase order reasons for an example of the structure/UI we want to create

Scenarios

1. Scenario 1
   • Given Settings/Data import/MARC field protection
   • When a user clicks the New button
   • Then add a blank row at the top of the list of fields, with the following default information
     • Field = [blank]
     • Ind 1 = *
     • Ind 2 = *
     • Subfield = *
     • Data = *
     • Source = User
     • Actions = Buttons for Save (greyed out) and Cancel (active)
   • See attached Field protection 2.PNG
2. Scenario 2
   • Given a newly-added row in the MARC field protection settings
   • When a user begins to enter or change information in the new row
   • Then activate the Save button at the end of the row
   • And validate the data in the fields as follows:
     • Field = must be * or 3-digit numeric between 010 and 999; cannot be blank; if * then subfield must have alpha or numeric
       • Otherwise red error message: Please enter * or numeric value
     • Ind 1 = must be [blank] or single character (*, alpha, or numeric)
       • Otherwise red error message: Please enter * or alphanumeric value
     • Ind 2 = must be [blank] or single character (*, alpha, or numeric)
       • Otherwise red error message: Please enter * or alphanumeric value
     • Subfield = must be single character (*, alpha, or numeric); cannot be blank
       • Otherwise red error message: Please enter * or alphanumeric value
     • Data = must be * or any text; cannot be blank
       • Otherwise red error message: Please enter * or other data
     • Source = [no validation]
     • Actions = [no validation]
   • See attached Field protection 3.PNG
3. Scenario 3
   • Given a newly-added row in the MARC field protection settings
   • When a user has finished entering or changing information in the new row
   • And presses the Save button at the end of the row
   • Then
     • Ensure the data in the row matches the validation in Scenario 2
     • And disallow the save and highlight the invalid fields in red until they have been corrected
     • And if Ind 1 and/or Ind 2 = [bank], display in the UI as [blank], not hyphen
     • And change the Source field from [blank] to User
     • And change the row to non-editable
     • And put it into numeric order in the MCL with any other existing fields in the screen
     • And if the Field data = *, put those rows at the top of the MCL
     • And change the Action icons to Edit pencil and Trash can
   • See attached Field protection 4.PNG
4. Scenario 4
   • Given a newly-added row in the MARC field protection settings, before a User presses Save
   • When a user presses Cancel
   • Then delete the row, without any confirmation modal
5. Scenario 5
   • Ensure this story passes Accessibility testing
6. Scenario 6
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

abreaux When testing this story, also test the validation from UIDATIMP-594