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

Field Mapping Profile details: MARC Bib from MARC Bib 1.3 - Trash can icon

    XMLWordPrintable

    Details

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

      Description

      Purpose: To create the trash can option that removes a row 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 remove a modification rows from the MARC field mapping profile MCL
      So that any unnecessary modifications can be deleted

      "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 trash can at the end of each row 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 there should be a Trash can as the last icon at the end of each modification row
      2. Scenario 2
        • Given the Trash can at the end of each modification row
        • When the user clicks it
        • And it is the only modification row on the screen
        • The Trash should be disabled/greyed out
      3. Scenario 3
        • Given the Trash can at the end of each modification row
        • When the user clicks it
        • And there are more than one modification row on the screen
        • Then delete the row
      4. Scenario 4 cannot be tested until after UIDATIMP-488
        • Given the Trash can at the end of each modification row
        • When the user clicks it
        • And the row is the first row in a group of "Add" modification rows with associated subfields
        • Then delete the first row and all associated subfield rows (so that the subfield rows are not orphaned)
      5. Scenario 5
        • Given the Trash can at the end of each modification row
        • When the user clicks it
        • And a row is deleted or emptied, per the above scenarios
        • Then do not display a confirmation modal (will be too much noise and extra clicks for the user)
      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:
                Ivan Kryzhanovskyi Ivan Kryzhanovskyi
                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