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:

• "View holdings" button should only be active for user if they have Inventory permission to at least view holdings for the specific member tenant that the holdings is associated with

  • Inventory permissions that allow View holdings for a member tenant

    • Inventory: All permissions

    • Inventory: View instances, holdings, and items

    • Inventory: View, create instances

    • Inventory: View, create holdings

    • Inventory: View, create items

    • Inventory: View, create, edit instances

    • Inventory: View, create, edit holdings

    • Inventory: View, create, edit items

    • Inventory: View, create, edit, delete holdings

    • Inventory: View, create, edit, delete items

  • For users that do not have at least Inventory permission to view holdings for the specific member tenant that the holdings is associated with, then the "View holdings" button should be suppressed

• "Add item" button should only be active for user if they have Inventory permission to at least create items in the specific member tenant that the item is associated with

  • Inventory permissions that allow Add item for a member tenant

    • Inventory: All permissions

    • Inventory: View, create items

    • Inventory: View, create, edit items

    • Inventory: View, create, edit, delete items

  • For users that do not have at least Inventory permission to create items for the specific member tenant that the item is associated with, then the "Add item" button should be suppressed

• Item: barcode hyperlink should only be active for user if they have Inventory permission to at least view items for the specific member tenant that the item is associated with

  • For users that do not have at least Inventory permission to view items for the specific member tenant that the item is associated with, then the "Item barcode" should not be a hyperlink

  • Inventory permissions that allow View items for a member tenant

    • Inventory: All permissions

    • Inventory: View instances, holdings, and items

    • Inventory: View, create instances

    • Inventory: View, create holdings

    • Inventory: View, create items

    • Inventory: View, create, edit instances

    • Inventory: View, create, edit holdings

    • Inventory: View, create, edit items

    • Inventory: View, create, edit, delete holdings

    • Inventory: View, create, edit, delete items

• "Add holdings" button should only be active for user if they have Inventory permission to at least create holdings in the specific member tenant that the holdings is associated with

  • Inventory permissions that allow Add holdings for a member tenant

    • Inventory: All permissions

    • Inventory: View, create holdings

    • Inventory: View, create, edit holdings

    • Inventory: View, create, edit, delete holdings

  • For users that do not have at least Inventory permission to create holdings for the specific member tenant that the holdings is associated with, then the "Add holdings" button should be suppressed

Scenarios:

1. Scenario 1 "View holdings" without permissions:

   • Given a member library sub-accordion in the Consortial accordion

   • And the user is NOT affiliated with the member library tenant OR the user does NOT have permission to View holdings for the member library tenant

   • When the user opens the holdings sub-accordion under the Tenant name

   • Then the "View holdings" button should be suppressed, so that the user cannot view the holdings details for that other member library

   • NOTE: This applies to the consortial central tenant and all member library tenants

2. Scenario 2 "Add items" without permissions:

   • Given a member library sub-accordion in the Consortial accordion

   • And the user is NOT affiliated with the member library tenant OR the user does not have permission to Create items for the member library tenant

   • When the user opens the holdings sub-accordion under the Tenant name

   • Then the "Add item" button should be suppressed, so that the user cannot create a new item record for that other member library

   • NOTE: This applies to member library tenants; central consortial tenant behavior is handled in UIIN-2523

3. Scenario 3 Item barcode: hyperlink without permissions:

   • Given a member library sub-accordion in the Consortial accordion

   • And the user is NOT affiliated with the member library tenant OR the user does not have permission to View items for the member library tenant

   • When the user opens the holdings sub-accordion under the Tenant name

   • Then "Item: barcode" data should not appear as a hyperlink, so that the user cannot view the item record details for that other member library

   • NOTE: This applies to the consortial central tenant and all member library tenants

