Field Mapping Profile details: MARC Bib from MARC Bib 1 - Basic layout

Purpose: To create the initial framework of the details section for the MARC record modifications field mapping profile

As a staff person importing MARC records
I want to specify 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 first one covers the basic layout of the Create/Edit screen.

Scenarios

1. Scenario 1
   • Given the Settings/Data Import/Field mapping profile
   • When the Incoming record type = MARC Bibliographic and the FOLIO record type = MARC Bibliographic
   • Then lay out the details section of the Create/Edit screen like this: (see attached wireframe)
     • Details accordion is defaulted to open
     • And use the whole width of the screen (currently lots of white space on the left and right of the Create/Edit screen)
     • Subheader: Field mapping [dot] MARC Bibliographic
     • MCL List with the following columns (details of each column will be laid out in stories below)
       • Column 1: no header (will be used for arrows) - Scenario 2 and UIDATIMP-496
       • Column 2 Header: Action - Scenario 3
       • Column 3 Header: Field - Scenario 4
       • Column 4 Header: In. 1 (that's a capital "eye" in the first position) - Scenario 5
       • Column 5 Header: In. 2 (that's a capital "eye" in the first position) - Scenario 6
       • Column 6 Header: Subfield - Scenario 7
       • Column 7 Header: Subaction - Scenario 8
       • Column 8 Header: Data - Scenario 9
       • Column 9 Header: Position - Scenario 10
       • Followed by + sign to allow for adding rows - Scenario 11 and UIDATIMP-497
       • Followed by trashcan to add for deleting rows - Scenario 12 and UIDATIMP-498
     • Alternating grey and white rows in the MCL list
     • And DO NOT allow the MCL to be sorted by any of the column headers
2. Scenario 2 (skip this scenario; leave a blank column; work will be done in UIDATIMP-496)
   • Given the First (Arrows) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then include
     • No arrow if there is only 1 row
     • If more than 1 row
       • A down arrow on the first row
       • An up arrow on the last row
       • Up and Down arrows on every row between first and last
   • NOTE: The quickMARC app uses this arrow construction in their editing screen, so perhaps you can borrow from UIQM-5
3. Scenario 3
   • Given the Second (Action) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then include the following as a dropdown list
     • Ghost text: Select
     • Add
     • Delete
     • Edit
     • Move
   • And only allow 1 action to be selected in the list
   • NOTE: Depending on which action is selected, columns 7-9 (Subaction, Data, Position) will vary
4. Scenario 4
   • Given the Third (Field) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then include enough space for 9 characters plus the x ("empty the field") symbol, so that a user can input a MARC field or fixed field positions, e.g.
     • 900
     • 024
     • LDR/09
     • 008/10-12
5. Scenario 5 Per Masha, validation will be in later stories
   • Given the Fourth (Ind. 1) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then include enough space for 1 character plus the x ("empty the field") symbol
   • And only allow the following symbols:
     • [blank]
     • asterisk *
     • alphas
     • numbers
6. Scenario 6
   • Given the Fifth (Ind. 2) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then include enough space for 1 character plus the x ("empty the field") symbol
   • And only allow the following symbols:
     • [blank]
     • asterisk *
     • alphas
     • numbers
7. Scenario 7
   • Given the Sixth (Subfield) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then include enough space for 1 character plus the x ("empty the field") symbol
   • And only allow the following symbols:
     • [blank]
     • asterisk *
     • alphas
     • numbers
8. Scenario 8
   • Given the Seventh (Subaction) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then allow it to be
     • Completely empty (no data input field at all)
     • Or a dropdown list which will vary depending on the Action that was chosen. Details will be in the stories UIDATIMP-487, UIDATIMP-488, UIDATIMP-489, UIDATIMP-490, UIDATIMP-491, UIDATIMP-492-UIDATIMP-493)
9. Scenario 9
   • Given the Eighth (Data) column of the MCL component of this field mapping profile
   • When working with it on the Create/Edit screen
   • Then allow it to be
     • Completely empty (no data input field)
     • A free text data input field, which wraps to subsequent lines when the data is too long to fit onto one line
     • A formatted text data input field, which is laid out in subsequent stories (UIDATIMP-490, UIDATIMP-492, UIDATIMP-493)
10. Scenario 10
    • Given the Ninth (Position) column of the MCL component of this field mapping profile
    • When working with it on the Create/Edit screen
    • Then allow it to be
      • Completely empty (no data input field)
      • A dropdown list, which is laid out in a subsequent story (UIDATIMP-491)
11. Scenario 11 (skip this scenario; work will be done in UIDATIMP-497)
    • Given the Plus sign at the end of each row of the MCL component of this field mapping profile
    • When a user clicks the plus sign
    • Then insert a blank row beneath the row with the plus sign. The new row should only contain arrows, dropdowns, and data entry fields for Columns 1-6 until an Action is selected. (See 1-new-field-mapping-profile attached)
12. Scenario 12 (skip this scenario; work will be done in UIDATIMP-498)
    • Given the Trash can sign at the end of each row of the MCL component of this field mapping profile
    • When a user clicks the trash can
    • Then remove the row. NO confirmation modal is required
13. Scenario 13
    • Given the Create/Edit screen
    • When starting a completely blank details section
    • Then only show Column headers plus one row (see attached 1-new-field-mapping-profile)
      • With the Action dropdown list
      • Blank input fields for columns 3-6
      • Completely empty (no input fields) for columns 7-9
      • + sign and Trash can
14. Scenario 14
    • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

See attached screenshots, showing the brand new create/edit screen with nothing filled in, with the Action dropdown, and a screen with many modifications. This story only covers the first two mockups. The last one is not possible until all stories in this feature are complete.