Requests (UXPROD-790)

[UXPROD-1131] Request statuses "Closed - pickup expired" and "Closed - unfilled" Created: 21/Sep/18  Updated: 16/Sep/20  Resolved: 10/Mar/19

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

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

Issue links:
Blocks
is blocked by UXPROD-1374 Get Hold Shelf Expiry Period from Ser... Closed
Defines
is defined by CIRCSTORE-109 Implement request status "Closed - Pi... Closed
is defined by CIRCSTORE-110 Implement request status "Closed - Un... Closed
is defined by UIREQ-128 Add New Status Values to Requests Fil... Closed
Epic Link: Requests
Front End Estimate: Small < 3 days
Front End Estimator: Kostyantyn Khodarev
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Kostyantyn Khodarev
Estimation Notes and Assumptions: Vega estimate - FE 3, BE XXL assumes scheduling is included
-------------------------------------------
Original estimate: FE 1, BE 15 (Matt and Marc)
Development Team: Vega
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R2
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Purpose: Implement request statuses for requests that are closed due to expiration dates passing

"Closed - pickup expired" = a request that was held for a requester and the requester did not pickup the item before the Hold Shelf Expiration Date was reached
"Closed - unfilled" = a request that was not filled before the Request Expiration Date was reached



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

Blocked on scheduler ( UXPROD-594 Closed and FOLIO-1445 Open )

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

Marc Johnson and Matt Connolly, can you please estimate this feature? We need estimates for the capacity plan analysis. Thanks!

Comment by Matt Connolly [ 21/Nov/18 ]

Hi, Cate Boerema ... I made an estimate based on the assumption that CIRCSTORE-109 Closed and UIREQ-128 Closed cover all the work that needs to be done for this.

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

Removed scheduler blocker, as per Jakub, we won't need Scheduler.

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

Marc Johnson this seems to be missing the backend estimate. Can you please add?

Comment by Marc Johnson [ 04/Dec/18 ]

We briefly talked about this yesterday on the core team planning meeting.

The understanding I took away from that conversation was that this only affected the request record itself. Leaving the item status as Awaiting pickup for a hold shelf fulfilled request that expires on the hold shelf. This discrepancy would then be used by staff to identify the items to take off the hold shelf.

Tania Fersenheim Does that fit with your understanding?

How would we expect that the item status becomes available again (given we don't allow direct editing), via a check in?

What status would we expect the item to be when the request generally expires? Is this affected by where in the queue the request is?

Comment by Marc Johnson [ 04/Dec/18 ]

Cate Boerema Given that this has changed to Vega, should I remove my estimate?

Comment by Tania Fersenheim [ 04/Dec/18 ]

Marc Johnson
Yes that fits with my understanding.

Only the request record changes. Item statuses/states are unaffected by the expiration of the request itself or the hold shelf expiration date.
The status/state of the item would be updated by a staff person running it through Check In.
When the item is run through Check In we would expect FOLIO to make all the same checks it makes when an item that is "Checked out", or in any other status/state is checked in - check for pending requests and trigger them, send it in transit to go home, or whatever else is appropriate next status/state/destination for the item.

The status of the item when an "Open - awaiting pickup" request changes to "Closed - pickup expired" should be "Awaiting pickup" (otherwise we have a weird mismatch state that a staff person probably needs to resolve)

The status of the item when a request changes to "Closed - unfilled" could be anything, since only "Open - not yet filled" requests are changing to "Closed - unfilled." The item that was requested could be "Checked out" to someone, it could be Awaiting pickup for some other request, etc.

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