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

Field Mapping Profile details: MARC Bib from MARC Bib 6 - Edit-Replace

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      Folijet Sprint 91
    • Story Points:
      1
    • Development Team:
      Folijet

      Description

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

      As a staff person importing MARC records
      I want to specify Edit 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 sixth one covers the layout and logic of the Replace subaction of the Edit modification on the Create/Edit screen.

      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 Edit modification and Replace 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
            • Insert
            • Remove
            • Replace
          • Column 8 (Data):
            • 1st row: Find: [text box]
            • 2nd row: Replace with: [text box]
            • Both text boxes should be free text data fields; allow it to wrap if necessary, so that the user can view the entire text in the Create/Edit screen
          • Column 9 (Position): Leave blank
      2. Scenario 2
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And fills in a Fixed Field (LDR, 006, 007, 008) with optional fixed field positions in Column 3, and Find/Replace data in column 8, but no Indicators or Subfield in columns 4-6
        • Then consider that a valid Edit action
        • And when the action is carried out, inspect any occurrences of that fixed field in any record in the incoming file, replace the first data string with the second data string in whichever position(s) it is in. Leave any other data in the fixed field as-is. test import after all the MARC modifications stories are complete
      3. Scenario 3
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user enters a Field in column 3 (other than LDR, 006, 007, 008) and Find/Replace data strings in column 8, and leaves asterisks in columns 4-6 (In 1, In 2, Subfield)
        • Then consider that a valid Edit action
        • And when the action is carried out, inspect any occurrences of that field in any record in the incoming file, regardless of indicators or subfields, and replace the first data string with the second data string in whichever subfield it is in. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the existing field. test import after all the MARC modifications stories are complete
      4. Scenario 4
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user enters a Field in column 3 (other than LDR, 006, 007, 008), Indicator(s) in column 4 and/or 5 ([blank], alpha, or numeric) and Find/Replace data strings in column 8, but leaves an asterisk for Subfield in column 6
        • Then consider that a valid Edit action
        • And when the action is carried out, inspect any occurrences of that field in any record in the incoming file, but only if the field's indicators match the ones in the modification action, and replace the first data string with the second data string in whichever subfield it is in. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the existing field. test import after all the MARC modifications stories are complete
      5. Scenario 5
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user enters a Field in column 3 (other than LDR, 006, 007, 008), a Subfield in column 6, and Find/Replace data strings in column 8, but leaves asterisks for both Indicators in columns 4 or 5
        • Then consider that a valid Edit action
        • And when the action is carried out, inspect any occurrences of that specific subfield in that specific field (regardless of the field's indicators) in any record in the incoming file, and replace the first data string with the second data string in the specified subfield. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the existing field. test import after all the MARC modifications stories are complete
      6. Scenario 6
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user enters a Field in column 3 (other than LDR, 006, 007, 008), Indicators in columns 4 and/or 5 ([blank], alpha, numeric), a Subfield in column 6 (alpha or numeric), and Find/Replace data strings in column 8
        • Then consider that a valid Edit action
        • And when the action is carried out, inspect any occurrences of that specific subfield in that specific field in any record in the incoming file, but only if the field's indicators match the specified ones, and then replace the first data string with the second data string in the specified subfield. Leave any other data in the subfield as-is, and do not change any subfields or indicators in the existing field. test import after all the MARC modifications stories are complete
      7. Scenario 7
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user enters an asterisk * in the "Find" section of Data column 8 (along with non-asterisk "Replace" data, Field, Subfield, and Indicators)
        • Then consider that a valid Edit action
        • NOTE Field must be valid; Subfield must be valid (alpha or numeric); Indicators can be wildcard or filled in (*, [blank], alpha, numeric)
        • And when the action is carried out, inspect any occurrences of that specific subfield in that specific field in any record in the incoming file, (also paying attention to indicators if they are specified), and then in the specified subfield, replace the complete data string (no matter what the original data string was) with the second data string. Do not change any subfields or indicators in the existing field. test import after all the MARC modifications stories are complete
      8. Scenario 8
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user does not select a Field in column 3
        • Then DO NOT consider that a valid Edit-Replace action, regardless of any other data in that row
        • And highlight the Field box in red
        • And do not allow the field mapping profile to be saved until the Field box has been filled in or the row has been deleted.
      9. Scenario 9
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user does not enter an asterisk, alpha or numeric in Subfield column 6
        • And the Field is anything other than Fixed Field (LDR, 006, 007, 008)
        • Then DO NOT consider that a valid Edit-Replace action, regardless of any other data in that row
        • And highlight the Subfield box in red
        • And do not allow the field mapping profile to be saved until the Subfield box has been filled in or the row has been deleted.
      10. Scenario 10
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Replace subaction
        • And the user does not enter Find/Replace data strings in Column 8
        • Then DO NOT consider that a valid Edit-Replace action, regardless of any other data in that row
        • And highlight the Find/Replace data boxes in red
        • And do not allow the field mapping profile to be saved until the Find/Replace data boxes have been filled in or the row has been deleted.
      11. Scenario 11
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See attached mockups, examples, and logic details

        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