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

Create data import settings page's 3rd pane for Field Mapping Profiles



    • EPAM BatchLoader Sprint 20, EPAM BatchLoader Sprint 21
    • 1
    • Folijet


      Purpose: To be able to create and save mapping profiles, so that they can be applied to saved and ad hoc job profiles used in Data Import

      As a staff person
      I want to be able to create and store data mapping profiles for the Data Import app
      So that I can assemble them, along with matching and action profiles in various configurations of job profiles
      And so that I do not have to reconstruct these configurations every time I import a new file


      • This story is only for creating the outline of the mapping profile pane on the settings screen. There will be additional stories for creating the create/edit screens for data mappings and for the detailed configuration of mappings.


      1. Scenario 1
        • Given the Data Import Settings
        • When a User clicks the Field mapping profiles setting in the second pane
        • Then the Field mapping profiles option in the second pane should turn grey with white text and
        • A third pane should open, displaying a list of the existing Field mapping profiles
        • As shown in attachment 80b-Settings Field mapping profiles 3rd pane-no count.png
      2. Scenario 2
        • Given the Field mapping profiles third pane
        • When displaying the pane
        • Then the format of the pane should be as follows, as shown in attachment 80b-Settings Field mapping profiles 3rd pane-no count.png
          • Header: [field mapping profile icon] followed by Field mapping profiles followed by a down caret [No action for now - action is covered by UIDATIMP-??]
          • Subheader: # profiles, where # is the number of field mapping profiles in the results list
          • New button on right side of header [No action for now - action is covered by UIDATIMP-227]
          • Top of results list: search box [See scenarios 3-4 for search details]
          • Results list column headers
            • Check box [No action for now - action is covered by UIDATIMP-??]
            • Name
            • FOLIO record type
            • Tags
            • Updated
            • Updated by
          • Results list data elements per row (alternating rows in white and grey)
            • Check box [No action for now - action is covered by UIDATIMP-??]
            • Field mapping profile icon followed by field mapping profile name
            • FOLIO record icon followed by the Record type, Record type is sentence case, except MARC is always all-caps, e.g. MARC holdings
              • Acceptable Record Types
                • Instance
                • Holdings
                • Item
                • MARC bibliographic
                • MARC holdings
                • MARC authority
                • Order
                • Invoice
            • [Ignore the white space in the picture - we may add a little more indication of how much mapping has been done, but not until the future]
            • Tags icon followed by tags; multiple tags are separated by comma [space], e,g. first, second, third
            • Edit pencil icon followed by most recent update date
            • User icon followed by most recent updater's name (firstname lastname) and username in parentheses, e.g. John Doe (johndoe)
          • Default sort order should be alphabetical A-Z by profile name
          • User should be able to sort and reverse sort by clicking on any of the column headers
          • End of list component (icon and wording)
      3. Scenario 3
        • Given a string entered into the search box of the Data Import Settings Field mapping profiles
        • When a User presses Enter on their keyboard, or the Search button to the right of the Search box
        • Then FOLIO should check for that string against the following fields in the Field mapping profiles record:
          • Name
          • Mapped (changing to FOLIO record type)
          • Tags
      4. Scenario 4
        • Given a string entered into the search box
        • When a User views the list of existing Field mapping profiles
        • Then the entered text should be highlighted in the list
        • And the list should be filtered down to only display Field mapping profiles that include that string
      5. Scenario 5
        • Given a string entered into the search box
        • When a User wants to view the entire list of profiles
        • Then a reset "x" at the right of the search box should allow the search data to be deleted without back-spacing
        • And default back to all results showing in the list
      6. Scenario 6
        • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot



      • Consider changing the search (filter) to trigger without an explicit enter in the future. Some issues with that function in Inventory previously, so we're using the explicit Enter key or Enter button for now.


      TestRail: Results


          Issue Links



                Oleksandr Yehorov Oleksandr Yehorov
                abreaux Ann-Marie Breaux
                Ann-Marie Breaux Ann-Marie Breaux
                0 Vote for this issue
                2 Start watching this issue



                  TestRail: Runs

                    TestRail: Cases