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

Field Mapping Profile details: MARC Bib from MARC Bib 3 - Add 1st line

    XMLWordPrintable

    Details

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

      Description

      Purpose: To specify the Add details for a field's first subfield 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 third one covers the layout of the Add modification (for the first subfield of a MARC field) 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 Add action
        • Then leave columns 3-6 (Field, Ind 1, Ind 2, Subfield) blank
        • And add the following to columns 7-9 of the MCL (see attached mockup)
          • Column 7 (Subaction): Dropdown with ghost text Select and one option Add subfield
          • 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 on the Create/Edit screen
          • Column 9 (Position): Leave blank - no data field
      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 Add action
        • And fills in a Field in Column 3, and Data in column 8, but no Indicators or Subfield in columns 4-6
        • And the Field = 006, 007, or 008
        • Then consider that a valid Add action
        • And when the action is carried out, add the MARC fixed field 006, 007, or 008, with no indicators or subfields, and with whatever data was supplied 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 Add action
        • And fills in a Field in column 3, a Subfield in column 6, and Data in column 8, but no Indicators in columns 4-5
        • And the Field is anything other than 006, 007 or 008
        • Then consider that a valid Add action
        • And when the action is carried out, add the MARC variable field, with [blank] indicators, and with the specified subfield and data 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 Add action
        • And fills in a Field in column 3, Indicator(s) in one or both of columns 4-5, a Subfield in column 6, and Data in column 8
        • And the Field is anything other than 006, 007 or 008
        • Then consider that a valid Add action
        • And when the action is carried out, add the MARC variable field, with the specified indicators, subfield, and 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 Add action
        • And fills in a Field in column 3, and Data in column 8, but no Subfield in columns 6
        • And the Field = anything other than 006, 007, or 008
        • Then DO NOT consider that a valid action
        • And highlight the Subfield box in red
        • And require the user to fill in a Subfield before the field mapping profile can be saved
      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 Add action
        • And does not fill in anything in Field in column 3
        • Then DO NOT consider that a valid action
        • And highlight the invalid Field box in red
        • And require the user to fill in the Field box before the field mapping profile can be saved
      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 Add action
        • And DOES NOT fill in any Data in column 8
        • Then DO NOT consider that a valid action
        • And highlight the Data box in red
        • And require the user to fill in Data before the field mapping profile can be saved
      8. Scenario 8
        • 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 Add action
        • And fills in an asterisk in any of fields 4-6 (Ind 1, Ind 2, Subfield)
        • Then DO NOT consider that a valid action
        • And highlight the invalid Ind 1, Ind 2, and/or Subfield box in red
        • And require the user to fill in a valid character before the field mapping profile can be saved.
          • Valid Indicator characters are [blank], alpha, numeric
          • Valid Subfield characters are alpha, numeric
      9. Scenario 9
        • 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 Add action
        • And puts 999 in the Field field and f in Indicator 1 and Indicator 2
        • Or puts 001 in the Field field
        • Or puts 005 in the Field field
        • Then DO NOT consider that a valid action
        • And highlight the Field/Indicators boxes in red
        • And require the user to change the data or delete the row before the field mapping profile can be saved
        • Fields 001, 005, and 999 ff cannot be updated via the MARC modification profiles
      10. Scenario 10
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See attached mockup and guide to adding fields into the MARC record

      NOTE: When adding fields 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

        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