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

Field Mapping Profile details: MARC Bib from MARC Bib 8 - Move-New field

    XMLWordPrintable

    Details

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

      Description

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

      As a staff person importing MARC records
      I want to specify Move 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 eighth one covers the layout of the Move to New field 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 Move modification and New field 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
            • Existing field (see UIDATIMP-493)
            • New field
          • Column 8 (Data): 4 boxes:
            • Box 1 ghost text Field (allows the same characters as column 3/Field)
            • Box 2 ghost text: In. 1 (allows the same characters as column 4/In. 1)
            • Box 3 ghost text: "In. 2" (allows the same characters as column 5/In. 2)
            • Box 4 ghost text: Subf. (allows the same characters as column 6/Subfield)
            • Column 8 has NO free text data box
          • Column 9 (Position): Leave blank
      2. Scenario 2
        • Given the above Create/Edit screen
        • When the user selects the Move modification and New field subaction
        • And the user enters a Field in column 3 and leaves asterisks in columns 4-6 (In 1, In 2, Subfield)
        • And only enters a field in the first box of column 8
        • Then consider that a valid Move 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 move each subfield to the field indicated in the first box of column 8, retaining the indicators, subfields, and data from the original field. Then remove the original field and all its subfields and data. test import after all the MARC modifications stories are complete
      3. Scenario 3
        • Given the above Create/Edit screen
        • When the user selects the Move modification and New field subaction
        • And the user enters a Field in column 3, values in one or both Indicator fields columns 4-5 ([blank], alpha, numeric) and leaves an asterisk in Subfield column 6
        • And only enters a field in the first box of column 8
        • Then consider that a valid Move action
        • And when the action is carried out, inspect any occurrences of that field in any record in the incoming file, paying attention to the appropriate indicators, but regardless of subfield, and move each subfield to the field indicated in the first box of column 8, retaining the indicators, subfields, and data from the original field. Then remove the original field and all its subfields and data. test import after all the MARC modifications stories are complete
      4. Scenario 4
        • Given the above Create/Edit screen
        • When the user selects the Move modification and New field subaction
        • And the user enters a Field in column 3, asterisk or values in one or both Indicator fields columns 4-5 (*, [blank], alpha, numeric) and a value in Subfield column 6 (alpha or numeric)
        • And only enters a field in the first box of column 8
        • Then consider that a valid Move action
        • And when the action is carried out, inspect any occurrences of that field in any record in the incoming file, paying attention to the appropriate indicators and subfield, and move the subfield to the field indicated in the first box of column 8, retaining the indicators, subfield, and data from the original field. test import after all the MARC modifications stories are complete
          • If that was the only subfield in the original field, then remove the original field, its subfield and data.
          • If the original field contains other subfields than the specified one, remove the specified subfield and its data from the original field, but retain the field, its indicators, its other subfields, and their data
      5. Scenario 5
        • Given the above Create/Edit screen
        • When the user selects the Move modification and New field subaction
        • And the user enters a Field in column 3, asterisk or values in one or both Indicator fields columns 4-5 (*, [blank], alpha, numeric), and a value in Subfield column 6 (alpha or numeric)
        • And enters a field in the first box of column 8, values in the indicator 2nd-3rd boxes of column 8 ([blank], alpha, numeric), and a value in the subfield 4th box of column 8 (alpha or numeric)
        • Then consider that a valid Move action
        • And when the action is carried out, inspect any occurrences of that field in any record in the incoming file, paying attention to the appropriate indicators and subfield, and move the subfield to the field indicated in the first box of column 8, assigning the indicators indicated in the 2nd-3rd boxes of column 8, and the subfield indicated in the 4th box of column 8, with the data from the original subfield. In this scenario, the data will be in a new subfield in the new field, rather than retaining the subfield that it had in the original field. test import after all the MARC modifications stories are complete
          • If that was the only subfield in the original field, then remove the original field, its subfield and data. test import after all the MARC modifications stories are complete
          • If the original field contains other subfields than the specified one, remove the specified subfield and its data from the original field, but retain the field, its indicators, its other subfields and their data test import after all the MARC modifications stories are complete
      6. Scenario 6
        • Given the above Create/Edit screen
        • When the user selects the Move modification and New field subaction
        • Then the following data combinations should NOT be considered valid
        • And the appropriate boxes should be outlined in red
        • And do not allow the field mapping profile to be saved until the errors have been corrected or the row has been deleted.
          • No field indicated in column 3
          • 001, 005, or 999 ff in columns 3 or 8
          • Values other than *, [blank], alpha, numeric in Indicator columns 4-5
          • Values other than *, alpha, numeric in Subfield column 6
          • The same field in column 3 and the first box of column 8 ["Please choose a different field" under column 8 box]
          • No field indicated in the first box of column 8
          • Values other than *, [blank], alpha, numeric in the 2nd-3rd Indicator boxes in column 8
          • Values other than *, [blank], alpha, numeric in the 4th Subfield box in column 8
          • Subaction not selected in column 7
      7. Scenario 7
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      Notes on field placement

      • If an existing field is retained, leave it in the same place in the MARC record as it was originally
      • When adding a new field into the MARC record, follow these placement instructions
        • 0xx fields: put in numeric order with other 0xx fields already in the record
        • 1xx fields: put in numeric order with other 1xx fields already in the record
        • 2xx fields: put in numeric order with other 2xx fields already in the record
        • 3xx fields: put in numeric order with other 3xx fields already in the record
        • 4xx fields: add any new 4xx field as the last field in the 4xx bloc of fields
        • 5xx fields: add any new 5xx field as the last field in the 5xx bloc of fields
        • 6xx fields: add any new 6xx field as the last field in the 6xx bloc of fields
        • 7xx fields: add any new 7xx field as the last field in the 7xx bloc of fields
        • 8xx fields: add any new 8xx field as the last field in the 8xx bloc of fields
        • 9xx fields: put in numeric order with other 9xx fields already in the record
        • 999 field: put above the 999 ff field
        • If any fields are repeated (e.g. multiple 035s or 910s, add the new one below any existing ones
        • Field 999 ff (with the FOLIO UUIDs) is always the last field of the record

      See attached mockups, examples, and logic details

        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:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases