Staff Slips (UXPROD-19)

[UXPROD-1077] Staff slips with custom triggers and conditions Created: 31/Aug/18  Updated: 23/Feb/23

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

Type: New Feature Priority: P3
Reporter: Darcy Branchini Assignee: julie.bickle
Resolution: Unresolved Votes: 0
Labels: appreport, resourceaccess, staff_slip_other, staff_slips
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-111 CRUD Printing slips Closed
relates to UXPROD-1112 Staff Slips: Print Closed
Epic Link: Staff Slips
Front End Estimate: XL < 15 days
Back End Estimate: XXL < 30 days
Development Team: Volaris
Report ID (pre-May 2019): ID442; ID443; ID444; ID445
Report Contact(s):
Mike Paxton
Report Functional Area(s):
Resource Access
Kiwi Planning Points (DO NOT CHANGE): 5
PO Rank: 20
PO Ranking Note: During SIG discussion, it was decided that this could wait.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R2
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: Leipzig (Full TBD): R1
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R2

 Description   

Updated by Darcy Branchini to include all out-of-the-box staff slips on 9/28/2020.

To clarify, there are four out of the box slip types (hold slip, transit slip, pick slip and delivery slip) already built and their templates (copy and tokens) are already customizable using a rich-text editor. For each of these, the triggering events and conditions are hardcoded.

This feature would allow FOLIO admins to CRUD their own triggers and conditions. Questions:

  1. Are there more triggering events and/or conditions than the following?
    • Hold slip
      • Item status changes to awaiting pickup and it's at the patron's requested service point
    • Transit slip
      • Outstanding request exists and item scanned at a location other than the requested location
      • Item returned at a location other than the home location
      • Item needed for a staff workflow and item scanned at a location other than the needed for WF location
    • Pick slip - Available item requested for pickup, and needs to be pulled off of shelf
    • Delivery slip - Item requested for office delivery
  2. Are the triggering events the ones listed above, but the conditions need to be defined? For example, a tenant might need multiple hold slips because each location or service point wants to do them differently? Or perhaps the transit event is always that it needs to go to a different location, but the conditions that define which transit slip template is needed is separated by home, request and/or staff workflow?
  3. Need use cases for custom triggering events and conditions


 Comments   
Comment by Anya [ 29/Mar/19 ]

Comment from March meeting : It was thought that this was done...

Comment by Cate Boerema (Inactive) [ 17/May/19 ]

Anya we have two out-of-the-box staff slips: hold and transit and the text they contain is configurable. What this feature is about is the ability to configure a totally new kind of staff slip, specify how and when it should be triggered AND customize the text that appears. Do I have that right Darcy Branchini? I think perhaps this needs to be clarified in the feature. I am quite surprised by how many people say they need this for go live and I wonder if there is a misunderstanding.

Comment by Darcy Branchini [ 17/May/19 ]

Yes, that's right Cate Boerema. It would be similar to patron notices. I wonder if we should circle back to the RA SIG about this, but the sub-group thought this was a necessary feature. This spreadsheet - https://docs.google.com/spreadsheets/d/1SwYo7TUszbkLc8b2QWqoZnEtTF3FdKjVohbALAYCqV8/edit#gid=0 - contains the analysis done to date.

Comment by Cate Boerema (Inactive) [ 20/May/19 ]

Thanks Darcy Branchini. I think the way we want to phase this work is:

  • Phase 1: Out-of-the-box staff slips with customized text but hard coded triggers like Hold and Transit slips. Are there others hardcoded slips we need to create? If so, we should have a feature for each of them, IMO. BTW, there is already a feature for paging slips UXPROD-1280 Closed
  • Phase 2: Custom staff slips with customized text and custom triggers. That is the scope of this feature, as I understand it, and I think we need to make that more clear in the feature description. Maybe some use cases people have discussed for needing this? Seems to me more of a nice-to-have than a must-have so I think people may be misunderstanding this feature (as Anya did) when ranking.
Comment by Darcy Branchini [ 21/May/19 ]

Cate Boerema, it's my understanding that three out-of-the-box slips are needed: hold, page and transit. Transit might be for routing an item from one library to another because it was returned somewhere other than the effective location and/or needs to get to a requested pickup location for a request. The other type of function transit slips need to accommodate is for a staff workflow need, such as getting an item to the binding department or cataloguing department. I don't think the staff workflow need is covered with transit slips in FOLIO today. So maybe we need another feature for that? Do you agree?

You might be right about the custom staff slips, but we need to be able to ILL (0 to many depending on the institution), document delivery and/or rush notifies.

Comment by Cate Boerema (Inactive) [ 22/May/19 ]

Thanks for the clarification Darcy Branchini. Maybe the transit slip for staff workflows could be put in scope for Emma Boettcher's feature UXPROD-1530 Draft as it probably doesn't make sense to specify and develop it independently from the overall workflow.

So it seems we have:

  1. Out-of-the-box slips:
    • Hold - Done
    • Transit for request and reshelving - Done
    • Transit for staff workflows - UXPROD-1530 Draft ?
    • Paging request individual pick slips - UXPROD-1280 Closed
  2. Completely custom staff slips with customized text and custom triggers - This feature
Comment by David Bottorff [ 01/Jul/19 ]

Chicago can wait up to 1 year for this

Comment by Cate Boerema (Inactive) [ 02/Jul/19 ]

Removing Q3 2019 fix version based on outcome of discussion in yesterday's RA SIG re-ranking.

Comment by Darcy Branchini [ 02/Jul/19 ]

Changed Cornell's and TAMU's rankings to "can wait - up to 1 year" based on conversation during RA SIG on 7/1/2019.

Much of the discussion centered around workflow, and not developing this feature until a workflow engine (where setting up custom triggers and conditions would presumably be simpler) was complete.

Comment by Darcy Branchini [ 29/Sep/20 ]

David Bottorff and Kelly Drake, can either of you provide use cases for this feature?

Comment by Kelly Drake [ 30/Sep/20 ]

Hi Darcy Branchini. I can't remember when we ranked this, or what we were thinking but all current triggers and events meet our needs so I'll change the ranking to R4. Thank you for checking in.

Comment by Erin Nettifee [ 11/Nov/20 ]

Hi Darcy Branchini - there may be another use case in there for delivery slips for mail delivery (as opposed to office delivery.) E.g., for libraries with distance ed students where they mail library materials.

I could also see some potential uses for proxy notifications here - e.g., notify a person's proxy when a hold is ready rather than the person directly. But that is VERY nuanced and not a priority IMO.

I could also see a use case for temporarily disabling transit slips for specific locations. Say a library has water damage and is temporarily closed - being able to go in and say "for items that are going to location X, use this temporary language on the notice for two weeks and don't put it in transit" or something like that.

Comment by julie.bickle [ 21/Mar/22 ]

Use cases that could potentially be covered by this:
_ Show a requester's default delivery address on the pick slip.
_ Be able to generate a request delivery slip, regardless of whether the option "Delivery" is selected in Users.

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