Allow printing slips for Requests (Holds) - Item level
Description
Priority
Fix versions
Development Team
Assignee
Solution Architect
Parent
Parent Field Value
Parent Status
Attachments
- 27 Oct 2023, 11:20 AM
- 27 Oct 2023, 11:20 AM
- 27 Oct 2023, 11:20 AM
- 27 Oct 2023, 11:20 AM
- 27 Oct 2023, 11:20 AM
- 27 Oct 2023, 11:20 AM
- 27 Oct 2023, 11:20 AM
is cloned by
is defined by
is required by
relates to
requires
Confluence content
Checklist
hideTestRail: Results
Activity
Anne EkbladMay 9, 2024 at 1:35 PM
Hi, @Oleksandr Hrusha . Can you please ensure that the test cases for https://folio-org.atlassian.net/browse/UXPROD-4047 reflect Item level Holds only?
Thomas TruttMarch 9, 2023 at 9:01 PM
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.
(OLD ACCOUNT) Erin NettifeeFebruary 14, 2023 at 4:38 PMEdited
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.
Current situation or problem: FOLIO needs to have the ability to print slips for Holds requests. This feature focuses on Item level requests.
Added Sept. 4, 2024: Should work with both ECS and Single tenant environments.
UXPROD-4831 (Allow printing slips for Requests (Holds) - Title level (TLR) will be available in R release.
Scenarios for printing slips:
Request meets the following criteria: is Hold (Item level), is Open - Not yet filled
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 (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 (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 Item level Hold requests with status = Open - Not yet filled that are for that retrieval service point.
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 the status (this figure includes both Item level requests and Title level requests).
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