4. Scenario 4 "Add holdings button" without permissions

   • Given a member library sub-accordion in the Consortial accordion

   • And the user is NOT affiliated with the member library tenant OR the user does not have the permissions to Create holdings for the member library tenant

   • When the user opens the holdings sub-accordion under the Tenant name

   • Then the "Add holdings" button should be suppressed, so that the user cannot create holdings for that other member library

   • NOTE: This applies to member library tenants; central consortial tenant behavior is handled in UIIN-2523

5.  Scenario 5 "View holdings" with permissions:

   • Given a member library sub-accordion in the Consortial accordion

   • And the user is affiliated with the member library tenant AND the user has the permissions to View holdings for that member library

   • When the user opens the holdings sub-accordion under the Tenant name

   • Then the "View holdings" button should be active

   • NOTE: This applies to the consortial central tenant and all member library tenants

6.  Scenario 6- "View holdings" action

   • Given that the "View holdings" button is active in a holdings sub-accordion under the Tenant name in the Consortium accordion

   • And the user presses the "View holdings" button

   • Then display the holdings details for that member library

   • Discuss: User should not have to manually change affiliation to see the other member library's holdings, but the system can change the affiliation automatically for the user

7. Scenario 7 "Add items" with permissions:

   • Given a member library sub-accordion in the Consortial accordion

   • And the user is affiliated with the member library tenant AND the user has the permissions to Create items for that member library

   • When the user opens the holdings sub-accordion under the Tenant name

   • Then the "Add item" button should be active

   • NOTE: This applies to member library tenants; central consortial tenant behavior is handled in UIIN-2523

8. Scenario 8 "Add items" action

   • Given a member library sub-accordion in the Consortial accordion

   • And the user presses the "Add items" button

   • Then display a new item screen for that member library

   • NOTE: User should not have to manually change affiliation to create the other member library's item, but the system can change the affiliation automatically for the user, including at the top of the detail pane, where affiliation is shown

   • NOTE: This applies to member library tenants; central consortial tenant behavior is handled in UIIN-2523{*}{*}

9. Scenario 9 Item barcode: hyperlink with permissions:

   • Given a member library sub-accordion in the Consortial accordion

   • And the user is affiliated with the member library tenant AND the user has the permissions to View items for that member library

   • When the user opens the holdings sub-accordion under the Tenant name

   • Then the hyperlink for "Item: barcode" should be active

   • NOTE: This applies to the consortial central tenant and all member library tenants

10. Scenario 10- Item barcode: hyperlink action

    • Given a member library sub-accordion in the Consortial accordion

    • And the user clicks the item barcode hyperlink

    • Then display the item record details for that member library

    • Discuss: User should not have to manually change affiliation to see the other member library's item record, but the system can change the affiliation automatically for the user

11. Scenario 11- "Add holdings" button with permissions

    • Given a member library sub-accordion in the Consortial accordion

    • And the user is affiliated with the member library tenant AND the user has the permissions to Create holdings for that member library

    • When the user opens the holdings sub-accordion under the Tenant name

    • Then the "Add holdings" button should be active

    • NOTE: This applies to member library tenants; central consortial tenant behavior is handled in UIIN-2523

12. Scenario 12- "Add holdings" button action

    • Given a member library sub-accordion in the Consortial accordion

    • And the user presses the "Add holdings button"

    • Then display a new holdings screen for that member library

    • NOTE: User should not have to change manually affiliation to create the other member library's holdings, but the system can change the affiliation automatically for the user, including at the top of the detail pane, where affiliation is shown

    • NOTE: This applies to member library tenants; central consortial tenant behavior is handled in UIIN-2523{*}{*}

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, these scenarios about user permissions and active/suppressed buttons and hyperlinks split from UIIN-2410

6. After refinement, scenarios for returning to the Instance from the holdings or item record were moved to a separate story, UIIN-2453

Testing

1. See each scenario above, plus

2. Confirm that permissions and actions for each of the 4 buttons/hyperlinks were not affected (still behave the same way) for holdings and items on instances in non-consortial tenants