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

MARC Bib field mapping profile: details for Update Selected fields on Create/Edit screen

    XMLWordPrintable

    Details

    • Template:
      Folijet UI story template
    • Sprint:
      Folijet Sprint 96, Folijet Sprint 97
    • Story Points:
      5
    • Development Team:
      Folijet

      Description

      Purpose: To indicate that only certain fields in an SRS MARC record should be updated, instead of replacing the entire record, when a user is importing

      As a staff person working with Data Import
      I want to be able to import a MARC file and have it only update specific fields in the existing SRS MARC record
      So that I can apply very specific updates when needed without the risk of losing the details of the existing record

      Scenarios

      1. Scenario 1
        • Given the Settings/Data import/Field mappings Create/Edit screen
        • When the user selects FOLIO record type = MARC Bibliographic and Field mappings for MARC = Updates
        • Then display the MARC updates field mapping details in the field mappings Details section, as shown in the attached MARC Updates - create edit.PNG
          • Header: Field mapping [space dot space] MARC Bibliographic [space dot space] Updates
          • Subtext: If updates should only affect specific fields, add them here.
          • Default to one row of update details, with headers
            • Field (leave blank, required)
            • In. 1 (default to *, not required)
            • In. 2 (default to *, not required)
            • Subfield (default to *, required)
        • NOTE: Ignore the "Override" section of the mockup. That will be handled in UIDATIMP-631
      2. Scenario 2
        • Given the Update area of the MARC field mapping profile
        • When the user would like to add a row, remove a row, or resequence a row
        • Then do it the same way as described in UIDATIMP-496 (up/down arrows) , UIDATIMP-497 (plus sign) , UIDATIMP-498 (trash can)
      3. Scenario 3 (cannot be checked until backend is done; MODSOURCE-184)
        • Given the Update area of the MARC field mapping profile
        • When the user fills in any MARC fields in this section
        • Then follow this logic when importing a MARC Bibliographic file:
          • Only overlay/replace the indicated MARC field in the existing SRS MARC record. Leave all other fields untouched. When the specified field(s) are updated, then the corresponding Instance fields should also be updated, based on the default MARC-Instance map.
          • If Indicator 1 and/or Indicator 2 has a value of alpha, numeric, [blank], or [space], then only replace the MARC field(s) that have the same indicator values
          • If Indicator 1 and/or Indicator 2 has a value of *, then replace the corresponding MARC field(s) regardless of indicator
          • If Subfield has a value of alpha or numeric, then only replace that subfield in the corresponding MARC field
          • If Subfield has a value of *, then replace the entire corresponding MARC field(s) regardless of subfield
          • If the specified field does not exist, add that field to the existing SRS MARC, without changing any of the existing fields in the record
      4. Scenario 4
        • Given the MARC-MARC Create field mapping screen
        • When the User selects Modify or Update for the MARC field mapping
        • And then changes to the other one (changes from Modify to Update, or Update to Modify)
        • Regardless if there are existing details or not
        • Then display the following confirmation modal:
          • Header: Please confirm
          • The previous [Modify or Update, depending on what the former profile was] field mapping profile details will be deleted when you switch to [Update or Modify, depending on what the new profile is]. Do you want to continue?
          • Left Button: Cancel
            • If clicked, change the Field mappings for MARC field back to the former type and do not change the details
          • Right Button: Continue
            • If clicked, change the Field mappings for MARC field to the new type, erase the former details below, and show an empty new details area in the format corresponding to the new type
      5. Scenario 5
        • Given the MARC-MARC Edit field mapping screen
        • When the User selects Modify or Update for the MARC field mapping
        • And then changes to the other one (changes from Modify to Update, or Update to Modify)
        • Then display the following confirmation modal:
          • Header: Please confirm
          • The previous [Modify or Update, depending on what the former profile was] field mapping profile details will be deleted when you switch to [Update or Modify, depending on what the new profile is]. Do you want to continue?
          • Left Button: Cancel
            • If clicked, change the Field mappings for MARC field back to the former type and do not change the details
          • Right Button: Continue
            • If clicked, change the Field mappings for MARC field to the new type, erase the former details below, and show an empty new details area in the format corresponding to the new type
      6. Scenario 6
        • Given the MARC-MARC Edit field mapping screen
        • When the User changes to the other MARC field mapping (from Modify to Update, or Update to Modify)
        • And confirms the change modal
        • But then closes the edit window without saving changes (after seeing the unsaved changes modal and confirming they want to discard changes)
        • Then revert the profile to the old MARC field mapping choice and details
      7. Scenario 7
        • Ensure this story passes Accessibility testing
      8. Scenario 8
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      Some examples:

      • Only update the 856 field (it has a new $u; rest of the incoming MARC record is brief and not useful)
      • Only update the 590 field (there is no 590 in the existing record; add the 590 and do not touch any of the other fields in the existing SRS record)
      • Only update the 907 field (replace the 907 with the incoming 907; do no touch any of the rest of the SRS MARC)

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Ihor_koba Ihor Koba
                Reporter:
                abreaux Ann-Marie Breaux
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases