Details
-
Story
-
Status: Closed (View Workflow)
-
P4
-
Resolution: Done
-
None
-
Volaris Sprint 118
-
13
-
Volaris
Description
Purpose:
In order to create local representations of items borrowed by FOLIO users from other INN-Reach agencies, FOLIO must create local instance, holdings, and item records. Holdings and item records require a permanent location to be set. This mapping indicates what FOLIO location should be associated with items from other agencies via INN-Reach central server by setting a default for each central server, an optional default for each local server, and optional locations for each agency hosted on another local server. When a Patron Hold is placed in FOLIO via INN-Reach, mod-inn-reach uses this configuration to assign a location to to the holdings and item records it creates to represent requested item in FOLIO.
User story statement(s):
As a FOLIO administrator with appropriate permissions, I want to manage the mapping of INN-Reach agencies hosted on other local servers to locations in FOLIO's location system so that items and holdings records can be properly associated with a location when created.
Scenarios:
MERGED with UIINREACH-8 and UIINREACH-9
- Scenario:
- Given at least one central server connection configuration has been created (
UIINREACH-7) - When I click on INN-Reach in Settings
- Then a "Circulation Settings" group is presented in the second pane, below the "General" with an "Agency to FOLIO Locations" option
- Given at least one central server connection configuration has been created (
- Scenario:
- Given the previous scenario
- When the user selects "Agency to FOLIO Locations"
- Then an "edit" pane with a "Select Central Server" pull-down menu at the top appears with an inactive "Save & close" button
- Scenario:
- Given scenario 2
- When the user selects a central server name from the list
- Then menus to select a default shelving location (library + location menus) is presented (required, see mockups) and the "Save & close" button is inactive
- Scenario
- Given the previous scenario
- When no configuration has been set for this central server
- Then the menus to select a default shelving location (library + location menus) are not set
- Scenario
- Given scenario 3
- When an existing configuration exists for the selected central server
- Then the menus to select a default shelving location (library + location menus) are set to the configured values
- Scenario
- Given scenarios 4 or 5
- When the default location is set for the central server
- Then a type-ahead select menu of local servers associated with the selected central server is presented and the "Save & close" button becomes active
- Scenario
- Given the menu of local servers
- When the user selects a local server from the list
- Then menus to select a local server default location (library + location menus) are presented (optional)
- Then a tabular list of agencies associated hosted on that local server (on the left) and folio locations (library + location) selection menus (on the right) is presented
- Scenario
- Given the previous scenario
- When there is more than one local server associated with the selected central server
- Then you can repeat scenario 5 for reach
- Scenario
- Given the desired mappings have been selected
- When the user clicks the "Save & close" button
- Then the form is submitted
- Scenario
- Given that the form is valid
- When the server returns success status
- Then a success toast is presented and the user remains on the edit screen but the "Save & close" button is inactive again
- Scenario:
- Given the scenarios in
UIINREACH-9 - When the user clicks "Save"
- Then the form performs local validation on the form before posting it to the API
- Given the scenarios in
- Scenario
- Given Scenario 11
- When the user attempts to save a form without the required fields
- Then the form is not posted and in-page errors are presented to the user with instruction on what fields are required
- Scenario
- Given Scenario 11
- When the user attempts to save a form with al required fields completed
- Then the form is posted to the backend API
- Scenario
- Given Scenario 13
- When the backend API returns a success status
- Then a success toast is presented that says "The INN-Reach Agency to FOLIO Location Mapping for <central server name> has been <created/updated> successfully"
- Scenario
- Given Scenario 13
- When the backend API returns an error
- Then an error toast is presented that says "There was a problem and your update was not saved: <error message and status code>
- Scenario
- Given an un-saved and modified form
- When the user clicks "Cancel" (or the "X" in the upper-left corner, if the create/edit screen is full-window)
- Then a standard modal asking if the user wishes to cancel and lose all changes or continue editing should be presented
- Scenario
- Given Scenario 16
- When the user selects "Keep editing"
- Then they are returned to the in-progress form
- Scenario
- Given Scenario 16
- When the user selects "Close without saving"
- Then the form is discarded and the user is returned to the pane listing central servers under "INN-Reach Agency to FOLIO Location Mapping" in the "Circulation Settings" group of INN-Reach settings
TestRail: Results
Attachments
Issue Links
- is required by
-
UIINREACH-44 Backend integration for INN-Reach Agency to FOLIO Location Mappings (INN-Reach Circulation Settings)
-
- Closed
-
- requires
-
MODINREACH-65 Create CRUD API(s) for Data Model to Store a Mapping of INN-Reach Agencies, Local Servers, and/or central servers to FOLIO Locations for Use with "Virtual Item Records" in FOLIO Inventory
-
- Closed
-
-
UIINREACH-8 INN-Reach Circulation Settings: Navigate to INN-Reach Agency to FOLIO Location Mappings
-
- Closed
-
-
UIINREACH-9 INN-Reach Circulation Settings: Configure INN-Reach Agency to FOLIO Location Mappings
-
- Closed
-