Purpose: In a consortium environment, Instance records may contain holdings from multiple institutions and users from one library may need to evaluate materials that are held by different institutions. Users in a central consortial environment should be able to view holdings and items for all member libraries, and depending on permissions, also create and edit holdings and items. Users in a local member library should be able to view their own holdings and items first, followed by other consortial member library holdings and items.

Requirements:

• If Instance is Shared, add accordion under "Add holdings" button for "Consortial holdings"

  • Add sub-accordion for the tenant name (sorted in alphabetical order)

  • Add another sub-accordion for the holdings for each tenant

• All users should be able to see the holdings on the Instance record, regardless of affiliation

• "View holdings" button should only be active for users if they are affiliated with the member library to which the holdings are attributed

  • For users that are NOT affiliated with the member library to which the holdings are attributed, the "View holdings" button should be inactive/greyed out

• "Add item" AND Item: barcode hyperlink should only be active if users have permissions to create items in the specific tenant

  • For users that do NOT have the necessary permissions, the "Add item" button should be inactive/greyed out and the hyperlink should be inactive

• "Add holdings" button under the Tenant name accordion for each tenant

  • Active: User is affiliated with the tenant and has permissions to add holdings

  • Inactive: User is not affiliated with the tenant and/or does not have permissions to add holdings

Scenarios:

1. Scenario 1

   • Given a Shared Instance in a Consortial central tenant or a Local member tenant

   • When a user views the instance details

   • Then add a new accordion below the Local member tenant's holdings and above the Instance Administrative data accordion

     • Accordion name: Consortial holdings

     • Default to closed

2. Scenario 2

   • Given the Consortial holdings accordion

   • When the user opens the accordion

   • Then the user should see the holdings for all member libraries

     • Each member library is in a sub-accordion, defaulted to closed

     • The name of the sub-accordion is the member library name from the Consortial app membership name

     • The list of member libraries is in alphabetical order

     • Note: If a member library does not have holdings for that shared instance, the library does not appear in the Consortial accordion

3. Scenario 3

   • Given the Member library sub-accordion in the Consortial holdings accordion

   • When the user opens the member library sub-accordion

   • Then the user should see sub-sub-accordions for each holdings and items. Those sub-sub-accordions follow the standard display for holdings and items (same holdings, call number, item summary data, buttons, defaulted to closed)

     • Default all buttons/hyperlinks to enabled at the beginning; permissions will be addressed in a separate story

   • NOTE: pagination for lists of many items within 1 holdings. Per https://bugfest-orchid.int.aws.folio.org/inventory/view/a99fdd9c-40e0-4819-a524-11b585433946?query=in853166&sort=title and screenshots on , looks like the item limit is set to 200. to check the code

Notes

1. For shared instances in the consortial tenant, there is a consortial holdings accordion, but no local holdings/item information

2. For shared instances in a local member library tenant, there may or may not be local holdings/item information, but there is a consortial holdings accordion with other library holdings/item information

3. For local instances, there is no consortial holdings accordion

4. For non-consortial tenants, there is no consortial holdings accordion

5. After refinement, moved the button enable/disable based on user permissions scenarios to separate story UIIN-2452

6. After refinement, moved the behavior for returning to Instance view from Holdings/Item full screen to separate story UIIN-2453

Testing

1. See each scenario above

2. In consortial tenant, confirm there is only a consortial holdings accordion, no local holdings/items

3. In a non-consortial tenant (all existing production libraries), confirm that there is no consortial holdings accordion

During UAT determine whether there should be a expand all/collapse all button in the consortial accordion