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

Requests in-app report: Requests Pick List

    XMLWordPrintable

Details

    • Hide
      Cate Boerema: Use the requests CSV export which has all the data needed by most institutions. OR, when we get UXPROD-1280 completed, that may be a preferred solution for some institutions. See comment below - it seemed at least a few institutions could live without this feature but the rankings haven't been updated.
      Show
      Cate Boerema: Use the requests CSV export which has all the data needed by most institutions. OR, when we get UXPROD-1280 completed, that may be a preferred solution for some institutions. See comment below - it seemed at least a few institutions could live without this feature but the rankings haven't been updated.
    • Medium < 5 days
    • Medium < 5 days
    • Low
    • XL < 15 days
    • estimates based on other appreport features
    • Vega
    • 74
    • Hide
      2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
      2019-07-12: Reduced rank relative to calculated because of the workarounds (see above)
      Show
      2020-10-04 - CB: Making my PO rank same as the calculated total rank for now. 2019-07-12: Reduced rank relative to calculated because of the workarounds (see above)
    • R4
    • R4
    • R4
    • R2
    • R4
    • R1
    • R2
    • R1
    • R1
    • R1
    • R2
    • R1
    • R1
    • R1
    • R2

    Description

      Purpose: Libraries that allow requests on not-checked-out items (e.g. Paging Requests, Remote Storage Requests, Resource Sharing Requests) will want to run a report periodically - at least daily and often multiple times per day, non-checked-out items that have been requested and need to be retrieved from the stacks by staff (paging requests, remote storage requests, resource sharing requests - any type that can be placed on not-checked-out items). The report will need to contain bib information, item call #, item location, item barcode, etc and be able to be limited to a service point's associated locations CB: Per RA SIG discussion on 2019-05-02, we do not need to limit by service point for location. Everyone preferred to be able to limit by Library.

      Output: Bib information, item call #, item location, item barcode, etc and be based on a service point's associated locations.

      Note:

      • The need for this report varies from institution to institution. Some institutions' workflow requires individual print/call slips in addition/instead: UXPROD-1280
      • Once UIREQ-262 (Add Library Column to Request CSV) is completed, most, if not all, of the data needed for this report is already included in the Requests app CSV export (see attached). So, in lieu of a purpose-built report, institutions could use the csv export as follows:
        • Use filters in FOLIO to limit to only requests where type = page and status = open-not yet filled
        • Export csv of search results
        • Filter csv export by Library to get those items you are responsible for picking up 2019-10-14 CB: Check in with SIG on this before developing because Darcy asked this same question for pick slips today and the SIG wanted those filtered by service point
        • Print csv export and pick up items on report
      • Follow up: Chalmers decided not to use the CSV export for their picklist and, instead, created a custom solution that would be worth looking at when designing this FOLIO report. See this comment for details: https://issues.folio.org/browse/CHAL-18?focusedCommentId=74386&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-74386

      TestRail: Results

        Attachments

          Issue Links

            is cloned by

            New Feature - New feature requests UXPROD-1138 Requests Pick List: CSV Export

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. UXPROD-867 Reporting: In-App Reports

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            New Feature - New feature requests UXPROD-1280 Paging Requests Individual Staff Slip

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                Unassigned Unassigned
                cboerema Cate Boerema
                Tania Fersenheim Tania Fersenheim
                Tania Fersenheim Tania Fersenheim
                Tania Fersenheim Tania Fersenheim
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases