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

Paging Requests Individual Staff Slip

    XMLWordPrintable

    Details

    • Template:
    • Potential Workaround:
      Hide
      Darcy
      - UXPROD-923 Requests in-app report: Requests Pick List, but that feature also tags this feature as a possible work-around. I'm ranking it higher assuming this one will be implemented and UXPROD-923 will not.
      Show
      Darcy - UXPROD-923 Requests in-app report: Requests Pick List, but that feature also tags this feature as a possible work-around. I'm ranking it higher assuming this one will be implemented and UXPROD-923 will not.
    • Epic Link:
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      Large < 10 days
    • Development Team:
      Vega
    • Calculated Total Rank:
      101
    • PO Rank:
      91
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R2
    • 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):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      Purpose/Problem:
      Paging requests are requests on items that are available in the library. To fulfill these types of requests, library staff need to print the list of open paging requests and go get the items off the shelf. Many institutions print a single report for this purpose (see UXPROD-1138 and UXPROD-923) but some want the option to print individual slips instead. NOTE: The report might be an acceptable work-around temporarily until this feature can be developed.

      1. Some libraries use an individual pick slip for retrieving an item from (closed) stacks and then place the same slip in the item on the collection shelf. The top printed line on the slip could provide a (pseudonymous) identification of the patron, that could stick out at the top for easy collection. The pick slip also serves as a paging slip in this case.
      2. Large closed stack libraries (Magazinbibliotheken) might want to aggregate pick slips for a certain period of time, sort them by call number and print them in a batch. This would provide one way of optimizing collection routes for staff.
      3. Other libraries want to have these slips print as a request comes in.
      4. Closed stack libraries might leave a copy of the loaned item call slip in the stack until the item is returned. This would require the system to print each call slip twice.

      Implementation Thoughts:

      • Setting to enable this option
      • Ability to CRUD the paging slip template, specifically the content and format (like hold slips)
      • Ability to print individual paging slips on demand and/or on a schedule
      • Ability to print only slips relevant to your location
      • Individual slips are properly sorted and collated (by location, call number, maybe even custom field - sort order should be configurable)

      Further use cases: (from Uschi Klute in comments below)
      In our larger libraries there are several closed stacks, each with its own printer. The slips automatically printed there belong to exactly this closed stacks area. In most libraries the books are picked "on demand" and not with a certain provision time.
      If an unexpectedly large amount of slips has been produced on a printer, it can easily be divided between two employees.
      For media which were not found in the shelf, a corresponding text can be noted on the slip. Those slips are collected at the service point and checked again at a later time.
      If the books are then transported to the service point, it is important that the request slip is in the book, as this is the only way for everyone involved to recognize that it is an ordered and already picked book.
      With a list, the status of the book (already picked or not found etc.) would have to be noted on the (paper) list.
      A list is very impractical and would cause much more work.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                dbranchini Darcy Branchini
                Reporter:
                cboerema Cate Boerema
                Front End Estimator:
                Kostyantyn Khodarev Kostyantyn Khodarev
                Back End Estimator:
                Kostyantyn Khodarev Kostyantyn Khodarev
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases