Staff Slips (UXPROD-19)

[UXPROD-3481] Wrong slips are being inserted in items which requires redirection of the items Created: 07/Jan/22  Updated: 20/Sep/22  Resolved: 20/Sep/22

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

Type: New Feature Priority: P2
Reporter: Holly Mistlebauer Assignee: julie.bickle
Resolution: Won't Do Votes: 0
Labels: cornell-access-services, cornell-priority, staff_slips
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3480 Showing the print preview on slips re... Closed
is cloned by UXPROD-3482 Stop displaying reminder that patron ... Closed
Defines
is defined by UXPROD-3476 Update slip printing modal in FOLIO C... Draft
Epic Link: Staff Slips
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 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 #6 from that document and has a priority of HIGHEST PRIORITY.

Overview
Wrong slips are being inserted by the other libraries, which requires redirection of the items. This is due to human error. Most locations are staffed by students who work only a few hours a week and can’t be expected to be experts at this. The short-term solution is to have only well-trained staff process the items. A possible long-term solution is to use large icons on the print slips so that errors are more noticeable.

Contact(s)
Tom Trutt
Wendy Wilcox



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

Holly Mistlebauer, what exactly is the human error that is happening in this case?

What exactly is it that staff need to see better, in order to make sure they put each slip with its destined item? Which information is it? Which tokens?

You mention "large icons" - what would these icons represent?

Has Cornell made use of the current formatting options available for staff slips (e.g. font size, bold, underline), or tried other ways to highlight important information, e.g. ==> !! THIS IS IMPORTANT !! <==

Comment by Debra Howell [ 08/Feb/22 ]

Andy Horbal Thomas Trutt Please see Julie's comment above - if you would respond please?

Comment by Andy Horbal [ 09/Feb/22 ]

julie.bickle The human error happening in this case is that staff are inserting the wrong pre-printed routing slips into materials. In order to save paper and time, most of our service points have a supply of slips with the names of all our ~20 locations on them which they insert into books as an alternative to printing out a unique routing slip every time an item goes in transit. As described in Holly's "Cornell Access Services FOLIO Observations & Suggestions" report, we are finding that information about where an item is going isn't displayed prominently enough. We have indeed made use of the current formatting options available for staff slips: our "Transit" slip displays the item.toServicePoint token in the "HUGE" font size and bold, which is about as prominent as we can make it. My understanding is that the "large icons" suggestion originated with an observation that the slips are all text, and that maybe something which wasn't would stand out more.

I think it's important to note that the issue here isn't just or even mostly with staff slips: rather, we're trying to articulate a problem that our frontline staff have identified whereby the information FOLIO displays about where an item needs to be routed to is too hard to see, especially for student workers. Staff slips are one place where this is an issue, but the "In transit" pop-up in the Check in app is another, and maybe a more important one. We also definitely do see large icons as just one POSSIBLE solution: if there are other, better ways of addressing this issue, we'd be all ears!

Comment by Thomas Trutt [ 19/Sep/22 ]

julie.bickle would you like to close this issue and link it to UXPROD-3476 Draft ? I feel that issues would solve the root cause of this one. 

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

Doing UXPROD-3476 Draft fixes the root cause to this feature.

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

{}Doing UXPROD-3476 Draft fixes the root cause to this feature.

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