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

Field Mapping Profile details: MARC Bib from MARC Bib 2 - Delete

    XMLWordPrintable

    Details

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

      Description

      Purpose: To specify the Delete details for the MARC record modifications field mapping profile

      As a staff person importing MARC records
      I want to specify delete 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 second one covers the layout of the Delete modification on 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
        • And the user selects the Delete action
        • Then add a single asterisk as a default into columns 4-6 (Ind 1, Ind 2, Subfield) of the row
        • And do not add any data fields to columns 7-9 of the MCL
      2. Scenario 2
        • 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 the Delete action
        • And fills in a Field in Column 3, but leaves the asterisks for Indicators and Subfield in columns 4-6
        • Then consider that a valid Delete instruction
        • And when the action is carried out, delete any instances of that field in any record in the incoming file, including all its subfields and data, and regardless of any indicators or subfields test import after all the MARC modifications stories are complete
      3. Scenario 3
        • 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 the Delete action
        • And fills in a Field in column 3, plus one or both Indicators in columns 4-5, but leaves the asterisk for Subfield in column 6, Specified indicators can be [blank], any alpha, or any numeric, as long as they are single characters
        • Then consider that a valid Delete action
        • And when the action is carried out, delete any instances of that field in any record in the incoming file, including all its subfields and data, but only if one or both indicators match the ones specified in the delete action. If both 1st and 2nd indicator are specified, then both must match for the field to be deleted from the record. test import after all the MARC modifications stories are complete
      4. Scenario 4
        • 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 the Delete action
        • And fills in a Field in column 3, plus a Subfield in column 6, and leaves asterisks for Indicators in columns 4-5, Specified subfields can be any alpha or any numeric, as long as they are single characters
        • Then consider that a valid Delete action
        • And when the action is carried out
          • Delete any instances of that specified subfield and its data in the specified field in any record in the incoming file, regardless of the specified field's indicators. test import after all the MARC modifications stories are complete
          • And If that subfield is the only subfield in the specified field, then also delete the entire field test import after all the MARC modifications stories are complete
          • If other subfields remain in the specified field, then delete the specified subfield and its data, but leave the field and the remaining subfields and their data. test import after all the MARC modifications stories are complete
      5. Scenario 5
        • 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 the Delete action
        • And fills in a Field in column 3, plus one or both Indicators in columns 4-5, plus a Subfield in column 6. Specified indicators can be [blank], any alpha, or any numeric, as long as they are single characters. Specified subfields can be any alpha or any numeric, as long as they are single characters
        • Then consider that a valid Delete action
        • And when that action is carried out
          • Delete any instances of that Subfield and its data in the specified field in any record in the incoming file, but only if one or both indicators match the ones specified in the delete action. If both 1st and 2nd indicator are specified, then both must match for the Subfield to be deleted from the record.
          • If that subfield is the only subfield in the specified field, then also delete the entire field test import after all the MARC modifications stories are complete
          • If other subfields remain in the specified field, then delete the specified subfield and its data, but leave the field and the remaining subfields and their data. test import after all the MARC modifications stories are complete
      6. Scenario 6
        • 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 the Delete action
        • And fills in one or both Indicators in columns 4-5 and/or a Subfield in column 6, but does NOT fill in a Field in column 3
        • Then DO NOT consider that a valid Delete action
        • 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.
      7. Scenario 7
        • 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 the Delete action
        • And fills in a Field, one or both Indicators in columns 4-5, but does NOT fill in a Subfield in column 6 (no asterisk, alpha, or numeric)
        • Then DO NOT consider that a valid Delete action
        • 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.
      8. Scenario 8
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See attached mockup

        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