Overview: In the ECS environment, there are two issues:

1. The effective location facet in one tenant is not showing the locations of other tenants. The effective locations of other tenants should show in the facet in both Inventory search and browse. 

2. The Held-by facet is capping out at 9 locations even though the backend sends more in the response (not discovered in poppy bugfest ECS because there are not more than 9 locations) (new ticket: https://folio-org.atlassian.net/browse/UIIN-2730 )

Steps to Reproduce:

1. Log into into ECS Poppy bugfest environment 

2. Switch affiliation to University tenant 

3. Select "Yes" in the "Shared" facet

4. Identify a shared instance (such as HRID cenin00000480881) with holdings from College tenant - note the location of the holdings

5. Add holdings/item for University tenant in the "Film/Fiche" permanent location

6. Switch affiliation to the College tenant 

7. Search for the Shared instance 

8. Open the "Effective location (item)"

9. Search for the "Film/Fiche" location

Expected Results: Effective location from University should show in the facet

Actual Results: Only effective locations from the College tenant are showing in the facet

Additional Information:
URL: https://bugfest-poppy-consortium.int.aws.folio.org/inventory/view/d717299d-5d1f-5001-ac4d-8cd20b72d6ed?filters=tenantId.cs00000int_0005&query=cenin00000480881 

CSP Details:

1. Describe issue impact on business - Issue prevents ECS users from viewing other tenants in the Effective location (item) facet. Users need to be able to view other tenants in conjunction with the Held by facet to evaluate holdings at another member tenant. Without this fix, users will only be able to filter by their current tenant context's locations. 

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

3. What is the workaround if exists? No workaround

4. What areas will be impacted by fix (i.e. what areas need to be retested) Inventory search and find instance plugin. 

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high). Work is complete and the level of effort was medium. The technical risk is low.

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO. Test cases already exist and level of effort is 30 minutes.

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