Overview: When shared instance have Member tenant 1 holdings and trying to look them on Member tenant 2, on which he have affiliation but don't have permissions, consortial member accordion is not displaying

Preconditions:

Shared instance with holdings from Member tenant 1 exists

User have following permissions:

Central tenant: "Inventory: all permissions"

Member tenant 1: No permissions

Member tenant 2: "Inventory: all permissions"

Steps to Reproduce:

1. Login on member tenant 2

2. Find and select the instance from precondition

3. Expand "Consortial holdings" accordion

Expected Results: Member tenant 1 consortial accordion is displayed, but user can't see the holdings of according member tenant

Actual Results: Consortial accordion is empty

Additional Information:
Reproduced on Folijet rancher, Sprint testing and Poppy Consortial Bugfest envs

See attached screenshot

Interested parties:

Critical service patch details

1. Describe issue impact on business - This ticket is aimed to update the way that Consortial Holdings are displayed in FOLIO ECS to better align with original expectations. Currently, users must have Affiliations with Member Tenants in order to see Consortial Holdings coming from the Member Tenants. This work will shift Consortial Holdings display to pull values from mod-search, rather than directly from each tenant so that all users can freely view Consortial Holdings without need for various Affiliations or Permissions.

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) - All ECS.

3. What is the workaround if exists? Only workaround would be to assign Affiliations for all Member Tenants to all Users, which would be cumbersome and tedious to maintain.

4. What areas will be impacted by fix (i.e. what areas need to be retested) - ui-inventory; “Consortial Holdings” accordion.

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high). - This work will shift Consortial Holdings display to pull values from mod-search, rather than directly from each tenant. Team Spitifre will be supporting this via .

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO.  - Low effort.

7. What is the roll back plan in case the fix does not work? Revert to previous version.