/
FQM-Lists app: Requests

FQM-Lists app: Requests

  • Rough draft

    • Related to Vega feature UXPROD-5164: Lists: Requests - Add data and record types (Item level requests)In Refinement

    Points of Contact: @Anne Ekblad and @Thomas Trutt

    CC: @Kathleen Moore

    Use case (ideal format): Library needs to provide [data/records] for [data/module/functionality] limiting based on [data limiter]

    Additions currently in progress - Requested deadline: Thursday, April 2, 2026

    Example from Fees/Fines feature

    1. At the end of each semester, we need to get a list of all students who own more than $20 in fines to block them in Banner. I need to be able to limit the search by date (last semester only), by user type (students only) and by feeFineType (Late fee manual charge, Overdue and Manual fines). Also I need to be able to group the fines by user as some patrons could have more than one fine each less than $20.

    Fields to display: User.first_name, user.last_name, user.user_name, user.barcode, user.external_id, account.metadata.createDate, account.amount, account.balance, account.status, account.feeFineType, account.paymentStatus, account.feeFineOwner

    Queryable fields: feeFineType, remaining, metadata.createdDate, user.patronGroup.name, paymentStatus

    Please add use cases below this point.

    Note: It will be helpful to specify ILR, TLR or Both when adding Use cases.

    Queryable fields and Fields to display can be ignored. Please just provide a brief example of what you would like to query. Thank you!

    1. I would like to be able to compare item status and request status. This could be used to detect anomalies (such as the current Ramsons/Sunflower bug with statuses not in sync) and also to find requests not handled correctly. (Both ILR and TLR) /Marie, Chalmers

    2. I would like a list for requests due to be removed from holdshelf within a time period and at a specific pick up service point. (Both ILR and TLR). This could be used to plan staff time and also to bulk edit hold shelf expiration date, e.g. due to unforseen circumstances. /Marie, Chalmers

    3. To see the need of additional acquisitions for a title, I would like a to get a list of open requests at an instance (Both ILR and TLR) and the number of items on the instance. (In addition, it would be great to also quickly the item statuses to determine if any of them are missing, lost etc.) /Marie, Chalmers

    4. For analytics purposes, I can see many use cases where I would like to lists requests by request type - request status - time period - pick up service point - retreival service point/holdings location/effectice call number. Preferably in combination with patron user group and cancellation reason. (Both ILR and TLR) /Marie, Chalmers

    5. Be able to find requests that are “stuck” on items and cannot be expected to progress because of item status or other factors. For example missing, aged to lost, etc. It would allow staff to identify these stuck requests and resolve them. (ILR and TLR) /Magnus
      Queryable fields: Item status, material type, request status, request type, request level, ??

    6. I want to be able to list open and closed requests that may not have been processed correctly. This will help me identify anomalies and gather data for statistical analysis. I would need to list requests by request type, request status, time period, pickup service point, and effective call number (ILR). /Sandra, NLS

    7. I want to be able to list all open requests that are set to expire from the holdshelf within a specific time period and at a particular pickup location (ILR). This would help me to manage holds more easily./Sandra, NLS

    8. A list of titles requested for a specific time period. The output should include data like: title, ISN, publication year, supplying library, pick up library. Anything that would be useful to get an idea if we should purchase a title or flesh out a collection. For statistics, I’d probably limit mostly by date range, but would want a lot of output options: supplying library, pick up library, an indicator of status (if the hold was fulfilled, cancelled, or expired), title, ISN, OpenRS instance UUID or other identifier (while I’m asking for the moon), and probably some more that don’t come to mind right now. (ILR and TLR) /Jacob, MOBIUS on behalf of Tom, Missouri State Library

    9. Hi! Here are some examples of visualizations I would like to make if I could run the queries in Lists. Thanks! Monthly request totals x Pickup service point - Request totals in date range x Status - Request totals in date range x Call number - Request totals in date range x Patron group - Cancellation reason totals x Retrieval service point (ILR and TLR) /Jacob, MOBIUS on behalf of Rachel William Woods University