Field Mapping Profile details: MARC Bib from MARC Bib 5 - Edit-Remove

Purpose: To specify the Edit action's Remove subaction details in the MARC record modifications field mapping profile

As a staff person importing MARC records
I want to specify Edit modifications to those incoming records
So that I can save the MARC records with appropriate adjustments

"MODIFY" is a special action in Data Import that only applies to MARC records. MODIFY action profiles can be at the beginning, middle, and/or end of a job profile tree. For example, as a first action, a library might want to add a proxy to the URLs in MARC 856 fields in an incoming file, then create instances and other records, and then as a last action, remove certain 9xx fields from the MARC records before saving the final versions of the MARC records in SRS.

The structure of the MARC Modification field mapping profiles (a special type of field mapping profile) will be laid out in a sequence of user stories, all covered under Feature UXPROD-2286. Details for the entire screen are covered in https://drive.google.com/open?id=1_WJ_RNhxnkHcIK_zvXxNKVW4qRwjG0kXaagA519S46w

This fifth one covers the layout and logic of the Remove subaction of the Edit modification on the Create/Edit screen.

Scenarios

1. Scenario 1
   • Given the Settings/Data Import/Field mapping profile Create/Edit screen
   • When the Incoming record type = MARC Bibliographic and the FOLIO record type = MARC Bibliographic
   • And the user selects the Edit modification
   • Then adjust the MCL row's details like this: (see attached mockup)
     • Columns 1-3 = same
     • Columns 4-6 = insert an asterisk as default (In 1, In 2, Subfield)
     • Column 7 (Subaction): Dropdown list with
       • Ghost text: Select
       • Insert
       • Remove
       • Replace
     • Columns 8 and 9 will adjust depending on which subaction is chose
       • For subaction Remove, see Scenario 2 in this story
       • For subaction Replace, see UIDATIMP-490
       • For subaction Insert, see UIDATIMP-491
2. Scenario 2
   • Given the Settings/Data Import/Field mapping profile Create/Edit screen
   • When the Incoming record type = MARC Bibliographic and the FOLIO record type = MARC Bibliographic
   • And the user selects the Edit modification and Remove subaction
   • Then adjust the MCL row's details like this: (see attached mockup)
     • Column 8 (Data): Free text data field; allow it to wrap in the text box if necessary, so that the user can view the entire text in the Create/Edit screen
     • Column 9 (Position): Leave blank
3. Scenario 3
   • Given the above Create/Edit screen
   • When the user selects the Edit modification and Remove subaction
   • And the user enters a Field in column 3 and a Data string in column 8, and leaves asterisks in columns 4-6 (In 1, In 2, Subfield)
   • Then consider that a valid Edit action
   • And when the action is carried out, inspect any occurrences of that field in any record in the incoming file, regardless of indicators or subfields, and remove that data string from whichever subfield(s) it is in. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the remaining field. test import after all the MARC modifications stories are complete
   • NOTE If an entire field or subfield is to be removed, then use the Delete action rather than the Edit-Remove action
4. Scenario 4
   • Given the above Create/Edit screen
   • When the user selects the Edit modification and Remove subaction
   • And the user enters a Field in column 3, Indicator(s) in column 4 and/or 5 ([blank], alpha, or numeric) and a Data string in column 8, but leaves an asterisk for Subfield in column 6
   • Then consider that a valid Edit action
   • And when the action is carried out, inspect any occurrences of that field in any record in the incoming file, but only if the field's indicators match the ones in the modification action, and remove that data string from whichever subfield(s) it is in. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the remaining field. test import after all the MARC modifications stories are complete
   • NOTE If an entire field or subfield is to be removed, then use the Delete action rather than the Edit-Remove action
5. Scenario 5
   • Given the above Create/Edit screen
   • When the user selects the Edit modification and Remove subaction
   • And the user enters a Field in column 3, a Subfield in column 6, and a Data string in column 8, but leaves asterisks for both Indicators in columns 4 or 5
   • Then consider that a valid Edit action
   • And when the action is carried out, inspect any occurrences of that specific subfield in that specific field (regardless of the field's indicators) in any record in the incoming file, and remove that data string from the specified subfield. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the remaining field. test import after all the MARC modifications stories are complete
6. Scenario 6
   • Given the above Create/Edit screen
   • When the user selects the Edit modification and Remove subaction
   • And the user enters a Field in column 3, Indicators in columns 4 and/or 5 ([blank], alpha, or numeric), a Subfield in column 6 (alpha or numeric), and a Data string in column 8
   • Then consider that a valid Edit action
   • And when the action is carried out, inspect any occurrences of that specific subfield in that specific field in any record in the incoming file, but only if the field's indicators match the specified ones, and then remove that data string from the specified subfield. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the remaining field. test import after all the MARC modifications stories are complete
7. Scenario 7
   • Given the above Create/Edit screen
   • When the user selects the Edit modification and Remove subaction
   • And the user does not enter a Field in column 3 (leaves it blank)
   • Then DO NOT consider that a valid Edit-Remove action, regardless of any other data in that row
   • And highlight the Field box in red
   • And do not allow the field mapping profile to be saved until the Field box has been filled in or the row has been deleted.
8. Scenario 8
   • Given the above Create/Edit screen
   • When the user selects the Edit modification and Remove subaction
   • And the user does not enter an asterisk, alpha or numeric in Subfield column 6
   • Then DO NOT consider that a valid Edit-Remove action, regardless of any other data in that row
   • And highlight the Subfield box in red
   • And do not allow the field mapping profile to be saved until the Subfield box has been filled in or the row has been deleted.
9. Scenario 9
   • Given the above Create/Edit screen
   • When the user selects the Edit modification and Remove subaction
   • And the user does not enter a Data string in Column 8
   • Then DO NOT consider that a valid Edit-Remove action, regardless of any other data in that row
   • And highlight the Data box in red
   • And do not allow the field mapping profile to be saved until the Data box has been filled in or the row has been deleted.
10. Scenario 10
    • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

See attached mockups, examples, and logic details