Requests (UXPROD-790)

[UXPROD-1374] Get Hold Shelf Expiry Period from Service Point Created: 29/Nov/18  Updated: 02/Nov/22  Resolved: 10/Mar/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: Requests

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: v+v_candidate
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-1131 Request statuses "Closed - pickup exp... Closed
is blocked by UXPROD-118 Fulfill pickup requests Closed
Defines
is defined by MODUSERBL-67 Temporarily Allow Additional Properti... Closed
is defined by CIRC-194 Requests: Populate the Hold Shelf Exp... Closed
is defined by MODINVSTOR-251 Backend Work for UISP-7: Add Hold She... Closed
is defined by UIORG-143 Add Hold Shelf Expiry Period to Servi... Closed
is defined by UIREQ-206 Null Hold Shelf Expiration Results in... Closed
is defined by UIREQ-221 Display Hold Shelf Expiration Dates a... Closed
Epic Link: Requests
Front End Estimate: Medium < 5 days
Front End Estimator: Cate Boerema (Inactive)
Front-End Confidence factor: Medium
Back End Estimate: Large < 10 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: Includes adding the period interval and duration properties to a service point
Includes using period during check in
Assumes that repeated check in will reset the expiration to current date and time plus period (and overwrite any manual changes)

CB: I needed a frontend estimate for planning so I put 5 days on this feature. @michal, please adjust as needed.
Development Team: Prokopovych
Rank: Chalmers (Impl Aut 2019): R2
Rank: Chicago (MVP Sum 2020): R4
Rank: 5Colleges (Full Jul 2021): R2
Rank: GBV (MVP Sum 2020): R2

 Description   

Create a Hold shelf expiry setting in the service point form. When items become awaiting pickup for a request at a service point, FOLIO will look to this setting and populate the Hold Shelf expiration period in the request form (this field already exists, it's just being populated with some random date). The hold shelf expiration period can be manually changed after being set according to the SP defaults (edit capability is already in place). Hold shelf expiration date is already a token for the print slips. We need to make sure this date is populated in the print slips, as well.



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

Marc Johnson and Michal Kuklis, can you please estimate this feature?

Comment by Marc Johnson [ 04/Dec/18 ]

Cate Boerema Given that it is possible to repeatedly check an item in at a service point, what is the expected effect on the hold shelf expiry date?

Should it be reset to the current date and time plus the configured period, or not be changed? If it should be changed, then that might overwrite any manual changes that a user has made.

Comment by Cate Boerema (Inactive) [ 04/Dec/18 ]

Hi Marc Johnson. This is actually described in UICHKN-49 and UICHKN-50. The first time an item whose status is changing to Awaiting pickup is checked in, the hold shelf expiration date is set. Subsequent check ins that don't change the status from Awaiting pickup do not change the hold shelf expiration date.

The one weird use case is:

  • Item is checked in at pickup service point: Item status goes into Awaiting pickup and hold shelf expiration date is set.
  • Item is somehow misplaced and is checked in at another service point: Item status goes into In transit and hold shelf expiration date is cleared.

I think we can generalize logic needed for the the above use case with this statement: Any time an item is checked in and the status is changing to In Transit, the hold shelf expiration date is cleared or left blank.

Make sense?

Comment by Marc Johnson [ 04/Dec/18 ]

Cate Boerema Thanks.

Does that mean that this feature is dependent upon the feature UXPROD-118 Closed (that includes UICHKIN-49 Closed and UICHKIN-50 Closed )?

Comment by Marc Johnson [ 04/Dec/18 ]

Cate Boerema I took a look at the scenarios in those issues.

Scenario 3 of UICHKIN-50 Closed suggests that repeated check ins at the pickup service point should not change the expiry date. Is that the correct interpretation?

Comment by Cate Boerema (Inactive) [ 04/Dec/18 ]

Well, I guess it is now. I had originally put a temp story into UXPROD-118 Closed that said we should hard-code the hold shelf expiration date at today plus 14 so that we could test all the setting and clearing logic as part of those stories. But Jakub Skoczen didn't want to do this hardcoding as an interim solution. So I created this separate feature, reworked my story so it said to look to the service point for the expiration period and moved it into this feature.

All that is to say, I think you are right. This now blocks some of UXPROD-118 Closed . Two options:
1. We do this first and then turn to UXPROD-118 Closed
2. We remove the scenarios related to hold shelf expiration date setting from UICHKN-49 and UICHKN-50 and put them in a new story which we will include with this feature.

Do you have a preference?

Comment by Marc Johnson [ 04/Dec/18 ]

Cate Boerema I think I might be confused.

UICHKIN-49 Closed and UICHKIN-50 Closed appear to define setting the hold shelf expiration date as part of their scenarios. Those issues appear to be part of UXPROD-118 Closed .

If we want to keep UXPROD-118 Closed and this separate, then I think we need (your option 2) to separate out the scenarios from UICHKIN-49 Closed and UICHKIN-50 Closed .

Once that is done, I think we can choose which of these is higher priority to start first. To me, this would make UXPROD-118 Closed effectively be transit to pickup service point and this to be determine request hold shelf expiration. With the closely related partner feature UXPROD-1131 Closed being expire requests and hold shelf fulfilment (which would be blocked on this?)

Otherwise, I think the two features are effectively intertwined (and might as well subsume all of this into UXPROD-118 Closed ?).

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Michal Kuklis, can you please put in a frontend estimate for this? The 5 currently showing is just my best guess (I needed an estimate for planning). Thanks

Comment by Michal Kuklis [ 05/Dec/18 ]

Cate Boerema just a quick question about this. Is the UXPROD-1374 Closed just about adding this new expiry setting to the SP form? If so your estimate is good!

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Actually, Michal Kuklis, Marc Johnson suggested this feature should also cover populating the hold shelf expiration date on the request when it goes into awaiting pickup. Given that, I have moved the story that covers that functionality ( CIRC-194 Closed ) out of UXPROD-118 Closed and into this one. I don't think CIRC-194 Closed has much, if any UI. That said, it would be great if you could both revisit the estimates in case this impacts. Thanks!!

Comment by Michal Kuklis [ 06/Dec/18 ]

Sounds good Cate Boerema. I think Medium for front end is reasonable here.

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