Loans (UXPROD-788)

[UXPROD-3778] Add indicator to checkout screen when checkout due date is truncated Created: 08/Aug/22  Updated: 13/Feb/23  Resolved: 13/Feb/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Orchid (R1 2023)
Parent: Loans

Type: New Feature Priority: P3
Reporter: Molly Driscoll Assignee: Tim Auger
Resolution: Done Votes: 1
Labels: resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File 1-due-date-indicator.png     PNG File 2-due-date-indicator-hover.png     PNG File Screen Shot 2022-11-23 at 9.20.48 AM.png    
Issue links:
Defines
is defined by UICHKOUT-805 Checkout table usability improvements Closed
is defined by UICHKOUT-806 Visual indicator in checkout due date... Closed
is defined by UICHKOUT-809 Visual indicator in checkout due date... Closed
is defined by UICHKOUT-810 Visual indicator in checkout due date... Closed
Relates
relates to UICHKOUT-808 SPIKE: For UXPROD-3778 Closed
relates to CIRC-1653 UXPROD-3778 - Scenario 1 - Add indica... Closed
relates to CIRC-1654 UXPROD-3778 - Scenario 2 & 3 - Add in... Closed
Release: Orchid (R1 2023)
Epic Link: Loans
Front End Estimate: Large < 10 days
Front-End Confidence factor: 90%
Back End Estimate: XXL < 30 days
Back-End Confidence factor: 90%
Development Team: Volaris
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2
Solution Architect: Raman Auramau

 Description   

Purpose: A checkout's due date may be truncated in several circumstances:

  • Due to an expiration date on the user record
  • Due to a recall on the item being checked out
  • Due to a hold on the item being checked out

In these cases, it is helpful for staff to have a visual indicator of this behavior to address questions around why a due date is not assigned as anticipated.

User story statement(s):

As a circulation staff member,
I want a visual cue of a system-calculated due date adjustment or truncation
so that I can better explain why a due date was assigned that does not appear to comply with the expected due date in the loan policy.

Scenarios:

  1. Scenario:
    • Given an expiration date in the near future
    • When an item is checked out and has its due date truncated to the expiration date
    • Then show an indicator in the checkout response for the item - preferably an icon in a table column, not a pop-up
  2. Scenario:
    • Given an item with a hold request and a loan policy that truncates loan periods in this circumstance
    • When  an item is checked out and has its due date truncated according to the loan policy
    • Then show an indicator in the checkout response for the item - preferably an icon in a table column, not a pop-up
  3. Scenario:
    • Given an item with a recall request and a loan policy that truncates loan periods in this circumstance
    • When  an item is checked out and has its due date truncated according to the loan policy
    • Then show an indicator in the checkout response for the item - preferably an icon in a table column, not a pop-up

Additional information: Based on discussion at the 2022-08-08, this flag should be part of the checkout by barcode API so it would appear in FOLIO UI, while also being accessible to self-checkout. The group would prefer an icon on screen, rather than a pop-up. If a pop-up is necessary, it should be at the beginning of the session only, rather than on each checkout – similar to override behavior. Performance is a concern that should be considered in implementation.



 Comments   
Comment by Molly Driscoll [ 16/Aug/22 ]

Another discussion point that was raised at RA SIG and in subsequent discussions I've had with libraries is a configuration to allow a library to specify if the user expiration date should turn red or have some sort of visual indicator when within 'x' number of days of expiration.

Comment by Khalilah Gambrell [ 06/Sep/22 ]

Molly Driscoll and Cheryl Malmborg - has the UX design been discussed with Kimie yet? 

 

cc: Tim Auger 

Comment by Molly Driscoll [ 06/Sep/22 ]

Khalilah Gambrell not to my knowledge. This also relates to potential bugs around renewal behavior with a truncated due date. Cheryl Malmborg were you able to find Jiras for this or shall I file them?

 

Context for that: if a due date is truncated due to expiration, renewal of the item appears to succeed despite the due date not extending. Expected behavior is for the renewal to fail if the due date/time does not change.

Comment by Tim Auger [ 18/Sep/22 ]

In wait until Kimie has been consulted. After that, I can move this forward.

Comment by Tim Auger [ 29/Sep/22 ]

Hi Kimie Kester. Has anyone asked for your input about this issue? If not, I will setup a time for us to review. 

Comment by Tim Auger [ 03/Oct/22 ]

Kimie Kester  and I talked about the visual design. She will create a visual indicator and tool tip which contains "system-calculated due date adjustment" within the due date field where the adjustment is made. 

Comment by Kimie Kester [ 03/Oct/22 ]

Hi Tim Auger & Molly Driscoll Attached are two mocks. Let me know what you think of using the flag icon and also the generic hover text. Thanks!

If possible, could we ask the Devs to:

  1. make the column widths of the table on the right more responsive and based on a percentage, rather than an exact pixel width? Then when a title is long it will have more space and not wrap so many times onto multiple lines like it does today.
  2. adjusting the width of the columns will allow the heading of Due date not to wrap onto two lines as it does today.
  3. add a heading of Details to the column that has the ellipsis icon in it. I think this will make it a little better for accessibility.
Comment by Molly Driscoll [ 05/Oct/22 ]

Kimie Kester I think this looks great! Tim Auger I'd be happy to bring this back to the RA SIG for feedback, if you'd like.

Comment by Tim Auger [ 07/Oct/22 ]

Molly Driscoll Feel free to take it back to the RA SIG for feedback. But if not, that's okay too. I think Kimie has captured the need with her proposed UX design. 

Kimie Kester I will create a story that captures the additional three points above and get that addressed. Thank you for taking a wider usability lens to the total user experience.

Comment by Tim Auger [ 08/Nov/22 ]

Priyanka Terala Gurleen Kaur1 I realized when setting up one of the scenarios that there are multiple displays in circulation that need to be addressed. I will take note where they are located in this Jira.

Comment by Tim Auger [ 09/Nov/22 ]

Priyanka Terala Gurleen Kaur1 

Please take a look at the attached screen capture to see the condition (expiration date) and the resulting checkout date (which would normally be 21 days).

Comment by Priyanka Terala [ 11/Nov/22 ]

Tim Auger 
I have set up an item with two recall requests on MG bugfest - https://bugfest-mg.int.aws.folio.org/inventory/view/2e7be7d9-7b22-4637-b9c3-b63270e4f9e3/eab4abbc-ff07-44cc-8489-58f09db1b50e/937cd8b7-3339-46cc-93f1-679a84f02e32

Comment by Tim Auger [ 23/Nov/22 ]

Priyanka Terala sorry for missing this one. I'll look just after our meeting today

Comment by Tim Auger [ 23/Nov/22 ]

Priyanka Terala I must be going to the wrong instance record because the one the URL directs me to is this:

Comment by Khalilah Gambrell [ 02/Jan/23 ]

Hey Tim Auger. Will this feature be done for Orchid? If so, can you update Fix Version/s? 

Comment by Khalilah Gambrell [ 13/Feb/23 ]

Hey Tim Auger   - can this feature's status move to In Review or Closed?

Comment by Tim Auger [ 13/Feb/23 ]

all done!

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