Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1131

Request statuses "Closed - pickup expired" and "Closed - unfilled"

    Details

    • Epic Link:
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      Vega estimate - FE 3, BE XXL assumes scheduling is included
      -------------------------------------------
      Original estimate: FE 1, BE 15 (Matt and Marc)
      Show
      Vega estimate - FE 3, BE XXL assumes scheduling is included ------------------------------------------- Original estimate: FE 1, BE 15 (Matt and Marc)
    • Development Team:
      Vega
    • Rank: Chalmers:
      go-live
    • Rank: Chicago:
      go-live
    • Rank: Cornell:
      go-live
    • Rank: 5Colleges:
      go-live
    • Rank: Lehigh:
      go-live
    • Rank: TAMU:
      go-live
    • Rank: U of AL:
      go-live
    • Rank: Bremen:
      go-live

      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

        Attachments

          Issue Links

            Expenses

              Activity

              Hide
              cboerema Cate Boerema added a comment -

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

              Show
              cboerema Cate Boerema added a comment - Blocked on scheduler ( UXPROD-594 and FOLIO-1445 )
              Hide
              cboerema Cate Boerema added a comment -

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

              Show
              cboerema Cate Boerema added a comment - Marc Johnson and Matt Connolly , can you please estimate this feature? We need estimates for the capacity plan analysis. Thanks!
              Hide
              mattjlc Matt Connolly added a comment -

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

              Show
              mattjlc Matt Connolly added a comment - Hi, Cate Boerema ... I made an estimate based on the assumption that UIREQ-59 and UIREQ-128 cover all the work that needs to be done for this.
              Hide
              cboerema Cate Boerema added a comment -

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

              Show
              cboerema Cate Boerema added a comment - Removed scheduler blocker, as per Jakub, we won't need Scheduler.
              Hide
              cboerema Cate Boerema added a comment -

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

              Show
              cboerema Cate Boerema added a comment - Marc Johnson this seems to be missing the backend estimate. Can you please add?
              Hide
              marcjohnson Marc Johnson added a comment - - edited

              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?

              Show
              marcjohnson Marc Johnson added a comment - - edited 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?
              Hide
              marcjohnson Marc Johnson added a comment -

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

              Show
              marcjohnson Marc Johnson added a comment - Cate Boerema Given that this has changed to Vega, should I remove my estimate?
              Hide
              taniafersenheim Tania Fersenheim added a comment -

              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.

              Show
              taniafersenheim Tania Fersenheim added a comment - 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.

                People

                • Assignee:
                  cboerema Cate Boerema
                  Reporter:
                  taniafersenheim Tania Fersenheim
                  Front End Estimator:
                  Kostyantyn Khodarev
                  Back End Estimator:
                  Kostyantyn Khodarev
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated: