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

Field Mapping Profile details: MARC Bib from MARC Bib 7 - Edit-Insert

    XMLWordPrintable

    Details

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

      Description

      Purpose: To specify the Edit action's Insert 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 seventh one covers the layout of the Insert subaction of the Edit modification on the Create/Edit screen. It can be used to add a subfield to an existing field, or to add data into an existing subfield of an existing field. If an entire new field needs to be added, then use the "Add" modification instead.

      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 Insert 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): Free text data field; allow it to wrap in the text box if necessary, so that the user can view the entire text in the Create/Edit screen
          • Column 9 (Position): Dropdown list with
            • Ghost text: Select
            • before string (Note: lower-case "b")
            • after string (Note: lower-case "a")
            • new subfield (Note: lower-case "n")
      2. Scenario 2
        • Given the above positions in column 9
        • When a user selects one of them
        • Then when the action is carried out, position the inserted data as follows
          • before string: add the new data in the specified, existing subfield, before the existing data in that subfield test import after all the MARC modifications stories are complete
          • after string: add the new data in the specified, existing subfield, after the existing data in that subfield test import after all the MARC modifications stories are complete
          • new subfield: add the new data in the new specified subfield, and place the subfield as the last subfield in the specified field. Note that subfields can often repeat within the same field, so it's OK for the newly-inserted subfield to have the same letter/number as an existing subfield in the field 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 Insert subaction
        • And the user enters a Field in column 3, and a Subfield in column 6, and a Data string in column 8, and a Position in column 9, and leaves asterisks in columns 4-5 (In 1, In 2)
        • 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 insert the specified data in the specified subfield, in the specified position. 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 Insert subaction
        • And the user enters a Field in column 3, Indicator(s) in column 4 and/or 5 ([blank], alpha, or numeric), a Subfield in column 6 (alpha or numeric), and a Data string in column 8, and a Position in column 9
        • 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 insert the specified data in the specified subfield, in the position as detailed in Scenario 2. Leave any other data in any existing 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 Insert subaction
        • And the user does not select a Field in column 3
        • Then DO NOT consider that a valid Edit-Insert 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.
      6. Scenario 6
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Insert subaction
        • And the user does not enter a Subfield in column 6
        • Then DO NOT consider that a valid Edit-Insert 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.
      7. Scenario 7
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Insert subaction
        • And the user does not enter a Data in column 8
        • Then DO NOT consider that a valid Edit-Insert action, regardless of any other data in that row
        • And highlight the Data box in red
        • And do not allow the field mapping profile to be saved until the Data box has been filled in or the row has been deleted.
      8. Scenario 8
        • Given the above Create/Edit screen
        • When the user selects the Edit modification and Insert subaction
        • And the user does not select any Position option in column 9
        • Then DO NOT consider that a valid Edit-Insert action, regardless of any other data in that row
        • And highlight the Position box in red
        • And do not allow the field mapping profile to be saved until the Position box has been filled in or the row has been deleted.
      9. Scenario 9
        • 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:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases