Staff Slips (UXPROD-19)

[UXPROD-4047] Allow printing slips for Requests (Holds) Created: 08/Feb/23  Updated: 05/Feb/24  Resolved: 11/Jan/24

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Quesnelia (R1 2024)
Parent: Staff Slips

Type: New Feature Priority: P3
Reporter: Stephanie Buck Assignee: Anne Ekblad
Resolution: Done Votes: 0
Labels: IC_review, LC-priority2, acs, loc, requests_printing, requires-discussion
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File Print hold requests + disabled.JPG     JPEG File Print hold requests.JPG     JPEG File Print search slips.JPG     JPEG File Search slip (Hold requests) + Edit.JPG     JPEG File Search slip (Hold requests) + Token.JPG     JPEG File Search slip (Hold requests) + View.JPG     JPEG File Search slip (Hold requests).JPG    
Issue links:
Defines
is defined by CIRC-1933 Search slips endpoint implementation Closed
is defined by UIREQ-1042 Add okapi interfaces for search slips Closed
is defined by CIRC-1932 Search slips endpoint skeleton Closed
is defined by CIRCSTORE-465 Create new staff slip - Search Slip Closed
is defined by UICIRC-1000 Create a new Circulation setting Prin... Closed
is defined by UICIRC-1001 Create and Display new Staff slip (Se... Closed
is defined by UICIRC-1008 Create new Staff slip - Search slip (... Closed
is defined by UIREQ-1039 Request Action - Create new option "P... Closed
Relates
relates to UXPROD-4163 Find way to make TLR holds on instanc... Draft
relates to UXPROD-4404 Requests: Deter Duplicate Pick Slip P... Draft
Requires
requires UXPROD-3972 TLR: allow request on instance with n... Closed
is required by UXPROD-4057 Create request status: Open – Not on ... Draft
Release: Quesnelia (R1 2024)
Epic Link: Staff Slips
Front End Estimate: XL < 15 days
Front-End Confidence factor: 100%
Back End Estimate: XL < 15 days
Back-End Confidence factor: 90%
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R4

 Description   

Current situation or problem: FOLIO needs to have the ability to print slips for Holds requests.

Scenarios for printing slips:

  • Request meets the following criteria: is Hold (can be either Title or Item level), is Open - Not yet filled, is not located Offsite
  • Instance has an item that is requestable but isn't available

In scope

  • Enable printing slips for requests (Holds) at retrieval service points
  • Exclude Hold slip printing for Offsite - remote storage locations.
  • Solution should be configurable - not all institutions want this functionality

Out of scope

  • Hold slip printing for Offsite - remote storage locations.
  • Creation of additional pop-up modal that includes multiple options with various slips that can be generated and printed
  • Deter duplicate pick slip functionality - UXPROD-4404 Draft (Requests: Deter Duplicate Pick Slip Printing) planned for S release
    -Note: If library needs to print multiple copies of slips, printer settings can be used
  • Add additional User tokens to staff slips functionality - UXPROD-1830 Draft (Add additional USER tokens to staff slips) planned for S release

Use case(s)
A library has many copies of a title (instance) and holdings, but not all copies have been cataloged. When a patron needs an item from that instance, a slip needs to be printed so a staff member can go look for the item. If there is a holding associated with the instance then staff should always be able to print a slip as long as the item is not in remote storage.

Proposed solution/stories

New setting under Circulation > Requests > Print hold requests

  • When enabled, the following happens:
  • Print search slips for [insert service point here] appears in the Actions menu of the Requests app. This appears, regardless of which service point is selected and is specific to each service point.
  • When you click on this option, a PDF appears containing all the Hold requests with status = Open - Not yet filled that are for that retrieval service point.
  • If it's a TLR Hold, then no available item is tied to the request
  • If it's an ILR Hold, then an item is tied to the request.

PDF created from new staff slip:
Settings >> Circulation >> General >> Staff slips >> Search slip (Hold requests)

Notes

  • At any time, there can be approximately 40 requests with this status.

Questions

  • What location(s) will be used for printing? Retrieval service points not associated with Remote storage (e.g., similar to printing Pick slips)
  • What call number will be used for printing? 
  • How often is this done? Need to plan for up to multiple times an hour.

Possible Future enhancements

*Original Title and Context below - *

Original title - TLR: Allow printing pick slips for title level holds on instances with no (or incomplete) item records
Current situation or problem: FOLIO needs to have the ability to print pick slips for title level requests (holds) on instances with no item records. 

Scenarios for printing pick slips:

  • Instance has no items
  • Instance has an item but it is non pageable
  • Instance has an item that is requestable but isn't available

In scope

Setting: Ability to print pick slips for title level holds

Solution should be configurable - not all institutions want this functionality

Out of scope

Use case(s)

A library has many copies of a title (instance), but no copies (or not all copies) have been cataloged. Only an instance record exists. When a patron needs an item from that instance, a pick slip needs to be printed so a staff member can go look for the item. This library may have remote storage where all items have been cataloged. TLR holding pick slips would not be printed for this location if the item is not available. If there is a holding associated with the instance then staff should always be able to print a pick slip as long as the item is not remote.

Proposed solution/stories

  • Require a stub/dummy holding records for each instance (so a location can be associated with the title)
    • Create an interface to filter what's printed, like
      • slips with no items
      • print pick slips created since the last print
        • date/time filter
        • "new" slips
      • Slips for the holdings locations associated with the service point (where slips are printed from)
  • Enable printing pick slips for all title level requests
    • Service point configuration to either print or not print TLR pick slips - this could allow the user to 
      • have all regular pick slips for printing and pulling items
      • have remote storage never print
      • have two separate pick lists to print

Solution update 29 Aug 2023:

  • In LC, there should be at least a stub item record for copy 1 for all instance records pre-1999 in general collection stacks, and for new materials since then, also in general collection stacks. We suspect there may be a copy 2 (that needs to be looked for and added to the record). 
  • This stub record for copy 1 enables the page request workflow, but only for the first request
  • Once the (only) item record is paged, all subsequent requests will be placed as a hold
  • A daily export of title level request holds can be printed to enable retrieval staff to look for copy 2 

Links to additional info

Questions

  • Was in original wording "Instance has an item but it is non-pageable" - Is unclear.

Is this akin to "I want to be able to print a pick slip for any request?

*Fixed locations to be discussed later



 Comments   
Comment by Erin Nettifee [ 14/Feb/23 ]

I think this should come to RA for discussion - I don't think we should be trying to impose a workflow for something that doesn't yet exist on the current staff slip process (in this case, the item record doesn't exist, right?)

Instead, I would advocate for some sort of "instance slip" or even just a reporting tool that lets people get the information they need about title level requests that are in this limbo state, and then libraries can design their own local workflows for how they want to handle them at their institution.

Also, for the scenario where items are requestable but not available, some libraries don't want a pick slip to print because most of the time there is nothing on the shelf to go pick. If a library expects that there may still be copies that just haven't been cataloged but are there regardless, some sort of "instance slip" would let them manage that without requiring an enable/disable workflow within the existing staff slip process.

Comment by Thomas Trutt [ 09/Mar/23 ]

I would agree.. If pick slips where printed for materials with no item records it would just confuse staff and student employees (who do the majority of our processing). Instead i would advocate a ui notification to staff when they add an item to holding record. At that point i'd give them the option to print a page or routing slip. This of course does not work if items are batch loaded.

Generated at Fri Feb 09 00:36:50 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.