View/Edit Transit Slip

Purpose: When an item is checked-in a one location, but it needs to be routed to another location, a staff slip should print automatically at check-in so the circulation desk user knows it needs to be routed to a different location. There are three use cases:

1. It's checked in at a location, and it was requested by another patron with a different pick-up location.
2. It's checked in at a location, and there's a staff workflow request on it (cataloguing, binding, repair, etc.).
3. It's checked in at a location that is NOT its home location.

Related Mockups are available here - https://drive.google.com/open?id=1IfG4_wx2YxSPPLnDn1PzQDOyXhA3nbw7

Scenarios

Scenario 1: (Mockup: 1 Starting Point.png)

• Given Settings > Circulation > Staff slips
• When options are displayed
• A list of slips will be shown with the RU (of CRUD) interface. List should include "hold" and "transit" slips at this point in time. Future development will include more.
  • Create/new is out of scope for this first pass, and delete will not be an option for predefined/out of the box slips. Instead of delete, administrators will be allowed to indicate whether a predefined slip is active or inactive.
  • Use same UX pattern seen in settings for other CRUD interfaces in settings.

Scenario 2: (Mockup: 2a View.png and 2b View.png)

• Given Settings > Circulation > Staff slips > Transit (view)
• When details are shown
• Then the following is shown as non-editable fields
  • Name
  • Active/Inactive status
  • Description
  • Toggle display with two modes is ideal:
    1. View with tokens (no HTML though).
    2. View with placeholder values for tokens (same as the preview modal)
    • Note: If only one view can be supported for v1, then a view with tokens (#1 above) is preferred.
  • And an edit button option is shown

Scenario 3: (Mockup: 3 Edit.png and 4 Edit - insert token.png)

• Given Settings > Circulation > Staff slips > Transit (edit)
• When edit form is shown
• Then the following is displayed as inputs/editable fields:
  • Title - (Not editable because it's a predefined/out of the box slip)
  • Active/Inactive - toggle (Required)
  • Description - text area (Optional)
  • Output/Display as a text area with a rich-text editor with ability to insert tokens (for field values) (Required)

Scenario 4: (Mockup: 3 Edit.png)

• Given rich-text editor
• When a user is defining and/or customizing the output or display of hold slip
• Then the following styling elements are available and displayed
  • Bold
  • Italic
  • Underline
  • Font size
  • Align left, center, right
  • Increase indent
  • Decrease indent
  • Insert token shown as {} for icon. If selected, show possible fields for tokens. Possible tokens for a transit slip include:
    • From location (where it's being checked-in)
    • To location or destination (where it's going to)
    • Needed for: (patron request or a particular workflow need, probably blank if use case #3 above)
    • Date (when it was checked-in/routed)
    • Item title
    • Item author(s)
    • Item barcode
    • Item call number
    • Request/transaction number
    • Staff slip name

Scenario 5: (Mockup: 5 Preview.png)

• Given Transit slip edit screen
• When the preview button is clicked
• Then the output for the transit slip is displayed as it would print using placeholder values for tokens (on a modal window)

Scenario 6: (Mockup: 5 Preview.png)

• Given Transit slip preview modal
• When the print icon is clicked
• Then the output for the transit slip is printed as it would print using placeholder values for tokens

Out of scope:

• Additional out-of-the-box or pre-defined slips
• User defined triggers and conditions
• Create a new custom slip
• Clone a slip and customize
• Delete a custom slip