Staff Slips (UXPROD-19)

[UXPROD-1112] Staff Slips: Print Created: 14/Sep/18  Updated: 16/Sep/20  Resolved: 11/Jan/19

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

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Darcy Branchini
Resolution: Done Votes: 0
Labels: Q42018-will-split, printslips, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-248 Check-in: Print/reprint and send/rese... Closed
is blocked by UXPROD-111 CRUD Printing slips Closed
Relates
relates to FOLIO-1441 SPIKE: How to print slips? Closed
relates to UICHKIN-60 Print Transit Slip at Check-in Closed
relates to UXPROD-568 Requests - settings for automatic pri... Closed
relates to UXPROD-1077 Staff slips with custom triggers and ... Draft
relates to UICHKIN-16 Print Hold Slip at Check In Closed
relates to UICIRC-119 Change From/To Location Tokens in Tra... Closed
Epic Link: Staff Slips
Analysis Estimator: Darcy Branchini
Front End Estimate: Large < 10 days
Front End Estimator: Michal Kuklis
Back End Estimator: Cate Boerema (Inactive)
Estimation Notes and Assumptions: Triggering an automatic print from a browser might prove very difficult since for security reasons the browser probably doesn't have direct access to print function (at the operating system level).
Development Team: Prokopovych
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R2

 Description   

There are two major parts to staff slips:

  • CRUD the pre-defined slips and their templates (including in-transit and hold) in settings (covered in UXPROD-111 Closed )
  • Print slip on triggering set of events (i.e., check-in for an in-transit or hold slip) and conditions (the focus of this feature)

There has been extensive dialog about this feature on the story UICHKIN-16 Closed for reference.

Additional information:
A list of all slips - refer to SS https://docs.google.com/spreadsheets/d/1SwYo7TUszbkLc8b2QWqoZnEtTF3FdKjVohbALAYCqV8/edit#gid=0.
User defined triggers and conditions
Create a new slip
Delete a predefined slip
Defining printers for a given location



 Comments   
Comment by Cate Boerema (Inactive) [ 14/Sep/18 ]

This feature was split off from UXPROD-111 Closed which originally included both CRUD and printing for staff slips. When I did the split, I removed the XXL frontend and backend estimates, as I was initially thinking we should re-estimate. But, upon further reflection, I don't think they developers will be able to improve the estimates until after we have settled on an approach to printing (we have a spike for this decision). Given that, I replaced the XXL estimates for now.

Comment by Cate Boerema (Inactive) [ 28/Sep/18 ]

Hi Michal Kuklis and Marc Johnson, can you please update the estimates on this when you have the chance. The assumption is now that we are going with kiosk mode which, I understand, means there is no more back end work and only whatever frontend work is needed to adjust css once we start testing with receipt printers etc. Thanks!

Comment by Michal Kuklis [ 28/Sep/18 ]

Cate Boerema I just updated the front end part.

Comment by Cate Boerema (Inactive) [ 12/Oct/18 ]

Just changing the status on this feature to In Progress, Darcy Branchini, as I think you've written the stories and are just waiting for them to be completed and for the testing phase.

Comment by Cate Boerema (Inactive) [ 18/Oct/18 ]

Michal Kuklis and Darcy Branchini, the backend estimates look really high on this to me. Is there really so much backend work remaining? I thought we were just testing and changing css as-needed for receipt printers at this point. Am I right? If so, can we please modify the backend estimates accordingly? Thanks!

Comment by Michal Kuklis [ 18/Oct/18 ]

If the assumption is that we can use kiosk mode then I think the server side is not existing. I just updated the estimate for the backend.

Comment by Cate Boerema (Inactive) [ 06/Nov/18 ]

Darcy Branchini, I added the Q42018-will-split label to this feature, as I think there's a chance we may have to defer the transit slip story ( UICHKIN-60 Closed ) to Q1 (as it is blocked on UICHKIN-49 Closed and/or UICHKIN-17 Closed which are both blocked by a ton of backend work). Let me know if that doesn't make sense to you.

Comment by Cate Boerema (Inactive) [ 11/Jan/19 ]

Marking this closed since all the user stories it contains are complete. Darcy Branchini some aspects of this feature were not completed. You probably want to modify the description of this feature to include only those aspects that did get completed and create a split feature for the remaining work.

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