Uploaded image for project: 'ui-requests'
  1. ui-requests
  2. UIREQ-114

Export Requests search results to csv - additional data elements

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      Prokopovych

      Description

      Purpose: Users need to be able to export requests in CSV format in order to do more complex sorting and filtering, to use as a picklist for retrieving items from the shelves, to use as a list of requests that have expired and need to be removed from the hold shelf, etc.

      This story is to add several data elements that are visible on the Requests screen but not yet available to the API

      The additional data elements are:
      Request expiration date
      Contributor (formerly author)
      Call number
      Enumeration
      Copy number - spun off into UIREQ-136
      Item status - data in column is incorrect
      Current due date - data in column is incorrect
      (Number of) Requests - column doesn't exist, but we can wait for this if needed, see note below
      Requester Patron group - no data in column
      Pickup location - column exists but unable to test because perhaps can't assign a pickup location yet [Note: now called Pickup service point; still no data; should there be?]
      Delivery address - no data in column, but maybe OK?
      Requester's proxy name
      Requester's proxy barcode

      Scenarios

      1. Scenario
        • Given the Requests screen (the list that results from a search within the Requests app)
        • When at least one request is displayed
        • Display and activate the export function
      2. Scenario
        • Given the Requests screen (the list that results from a search within the Requests app)
        • When a user clicks export on the Requests (search results) screen
        • Then the following fields, populated as they are on the Request details page, are exported as CSV for each request:
          • Request type
          • Request status
          • Request expiration date*
          • Hold shelf expiration date
          • Position in queue
          • Item barcode
          • Title
          • Contributor (formerly author)
          • Shelving location (Effective Location)
          • Call number*
          • Enumeration*
          • Copy number (aka Piece identifier SPIN OFF TO A NEW STORY)* CB: Moved into UIREQ-136
          • Item status* Tania Fersenheim for the paged item, it is showing a status of checked out; this is a separate ticket now
          • Current due date*
          • (Number of) Requests* CB: Per Tania Fersenheim we can live without this for a while if it's going to have performance implications [not in the export - is this covered in another story now?]
          • Requester Name
          • Requester Barcode
          • Requester Patron group*
          • Request Fulfillment preference
          • Pickup service point (name not the ID)* (column exists but cannot test because we can't assign pickup service points yet)
          • Delivery address* - column exists; should there be data?
          • Requester's proxy name*
          • Requester's proxy barcode*
      3. Scenario
        • Given the Requests screen (the list that results from a search within the Requests app)
        • When a user clicks export on the Requests (search results) screen
        • Then the file will contain every field, even when no data is present for that field (e.g. a request with no proxy will have no Requester's proxy name or Requester's proxy barcode associated with it)
      4. Scenario
        • Given the Requests screen (the list that results from a search within the Requests app)
        • When a user has filtered the list of requests
        • Then the exported csv will contain only the requests in the filtered results list

      Implementation note: While this story is specific to exporting requests, we will need the ability to export other types of lists as well in FOLIO (e.g. fees/fines, users, loans). Please consider implementing as a reusable component.

        TestRail: Results

          Attachments

          1. deliveryaddress.PNG
            deliveryaddress.PNG
            10 kB
          2. example-request-export.csv
            1 kB
          3. example-request-records.json
            6 kB
          4. example-requests.json
            10 kB
          5. export (6).csv
            2 kB
          6. ItemData_full_0810.png
            ItemData_full_0810.png
            241 kB
          7. PageRequestStatusBug.mp4
            4.31 MB
          8. Requests11.1.csv
            3 kB
          9. screenshot-1.png
            screenshot-1.png
            108 kB
          10. screenshot-2.png
            screenshot-2.png
            123 kB
          11. Skärmavbild 2018-10-05 kl. 13.09.59.png
            Skärmavbild 2018-10-05 kl. 13.09.59.png
            169 kB
          12. Skärmavbild 2018-10-15 kl. 13.50.10.png
            Skärmavbild 2018-10-15 kl. 13.50.10.png
            93 kB
          13. Skärmavbild 2018-10-15 kl. 14.48.31.png
            Skärmavbild 2018-10-15 kl. 14.48.31.png
            114 kB

            Issue Links

              Activity

                People

                Assignee:
                adityamatukumalli Aditya matukumalli
                Reporter:
                taniafersenheim Tania Fersenheim
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases