Purpose: To include an option in the new service point page to flag a service point as a routing service point in an ECS environment using mod-tlr. A routing service point serves as an indicator within a circulation policy that a given item can circulate out of a data tenant. They are not used for check out, check in, or pickup locations.

User story statement(s):

As a library administrator of an ECS environment,
I want to set some service points as routing service points
so that they can be included in circulation policies and rules and help determine what can circulate out of a data tenant

Scenarios:

The following scenarios are true given an ECS environment only.

1. Scenario:

   • Given Settings > Tenant > Service points

   • When I select New

   • Then the New service point page opens

2. Scenario:

   • Given the New service point page

   • When I view it

   • Then I see the following fields that are blank or unchecked by default

     • Name* (required text field)

     • Code* (required text field)

     • Discovery display name* (required text field)

     • Description (text field)

     • Routing service point (Yes/No dropdown, No as default)

3. Scenario

   • Given the Routing service point dropdown

   • When “No” is selected

   • Then the following scenarios are true

4. Scenario

   • Given the New service point page

   • When I view it

   • Then I see the following fields that are blank or unchecked by default

     • Name* (required text field)

     • Code* (required text field)

     • Discovery display name* (required text field)

     • Description (text field)

     • Routing service point (Yes/No dropdown, No as default)

     • Shelving lag time (text field)

     • Pickup location (Yes/No dropdown, No as default)

5. Scenario

   • Given the New service point page

   • When I view it

   • Then after Pickup location I see the following, with all options checked by default

     • Print by default

       • Hold (check box)

       • Pick slip (check box)

       • Request delivery (check box)

       • Search slip (Hold requests) (check box)

       • Transit (check box)

6. Scenario

   • Given the New service point page

   • When I view it

   • Then after the Print by default options I see a new section called Assigned locations that is open by default

7. Scenario

   • Given Assigned locations

   • When there is no assigned location

   • Then the following text appears in gray “No locations found”

8. Scenario

   • Given Assigned locations

   • When there is an assigned location

   • Then the location name and code are listed below

9. Scenario

   • Given the Routing service point dropdown

   • When “Yes” is selected

   • Then I see the following fields

     • Name* (required text field)

     • Code* (required text field)

     • Discovery display name* (required text field)

     • Description (text field)

     • Routing service point (“Yes” selected)

   • AND the remainder of the form seen when the Routing service point selection is “No” disappears.

10. Scenario

    • Given a named existing service point (Tenant > Service points > Service points > [Named existing service point])

    • When I select Edit

    • Then I see the Routing service point dropdown in the form as described in Scenario 4

11. Scenario

    • Given a named existing service point (Tenant > Service points > Service points > [Named existing service point])

    • When viewing the details of the Service point in the fourth (4th) pane,

    • If the Service point is a Routing service point, then I see the same fields as in Scenario 9,

    • And, if the Service point is not a Routing service point, then I see all other necessary fields, including any additional fields for if the Service point is also a pickup location.

Questions: Should a user be able to change a Routing service point from “Yes” to “No”, after it is already in use? Yes.

Notes: Routing service points will occur in data tenants where mod-tlr is not deployed

Service point schema was extended with a new boolean field - ecsRequestRouting.