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

Field Mapping Profile details: MARC Bib from MARC Bib 4 - Add Subsequent lines

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 43, Folijet Sprint 91
    • Story Points:
      5
    • Development Team:
      Folijet

      Description

      Purpose: To specify the Add details for a field's subsequent subfields in the MARC record modifications field mapping profile

      As a staff person importing MARC records
      I want to specify Add 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 fourth one covers the layout of the Add modification (for subsequent subfields of a MARC field) on the Create/Edit screen. If a user needs to add multiple subfields into the same new field, they will add as many rows as there are subfields, and those rows will act together in terms of 1) traveling up and down the modification list together and 2) adding a new field with multiple subfields

      Note to A-M: when testing this, also test scenario 4 from UIDATIMP-496 and scenario 3 from UIDATIMP-497 and scenario 4 from UIDATIMP-498

      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
        • And the User selects Add in the Create/Edit screen
        • Then they will have an optional dropdown in column 7 to Add a subfield
      2. Scenario 2
        • Given that the User selects Add and selects the option to Add a subfield in column 7
        • Then adjust the details of the Create/Edit screen like this (see attached wireframe)
          • Add another row directly below the first "Add" row
          • Make it the same grey or white color as the first "Add" row
          • Do not include up/down arrows at the left side of the row
          • Do not include the "Add" action button in column 2
          • Copy the Field, Indicator 1, and Indicator 2 information from the first "Add" row, and grey them out. If the user changes the Field, Indicator 1, or Indicator 2 in the first "Add" row, then copy those changes to the subsequent row(s) but grey them out
          • Do not copy the Subfield information from the first "Add" row
          • Include the Subaction dropdown, defaulted to the "Select" ghost text and allow the user to select "Add subfield"
          • Do not copy the Data from the first "Add" row
          • Position column stays blank
          • Do not include the + sign on the subfield rows (only on the first row). When clicked on the first row, + sign adds a whole new row (not a subfield row), as documented in UIDATIMP-497
          • Trashcan on the first "Add" row deletes that row plus any subfield rows currently associated with it (so that there are not orphaned subfield rows sitting in the MCL), as documented in UIDATIMP-498
          • Trashcan on a subsequent subfield row deletes that individual row, as documented in UIDATIMP-498
      3. Scenario 3
        • Given that the User selects Add and selects the option to Add a subfield in column 7
        • And adds a subfield and data into the subsequent subfield row
        • Then consider that a valid action
        • And when the action is carried out, add the field, its first subfield and its data, and any subsequent associated subfields and their data, all in the same MARC field, in the subfield order that they display in the modification profile. Note that fields can sometimes repeat the same subfield, so that is not an error or invalid. test import after all the MARC modifications stories are complete
      4. Scenario 4
        • Given that the User selects Add and selects the option to Add a subfield in column 7
        • And fails to add both a subfield and data in the subsequent subfield row
        • Then DO NOT consider that a valid action
        • And highlight the Subfield and/or Data box in red
        • And require the user to fill in both the Subfield and Data box, or delete the row, before the field mapping profile can be saved
      5. Scenario 5
        • Given that the User selects Add and selects the option to Add a subfield in column 7
        • And adds an asterisk in the subfield box of the subsequent subfield row
        • Then DO NOT consider that a valid action
        • And highlight the Subfield box in red
        • And require the user to fill in a valid value in the Subfield box (alpha or numeric), or delete the row, before the field mapping profile can be saved
      6. Scenario 6
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See attached mockups

      NOTE: The same rules about field placement apply as indicated in UIDATIMP-487

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Ihor_koba Ihor Koba
                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