Staff Slips (UXPROD-19)

[UXPROD-3479] Printing the slips one-by-one slows down the process Created: 07/Jan/22  Updated: 23/Feb/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Staff Slips

Type: New Feature Priority: P3
Reporter: Holly Mistlebauer Assignee: julie.bickle
Resolution: Unresolved Votes: 0
Labels: cornell-access-services, staff_slip_printing, staff_slips
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-3480 Showing the print preview on slips re... Closed
Defines
is defined by UICIRC-818 SPIKE: Investigate customer requests ... Closed
is defined by UIBULKED-89 The name of previously uploaded file... Closed
Epic Link: Staff Slips
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R3

 Description   

Background
In mid-October 2021, Holly was asked by Cornell University Library to review various issues discovered by CUL Access Services staff while using FOLIO. Holly met with various individuals at Olin and Mann libraries and produced the CORNELL ACCESS SERVICES FOLIO OBSERVATIONS & SUGGESTIONS document, which is available at https://docs.google.com/document/d/1lwnZpkiw7G0c3EyObRRnjuV6XVMcFNK1lWUG952sFgI/edit?usp=sharing. This feature is ISSUE #4 from that document and has a priority of NOT AS IMPORTANT.

Overview
Add an option to queue up the print slips, allowing the user to decide whether or not to print them (like they are batched for the “Print pick slips” option). This would be an option in addition to printing the slips as is currently done.

Contact(s)
Tom Trutt
Wendy Wilcox



 Comments   
Comment by julie.bickle [ 08/Feb/22 ]

This request acutally is a requirement of  UXPROD-3480 .

Comment by julie.bickle [ 20/Jun/22 ]

After UICIRC-818 SPIKE:

The solution for this would probably be to print out all slips generated within a check in session.

BUT the main question is: Where do you store the data/ the slips?
_ Currently, this is handled by the UI, but if you have a lot of slips (e.g. over 1000), you end up waiting a long time, the browser could freeze, then the printing fails.
_ If you lose the browser session, where should the data be stored? Saving it locally is not safe.

Additional questions:
_ Does the business logic at check in have to change? E.g. you can currently check in an item several times. And what if the item is being worked on at the same time, how does that affect the slips?
_ This belongs to the larger topic of re-writing how we do/deliver reports, so that the user doesn’t have to wait for it to download from the browser, but that the report is available when it is ready. So ideally we wouldn’t work on this until this larger topic is solved. Maybe the epic UXPROD-867 Open is the place to start this conversation?

--> I suggest updating this as Blocked by UXPROD-867 Open .

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