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

Requests: Paging requests (Basic)

    Details

    • Epic Link:
    • Analysis Estimate:
      Small < 3 days
    • Front End Estimate:
      Medium < 5 days
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      Includes the need to handle the impact of a request queue on item status when there isn't a loan
      This means that the transitions for a request can happen at any point for an item
      Assumes no changes to fulfilment of requests after creation
      Assumes states where creation are allowed are hard-coded for the scope of this feature
      Show
      Includes the need to handle the impact of a request queue on item status when there isn't a loan This means that the transitions for a request can happen at any point for an item Assumes no changes to fulfilment of requests after creation Assumes states where creation are allowed are hard-coded for the scope of this feature
    • 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 paging requests (requests for not-checked-out items to be retrieved from stacks by staff and either placed on pickup shelf or delivered), including:

      • Staff slips (covered in UXPROD-1280) and notices to the patron (covered in UXPROD-18)
      • Service points that will be responsible for retrieving items
      • In app reports/list exports Covered in UXPROD-1138, UXPROD-923 and UXPROD-1280
      • Closing of the request
      • Alerts at checkin, checkout and renewal that an item is wanted for a Paging request

        Attachments

          Issue Links

            Expenses

              Activity

              Hide
              cboerema Cate Boerema added a comment - - edited

              There are some questions we still need to answer (with SIG) about this feature:

              1. Are paging requests really needed if FOLIO supports the ability to configure which item states holds can be put on? This configurability is something we have been told we must absolutely have. If the only difference between a hold and a page is the item states on which they are allowed, I am not sure both are necessary
              2. Also, it seems that paging requests are not really any different from recalls and holds vis-a-vis how fulfillment is handled. Therefore, if we do go ahead with this feature, much of what is needed will already have been covered by UXPROD-118.

              Given the remaining uncertainty and the fact that the development scope on this is smaller than originally thought, I think it makes sense to move this out of Q4 and into Q1 2019.

              Show
              cboerema Cate Boerema added a comment - - edited There are some questions we still need to answer (with SIG) about this feature: Are paging requests really needed if FOLIO supports the ability to configure which item states holds can be put on? This configurability is something we have been told we must absolutely have. If the only difference between a hold and a page is the item states on which they are allowed, I am not sure both are necessary Also, it seems that paging requests are not really any different from recalls and holds vis-a-vis how fulfillment is handled. Therefore, if we do go ahead with this feature, much of what is needed will already have been covered by UXPROD-118 . Given the remaining uncertainty and the fact that the development scope on this is smaller than originally thought, I think it makes sense to move this out of Q4 and into Q1 2019.
              Hide
              marcjohnson Marc Johnson added a comment - - edited

              Cate Boerema Tania Fersenheim at the moment, I believe it is only possible to create hold requests when an item is Checked out. (Changing this may impact the scenarios for check in and check out of items when looking at the request queue)

              Which issues cover the configurable restriction on item status of hold requests?

              Show
              marcjohnson Marc Johnson added a comment - - edited Cate Boerema Tania Fersenheim at the moment, I believe it is only possible to create hold requests when an item is Checked out . (Changing this may impact the scenarios for check in and check out of items when looking at the request queue) Which issues cover the configurable restriction on item status of hold requests?
              Hide
              cboerema Cate Boerema added a comment - - edited

              Which issues cover the configurable restriction on item status of hold requests?

              Hi Marc Johnson. There isn't a feature for that yet (just learned of it recently). I can put something in the backlog: UXPROD-1320

              Show
              cboerema Cate Boerema added a comment - - edited Which issues cover the configurable restriction on item status of hold requests? Hi Marc Johnson . There isn't a feature for that yet (just learned of it recently). I can put something in the backlog: UXPROD-1320
              Hide
              marcjohnson Marc Johnson added a comment - - edited

              Cate Boerema That's all good, I just wondered if I missed something. Please, don't raise anything prematurely on my behalf. I'm just curious (and now I know I can defer thinking about it). Thank you.

              Show
              marcjohnson Marc Johnson added a comment - - edited Cate Boerema That's all good, I just wondered if I missed something. Please, don't raise anything prematurely on my behalf. I'm just curious (and now I know I can defer thinking about it). Thank you.
              Hide
              hkaplanian@ebsco.com Harry added a comment -

              Does this imply that a person that wants to place a hold must determine if the title is available 1st and then make a decision about placing a hold vs request?

              Show
              hkaplanian@ebsco.com Harry added a comment - Does this imply that a person that wants to place a hold must determine if the title is available 1st and then make a decision about placing a hold vs request?
              Hide
              Klute Uschi added a comment - - edited

              Harry not the patron, but FOLIO
              FOLIO should self-detect whether the item is

              • either on loan --> create hold request (perhaps incl. return request if desired by the library)
              • or available --> create paging request (incl. an automatically printed request slip)

              Usually these are functions from the discovery system. In our experience requests are only carried out by staff in exceptional cases.

              Indeed, I suppose that the staff user must distinguish between the two manifestations of an item (on loan/not on loan) and do the appropriate action.

              Show
              Klute Uschi added a comment - - edited Harry not the patron, but FOLIO FOLIO should self-detect whether the item is either on loan --> create hold request (perhaps incl. return request if desired by the library) or available --> create paging request (incl. an automatically printed request slip) Usually these are functions from the discovery system. In our experience requests are only carried out by staff in exceptional cases. Indeed, I suppose that the staff user must distinguish between the two manifestations of an item (on loan/not on loan) and do the appropriate action.
              Hide
              cboerema Cate Boerema added a comment - - edited

              Does this imply that a person that wants to place a hold must determine if the title is available 1st and then make a decision about placing a hold vs request?

              Harry, it depends. If there is only one type of request allowed per status, the system could make the determination, as Uschi suggested. But many institutions allow more than one type of request for, say, checked out items (i.e. recall, hold). In this case, the requester does need to specify the type of request they are making. This is not a big deal when you are talking about recalls vs holds because there are clear implications (do you need it right away or can you wait for it to be checked back in at the normal due date). With holds and pages it is really not clear why you would choose one over the other. Hence my first comment here - I need to revisit this topic with the SIG to determine if we really need paging requests if we make the allowed item states configurable.

              Show
              cboerema Cate Boerema added a comment - - edited Does this imply that a person that wants to place a hold must determine if the title is available 1st and then make a decision about placing a hold vs request? Harry , it depends. If there is only one type of request allowed per status, the system could make the determination, as Uschi suggested. But many institutions allow more than one type of request for, say, checked out items (i.e. recall, hold). In this case, the requester does need to specify the type of request they are making. This is not a big deal when you are talking about recalls vs holds because there are clear implications (do you need it right away or can you wait for it to be checked back in at the normal due date). With holds and pages it is really not clear why you would choose one over the other. Hence my first comment here - I need to revisit this topic with the SIG to determine if we really need paging requests if we make the allowed item states configurable.
              Hide
              cboerema Cate Boerema added a comment -

              Okay, the SIG confirmed that paging requests are needed. Highlights from our discussion:

              • While request to status mapping must be configurable, most institutions won't allow hold requests on available items (UXPROD-1320)
              • For available items, they want to have a separate request type (paging request) so paging requests can have:
                • Different request policy rules
                • Different patron notices
                • Different system behavior, for example, related to impact of cancelling requests or automatic conversion of paging requests to ILL
              Show
              cboerema Cate Boerema added a comment - Okay, the SIG confirmed that paging requests are needed. Highlights from our discussion: While request to status mapping must be configurable, most institutions won't allow hold requests on available items ( UXPROD-1320 ) For available items, they want to have a separate request type (paging request) so paging requests can have: Different request policy rules Different patron notices Different system behavior, for example, related to impact of cancelling requests or automatic conversion of paging requests to ILL

                People

                • Assignee:
                  cboerema Cate Boerema
                  Reporter:
                  taniafersenheim Tania Fersenheim
                  Analysis Estimator:
                  Tania Fersenheim
                  Front End Estimator:
                  Matt Connolly
                  Back End Estimator:
                  Marc Johnson
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated: