Purpose: In a consortium environment, Instance records may be shared amongst the member institutions or restricted to a single member tenant. When editing Instances, FOLIO needs to distinguish whether an instance being edited is Local or Shared, since those options 1) require different user permissions and 2) the edited Instances are stored in different Inventory-storage modules and 3) shared Instances require updates to their shadow instances in member library tenants

As a staff person editing Inventory instances
I want to be able to distinguish between editing local and shared instances
So that shared instances can have tighter permissions, and so that FOLIO distinguishes the different data flows and storage for local/shared instances

Scenarios

1. Scenario 1 [no change]

   • Given the Action menu in the Inventory second pane

   • When the tenant is a non-consortial tenant

   • And a user has permission to edit Instances (UI permission: Inventory: View, create, edit instances)

   • Then display the edit action and permit the user to edit instances

2. Scenario 2

   • Given the Action menu option "Edit instance" in the Instance detail (third) pane

   • When the tenant is a Member library tenant

   • And the instance is local

   • And a user has permission to edit Instances (UI permission for Member library tenant: Inventory: View, create, edit instances)

   • Then display the edit action and permit the user to edit it

   • But do not permit the user to edit shared instances

3. Scenario 3

   • Given the Action menu option "Edit instance" in the Instance detail (third) pane

   • When the tenant is a Member library tenant

   • And the instance is shared

   • And a user has permission to edit shared Instances (UI permission for Central consortial tenant: Inventory: View, create, edit instances)

   • Then display the edit action and permit the user to edit it

4. Scenario 4

   • Given the Action menu option "Edit instance" in the Instance detail (third) pane

   • When the tenant is a Member library tenant

   • And a user is editing a shared instance

   • And the user saves their edits

   • Then change the text of the standard green success toast to read:

     • This shared instance has been saved centrally, and updates to associated member library records are in process. Changes in this copy of the instance may not appear immediately.

   • NOTE: Once the member library's shadow instance is updated (based on the changes to the central shared instance), if a member library user is still displaying the instance details on their screen, those updates should appear automatically, without the user having to manually refresh the screen.

5. Scenario 5

   • Given the Action menu option "Edit instance" in the Instance detail (third) pane

   • When the tenant is a Central consortial tenant

   • And the instance is shared (which all instances in the Central tenant will be)

   • And a user has permission to edit shared Instances (UI permission for Central consortial tenant: Inventory: View, create, edit instances)

   • Then display the edit action and permit the user to edit it

6. Scenario 6

   • Given the menu option "Edit instance" for a member library or non-consortial tenant

   • And a user selects that menu option, edits the instance, and saves it

   • And the instance is local

   • Then update the instance as usual

   • And save it in the local tenant's inventory-storage

7. Scenario 7

   • Given the menu option "Edit instance" for a member library or central consortial tenant

   • And a user selects that menu option, edits the instance, and saves it

   • And the instance is shared

   • Then update the shared instance

   • And save it in the Central consortial tenant's inventory-storage

   • And update any related shadow instances in the member library tenants

   • NOTE: See updated success toast wording for the shadow instances in scenario 4 above. Do not change the wording for the success toast in the central consortial tenant.

8. Scenario 8

   • Ensure automated testing coverage for this new code is 80% plus

Testing

1. Edit instance in non-consortial tenant

2. Edit local instance in member tenant

3. Edit shared instance in member tenant, and confirm success toast wording

4. Edit shared instance in central consortial tenant

5. And if no permission to edit, make sure the edit option does not appear