Check the linked tickets - if all is fine, can close this one too

Purpose: Confirm that the import log details display properly for import jobs in member tenants that include import work done in both the central and member tenant

As a staff person importing MARC Bibs in a member tenant
When the incoming MARC bibs update shared or local MARC bibs/instances
I want to see data for all the hotlinks in the import log
So that I can review the newly-imported data in Inventory and SRS

Scenarios

1. Scenario 1

   • Given a data import job in a member tenant that is doing the following

     • Updating a central shared SRS MARC and/or Instance

     • And/or Updating a local SRS MARC and/or Instance

     • Creating or updating the member's holdings

     • Creating or updating the member's items

     • Creating the member's orders

   • When viewing the log for the completed job

   • Then the user should see the following

     • Hotlinked titles for all successful imports in the job, that when clicked, show the following JSON data

       • MARC: JSON from central tenant for shared MARCs, or from member tenant for local MARCs

       • Instance: JSON from central tenant for shared Instances, or from member tenant for local Instances

         • NOTE: user should never see shadow instance JSON

       • Holdings: JSON from local tenant

       • Item: JSON from local tenant

       • Order: JSON from the local tenant

     • Updated hotlink for instance, that when clicked, takes the user to the instance view in the member tenant, and that instance view consists of

       • For shared instances: the central shared instance displayed in the member tenant, with the consortial accordion and its contents, but the specific member's holdings/items displaying separately, above the consortial tenant

       • For local instances: the local instance, with the specific member's holdings/items displaying (and no consortial accordion)

     • Created/updated hotlink for member library's holdings, that when clicked, takes the user to the detail view of the holdings record, in the member tenant

     • Created/updated hotlink for member library's item, that when clicked, takes the user to the detail view of the item record, in the member tenant

     • Created hotlink for member library's order, that when clicked, takes the user to the detail view of the order record, in the member tenant

For testing:
Test 1

1. Include instances that will match on 010, 1 representing a central instance and 1 representing a member instance

   • Add 590$a to the MARC Bibs "This is an update to a (shared or local) record"

2. Job profile

   • Match 010-010 or 010-LCCN (will it matter which one)?

   • If match, update instance (shared or local), create local holdings, create local item

     • Instance updates field mapping

       • Add an admin note based on mapping from a 590$a

       • Set a default status

     • Holdings field mapping

       • Set a default location

       • Set default call number type: Library of Congress

       • Call number mapping: 050$a " " 050$b

     • Item field mapping

       • Defaults for all required fields, no other info mapped

   • If no match, stop

3. Import the file

4. Check the log for each record from the incoming file

   • Counts in the top summary are correct

     • MARC: 2 updated

     • Instance: 2 updated

     • Holdings: 2 created

     • Item: 2 created

   • Instance title is a hotlink

     • Shows JSON data for SRS, Instance, Holdings, Item

   • Instance updated is a hotlink

     • Shows the shared instance data in the member tenant, with consortial holdings accordion, and member library's new holdings/item above the consortial accordion

   • Holdings created is a hotlink

     • Shows the newly-created holdings in the member tenant

   • Item created is a hotlink

     • Shows the newly-created item in the member tenant

Test 2: Same as above, but updating existing holdings/item for member library (so will need holdings/item match as well)

Test 3: Same as above, but creating a new open order for the member library, along with creating holdings and items