Overview: When a user has permission to create holdings/items for multiple member tenants, and is in Member tenant 1, but tries to create a holdings/item for Member tenant 2 without manually changing affiliations, they only see local data (like locations) for Member tenant 1, and the holdings/item is created in Member tenant 1

Steps to Reproduce:

1. Be sure user has permission to create/edit holdings and items for at least 2 member tenants

2. Log into a member tenant and go to Inventory

3. Find an existing shared instance

4. Display the details for that instance

5. View the consortial details

6. Click "Add holdings" button in the consortial accordion, not the one above it. That should take the user to a create holdings screen in Member tenant 2

7. View the list of locations in the permanent locations field and select one

8. Save the new holdings

9. View the new holdings details

Expected Results:

• When user clicks "Add holdings" in the consortial accordion, they are taken to a create holdings screen in Member tenant 2

• When the user views the Permanent locations dropdown list, it displays locations for Member tenant 2

• When the user saves the newly-created holdings

  • They are returned to member tenant 1 affiliation

  • There is a new holdings for member tenant 2 in the consortial holdings accordion

Actual Results:

• When user clicks "Add holdings" in the consortial accordion, they are taken to a create holdings screen in Member tenant 1

• When the user views the Permanent locations dropdown list, it displays locations for Member tenant 1

• When the user saves the newly-created holdings

  • They are in member tenant 1's affiliation (because they were never taken to member tenant 2)

  • There is a new holdings for member tenant 1 above the consortial holdings accordion

• Question for devs: Does it make a difference if the instance already has a holdings for Member tenant 1 or 2 (so already has a shadow instance in Member tenant 1 or 2's inventory-storage) or if the instance does NOT already have a holdings for member tenant 1 or 2 (so does not already have a shadow instance in Member tenant 1 or 2)?

Additional info

• See attached video (I'll attach after the environments become available again)

Testing notes
Make sure there are tests for the following consortial scenarios, if they don't already exist:

1. Member tenant 1: When a holdings for Member tenant 1 already exists on a shared instance, create holdings for Member tenant 2

2. Member tenant 1: When a holdings for Member tenant 1 does NOT already exist on a shared instance, create holdings for Member tenant 2

3. Member tenant 1: When an item for member tenant 1 already exists on a shared instance, create item for Member tenant 2

4. Member tenant 1: When an item for member tenant 1 does NOT already exist on a shared instance, create item for Member tenant 2

5. Member tenant 1: When a holdings for Member tenant 1 already exists on a shared instance, edit holdings for Member tenant 2

6. Member tenant 1: When a holdings for Member tenant 1 does NOT already exist on a shared instance, edit holdings for Member tenant 2

7. Member tenant 1: When an item for member tenant 1 already exists on a shared instance, edit item for Member tenant 2

8. Member tenant 1: When an item for member tenant 1 does NOT already exist on a shared instance, edit item for Member tenant 2