Field Mapping Profile details: MARC Bib from MARC Bib 9 - Move-Existing fields

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

As a staff person importing MARC records
I want to specify Move 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 ninth one covers the layout of the Move to Existing field modification on the Create/Edit screen.

NOTE This only allows one subfield to be moved at a time, not multiple subfields.

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 Move modification and New field subaction
   • 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
       • Existing field
       • New field (see UIDATIMP-492)
     • Column 8 (Data): 4 boxes:
       • Box 1 ghost text Field (allows the same characters as column 3/Field)
       • Box 2 ghost text: In. 1 (allows the same characters as column 4/In. 1)
       • Box 3 ghost text: "In. 2" (allows the same characters as column 5/In. 2)
       • Box 4 ghost text: Subf. (allows the same characters as column 6/Subfield)
       • Column 8 has NO free text data box
     • Column 9 (Position): Leave blank
2. Scenario 2
   • Given the above Create/Edit screen
   • When the user selects the Move modification and Existing field subaction
   • And the user enters a Field in column 3, enters values in In 1, In 2 columns 4-5 (*, [blank], alpha, numeric), and enters a Subfield in column 6 (alpha or numeric)
   • And enters a Field in the first box of column 8, and values in In 1, In 2 boxes 2-3 of column 8 (*, [blank], alpha, numeric), and a Subfield in box 4 of column 8 (alpha or numeric)
   • Then consider that a valid Move action
   • And when the action is carried out test import after all the MARC modifications stories are complete
     • Look for any existing field that matches the first box of column 8, with appropriate indicators
       • If not found, then stop - do not make any changes to the record
       • If found, then look for the existing field indicated in column 3, with appropriate indicators
         • If that field, or the indicated subfield in column 6 is not found, then stop - do not make any changes to the record
         • If that field and the indicated subfield in column 6 are found, then
           • Move the contents of that subfield to the field and subfield indicated in column 8. The subfield will always be a new subfield within the existing field specified in column 8
             • If that was the only subfield in the original field (specified in column 3), then remove the original field, its subfield and data.
             • If the original field (specified in column 3) contains other subfields than the specified one, remove the specified subfield and its data from the original field, but retain the field, its indicators, its other subfields, and their data
3. Scenario 3
   • Given the above Move-Existing fields scenario
   • When there are multiple existing fields that match the criteria in columns 3-6
   • And an existing field that matches the criteria in column 8
   • Then add the data from the each field that matches column 3/column 6 as a new, repeated subfield to the existing field that matches the criteria in column 8 test import after all the MARC modifications stories are complete
4. Scenario 4
   • Given the above Move-Existing fields scenario
   • When there are multiple existing fields that match the criteria in column 8
   • Then add the data from the field in column 3 and the subfield in column 6 to every existing field that matches the criteria in column 8 test import after all the MARC modifications stories are complete
5. Scenario 5
   • Given the above Create/Edit screen
   • When the user selects the Move modification and Existing field subaction
   • Then the following data combinations should NOT be considered valid
   • And the appropriate boxes should be outlined in red
   • And do not allow the field mapping profile to be saved until the errors have been corrected or the row has been deleted.
     • No field indicated in column 3
     • Values other than *, [blank], alpha, numeric in Indicator columns 4-5
     • Values other than alpha, numeric in Subfield column 6
     • The same field in column 3 and the first box of column 8
     • No field indicated in the first box of column 8
     • Values other than *, [blank], alpha, numeric in the 2nd-3rd Indicator boxes in column 8
     • Values other than alpha, numeric in the 4th Subfield box in column 8
     • Subaction not selected in column 7
6. Scenario 6
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

Note on field placement: If any existing fields are retained, leave them in the same place in the MARC record as they were originally

See attached mockups, examples, and logic details