Uploaded image for project: 'ui-data-import'
  1. ui-data-import
  2. UIDATIMP-496

Field Mapping Profile details: MARC Bib from MARC Bib 1.1 - Up/Down Arrows

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 42
    • Story Points:
      2
    • Development Team:
      Folijet

      Description

      Purpose: To create the up/down arrows that resequence rows in the MCL of the Field Mapping profile details for MARC modifications

      As a staff person importing MARC records
      I want to be able to adjust the sequence of modifications applied to those MARC records via the field mapping profile
      So that they are carried out in the appropriate order

      "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 one covers the placement and action of the up/down arrows in Column 1 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 the first column should not have a header and will be used for up/down arrows to resequence the modification rows in the list.
        • NOTE: The quickMARC app uses this arrow construction in their editing screen, so perhaps you can borrow from UIQM-5
      2. Scenario 2
        • Given the First (Arrows) column of the MCL component of this field mapping profile
        • When working with it on the Create/Edit screen
        • And there is only 1 modification row
        • Then do not include an arrow
      3. Scenario 3
        • Given the First (Arrows) column of the MCL component of this field mapping profile
        • When working with it on the Create/Edit screen
        • And there is more than 1 modification row
        • Then include
          • 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
      4. Scenario 4 cannot be tested until after UIDATIMP-488
        • Given the First (Arrows) column of the MCL component of this field mapping profile
        • When working with it on the Create/Edit screen
        • And there is an "Add" modification row that includes additional, associated subfield rows
        • Then only display an arrow next to the first row, not the additional, associated subfield rows
      5. Scenario 5
        • Given the First (Arrows) column of the MCL component of this field mapping profile
        • When a user clicks the up or down arrow
        • Then move the modification row (plus its additional, associated subfield rows, if there are any) up or down 1 position in the list of modifications
      6. Scenario 6
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See attached mockups

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Mariia_Aloshyna Mariia Aloshyna
                Reporter:
                abreaux Ann-Marie Breaux
                Tester Assignee:
                Ann-Marie Breaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases