Purpose: To update the Data Import UI to accommodate multiple holdings and items being created and/or updated by importing individual MARC Bibliographic records

As a staff person working with Data Import
I want to see updated counts and outcomes in the data import UI log
So that I can confirm the results when multiple holdings and items are created and/or updated from individual imported MARC Bibs

Notes:

• Mockup log screens attached

• There's a separate story to change the word Discarded to No action. If you prefer to leave the value of Discarded in this story, that's fine

• Once this work is done, there should be no need for the value of Multiple in the log. Please ensure that it can never be assigned. Let A-M know if there should be a separate story or scenario for that

Scenarios

1. Scenario 1

   • Given the Data Import log summary

   • When viewing the holdings and item results

   • Then include counts for as many holdings and items were created, updated, no action, or errored, even if that count is higher than the number of SRS MARCs and Instances

2. Scenario 2

   • Given the Data Import log details

   • When multiple holdings and/or items are acted upon for one incoming MARC Bib record

   • Then include include as many rows as the highest number of records that were acted upon for that incoming record

     • Color them all the same shade as the first row for the incoming record, so that they appear to be grouped together

     • On the first row, have the info for the SRS MARC, Instance, first Holdings, and first Item

     • On the next row(s), have the info for any additional Items that belong to the first Holdings

     • Once finished with items for the first Holdings, on the next row, have the info for the next Holdings created/updated by the incoming record, and the first Item that belongs with it

     • On the next row(s), have the info for any additional Items that belong to the first Holdings

     • Etc - until all holdings and items acted upon by the incoming MARC Bib have been accounted for.

3. Scenario 3

   • Given the Data Import log details

   • When displaying details for the second MARC Bib in the incoming file

   • Then follow the same pattern as above, except all rows associated with the second record should be shaded the opposite color from the first record's rows

   • And continue the above pattern until all MARC Bibs in the incoming file have been accounted for

4. Scenario 4

   • Given the Data Import log details

   • When displaying errors for holdings or items

   • Then display the created/updated info for as many holdings/items as possible from the incoming MARC Bib and Error for any Holdings/Items whose work could not be completed. See attached mockups for examples

5. Scenario 5

   • Given the Data Import log details

   • When displaying the results for a Holdings

   • Then display the action as a hotlink (Created/Updated)

   • And display the Permanent Location code in parentheses to the right of the action

   • e.g Created (UC/HP/JRL/Gen)

   • Except if there is no permanent location code (in older logs), then only display the action (no empty parentheses afterwards)

   • NOTE: This format applies to all Holdings in all import logs as of Poppy, regardless of whether they relate to single or multiples

6. Scenario 6

   • Given the Data Import log details

   • When displaying the results for an Item

   • Then display the action as a hotlink (Created/Updated)

   • And display the Item HRID in parentheses to the right of the action

   • e.g Created (it12345)

   • NOTE: This format applies to all Items in all import logs as of Poppy, regardless of whether they relate to single or multiples

7. Scenario 7

   • Given the Data Import log details

   • When viewing older logs (for imports created before these log changes)

   • Then ensure there are no error messages or weird-looking UI display

   • NOTE: We cannot test this on Snapshot, since previous import jobs are cleared out every day. To test this, we'll need to do some imports on Folijet Rancher, then implement these changes, and then do some additional imports. When reviewing on Rancher, please add screenshot(s) to this Jira showing what the older logs look like after the changes are merged.

8. Scenario 8

   • Ensure automated testing coverage for this new code is 80% plus

QA notes

• This story needs a new TestRail for multiples

• Existing TestRails for logs need to be updated to match scenarios 5 and 6

Release notes
Indicate what happens with older logs; will display the Item HRID, but will not display the Holdings Perm Loc

UI notes
Make an additional request to fetch Holdings permanent location codes