Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
EPAM BatchLoader Sprint 37
-
3
-
Folijet
Description
Purpose: Document the changes needed in the UI for various types of static value matches
As a staff person
I want to be able to use various kinds of static values 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://drive.google.com/open?id=1JDD1oKrNM3jRRj_NXJtqBJZAAImiQck-u3ZVH_t9X2E
Scenarios
- Scenario 1
- Given the Create/Edit screen for Match profiles
- When the Incoming record type = Static value - submatch only
- Then add a dropdown to the right of the match header, as indicated in the attached Static value - Text string and Dropdown.PNG with values of
- Text (make this the default)
- Number
- Date
- Date range
- Text (make this the default)
- Scenario 2
- Given the Create/Edit screen for Match profiles
- When the Incoming record type = Static value - submatch only
- And the user has selected Text
- Then display a text box
- And allow entry of letters, numbers, punctuation, etc
- Scenario 3
- Given the Create/Edit screen for Match profiles
- When the Incoming record type = Not applicable - match to static value
- And the user has selected Number
- Then display a text box
- And only allow entry of numbers and punctuation (no letters)
Not allowing decimals or commas; will write a separate bug for it
- See attached Static value - Number.PNG for an example
- Scenario 4
- Given the Create/Edit screen for Match profiles
- When the Incoming record type = Not applicable - match to static value
- And the user has selected Date
- Then display a box with ghost text YYYY-MM-DD
- And a date picker at the end of it
- See attached Static value - Single date.PNG for an example
- Scenario 5
- Given the Create/Edit screen for Match profiles
- When the Incoming record type = Not applicable - match to static value
- And the user has selected Date range
- Then display
- Text: From
- Followed by a box with ghost text YYYY-MM-DD and a date picker at the end of it
- Followed by text: To
- Followed by a box with ghost text YYYY-MM-DD and a date picker at the end of it
- Text: From
- See attached Static value - Date range.PNG for an example
- Scenario 6
- Given the match profile result list in Settings/Data import/Match profiles
- When a user clicks a match profile to display the View details screen
- The details section for a MARC-to-MARC match should appear as indicated in the above scenarios, except it is not editable
- Scenario 7
- Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot
See attached screenshots
TestRail: Results
Attachments
Issue Links
- defines
-
UIDATIMP-237 Data import settings page's 4rd pane for Match Profiles: Details section of Create/Edit Screen
-
- Closed
-
-
UXPROD-2208 Remaining Job and Match profile work, part 3
-
- Closed
-
- has to be done after
-
UIDATIMP-373 Data import settings page's 4th pane for Match Profiles: Create MARC records' match-to section
-
- Closed
-
- is blocked by
-
MODDICONV-109 Adjust staticValueDetail.json schema
-
- Closed
-
- relates to
-
MODDICORE-29 Support matching by STATIC_VALUE
-
- Closed
-
-
UIDATIMP-440 Can't use decimal in Static value number match
-
- Closed
-