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

CSP Rejection Details

None

CSP Request Details

None

CSP Approved

None

Description

Purpose: To be able to create and save match 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 match profiles for the Data Import app
So that I can assemble them, along with action and mapping 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

Notes:

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

Live prototype:
https://xd.adobe.com/view/0bb2d8ab-aabd-4ff6-4d5a-faa59a93368e-7d83/

Brief video walk-through
https://www.dropbox.com/s/3slcv4v49qm92rv/2018-11-06-data-import-19.mp4?dl=0

Sample data: https://docs.google.com/spreadsheets/d/1sMiwp6nbb08H9SOD-zxIsJ1i5d0e8RXZ_mliIw9mmDA/edit#gid=1212064214

Scenarios

  1. Scenario 1

    • Given the Data Import Settings

    • When a User clicks the Match profiles setting in the second pane

    • Then the Match profiles option in the second pane should turn grey with white text and

    • A third pane should open, displaying a list of the existing match profiles

    • As shown in attachment 40-Settings Match profiles.png

  2. Scenario 2

    • Given the Match profiles third pane

    • When displaying the pane

    • Then the format of the pane should be as follows, as shown in attachment 40-Settings Match profiles.png

      • Header: [match profile icon] followed by Match profiles followed by a down caret [No action for now - action is covered by future story]

      • Subheader:

        1. profiles

        , where # is the number of match profiles in the results list

      • New button (no plus sign) on right side of header [No action for now - action is covered by future story]

      • Top of results list: search box [No action for now - action is covered by future story]

      • Results list column headers

        • Check box [Can check and uncheck the checkboxes, but no action for now; top checkbox does not yet affect the individual line checkboxes for now, and all action is covered by future story]

        • Name

        • Match

        • 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 future story]

        • Match profile icon followed by match profile name (row 2 in sample data) [NOTE: Match profile name must be unique]

        • Icon for FOLIO record type being matched (see list of record types attached) followed by brief summary of match, which consists of

          • FOLIO record type (row 14 in sample data)

          • Centered dot

          • Match field from incoming record (row 16 or 20 in sample data)

          • Right arrow

          • Field label for FOLIO record field being matched to (row 31, 35, or 36 in sample data)

          • NOTE: make sure the arrow and construction will reformat properly when screen changes from LTR to RTL (use Arabic localization setting to check)

        • Tag icon followed by tags; multiple tags are separated by comma [space], e,g. first, second, third (row 11 in sample data)

        • Edit pencil icon followed by most recent update date (row 4 in sample data)

        • User icon followed by most recent updater's name (firstname lastname) and username in parentheses, e.g. John Doe (johndoe) (row 5 in sample data)

      • 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

    • Include standard automated testing coverage; add screenshot or other details to confirm test coverage is in place

NOTES

Environment

None

Potential Workaround

None

Attachments

2

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie BreauxMay 20, 2019 at 6:22 AM
Edited

Hi All looks good, so I'm closing this story. One very minor bug (arrow showing next to the check box header) which I'll write up separately.

Ann-Marie BreauxMay 20, 2019 at 6:21 AM

Hi Are we in good shape with automated testing coverage? Is SonarCloud happy? Thank you!

Taras TkachenkoMay 15, 2019 at 9:22 AM

Hi yes it is.
I've left it in Code Review column due to environments problems yesterday that prevented us from newly created features deployment at that time.

Ann-Marie BreauxMay 15, 2019 at 7:44 AM

Hi This is the story you demo'd yesterday, right? It's still in Code Review status. Should it be In Review now?

Kateryna SenchenkoMay 2, 2019 at 3:13 PM

Thanks , it's clear now.

Done

Details

Assignee

Reporter

Tester Assignee

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created October 2, 2018 at 4:20 AM
Updated May 31, 2019 at 10:27 AM
Resolved May 20, 2019 at 6:22 AM
TestRail: Cases
TestRail: Runs