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

Data import settings page's 4th pane for Match Profiles: Changes needed to support Static value text submatches



    • Template:
    • Sprint:
      EPAM BatchLoader Sprint 36, EPAM BatchLoader Sprint 37
    • Story Points:
    • Development Team:


      Purpose: Document the changes needed in the UI for Create/Edit/View match profiles when match is based on a static value

      As a staff person
      I want to be able to use a static value as a submatch (e.g. match on Instance HRID first, then submatch on Holdings location field)
      So that the match details can identify the correct subrecord within a primary match

      See overview PPT at https://docs.google.com/presentation/d/1r-MLsfgzrjdxhMm6z0AKCXWxr3b8B-yG35KgPzkG47g/edit#slide=id.p1


      1. Scenario 1
        • Given the Create/Edit screen for Match profiles
        • When the Incoming record type = Not applicable - match to static value
        • Then the top section of the Match criterion should be adjusted as indicated in the attached Match profile expansion 3.PNG
          • Header label: Change from Incoming MARC record to Static value (submatch only)
          • Incoming match field label: Change from MARC field in incoming record to Static value
          • Field/Indicators/Subfield text boxes: Change to one free-text textbox. Allow input of any string in this field
          • Remove the "Qualifier" section
          • Remove the "Only compare" section
          • Keep the "Match criterion" dropdown list and the "Existing record" sections as-is
      2. Scenario 2
        • Give then View details screen for Match profiles
        • When the changes in Scenarios 1 have been made in the Create/Edit screen to make it support a Static value match
        • And a saved match profile reflects these changes
        • Then make sure these changes show in the view details screen See attached video - the existing record field name is showing the backend field name instead of the label. Is that a translation issue?
        • And that the details are not editable in the view details screen
      3. Scenario 3
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

      See attached screenshot

      Will need changes to the form renderer

        TestRail: Results


            Issue Links



                taras_tkachenko Taras Tkachenko
                abreaux Ann-Marie Breaux
                0 Vote for this issue
                3 Start watching this issue



                    TestRail: Runs

                      TestRail: Cases