Hide completed purchase requests from the Primo MyAccount
Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.
Thank you for posting this suggestion, we are considering the option to add a Request Type Filter to help users filtering requests by type (ILL, Purchase, Digitzation, Request ,… )
Jerry McCulley commented
Is there a way to add a field to identify campus location, course, professor, or submitter? Currently the blank patron request form is not very useful for us. We submitted a case#800907 for this and still waiting.
Benoît Vicart commented
In my opinion an opt in/opt out option in back office would be great and more flexible (for example by selecting in a list the status to display/hide). But I have no idea how complex it would be.
Alternatively, displaying only active requests by default (remain accross sessions) and offering a separate option "show rejected/cancelled requests" (like loan history button) would also be nice for me.
Anyway, thanks for the idea that we support actively!
Thanks for asking! We had a look at the new Request type filter in My Library Card (Primo February 2020 Release) that allows users to select one or more request types to filter requests based on the selected request types. We consider this as a nice new feature, but it does not meet our original expectations in my institution that came to create this idea.
An additional Status filter could maybe be interesting, but this would probably require an action from patrons who do not want to see completed/rejected/inactive requests. We would like to avoid patrons to systematically use such a filter to hide completed/rejected/inactive requests they don’t want to see. So, if a new Status filter could be (1) set by default to only display Active requests and (2) remain across sessions, that would be great.
Additionally, there could be other possibilities. For example:
(A) By providing the Purchase Request type and the Purchase Request status with specific IDs that libraries could use to hide by default any completed/rejected Purchase Request in My Library Card by using the Customization Package (CSS).
(B) By adding a new true/false setting in the Primo BO / Primo VE Discovery Configuration tables that would allow libraries to decide whether or not they want completed/rejected/inactive requests to be displayed in My Library Card.
Generally speaking, we are a bit confused here to see that Purchase Requests are not processed in the same way as the other requests (Hold, Digitization, Booking) that are not visible anymore in My Library Card once they have been completed or canceled. If you add a new Status filter, does that mean that all completed and canceled requests will suddenly become visible for patrons in My Library Card?
I appreciate your efforts to find a lasting solution to the situation.
As always, any comment or suggestion from the community would be most welcome!
I would like to know if in addition to the Request Type Filter a Status Filter is required
Thanks for the update, Nili. A Request Type Filter may be a good option in several cases.
I would like however to draw your attention to the current inconsistency in the MyAccount: Completed or Canceled ILL, Digitzation or Hold Requests are NEVER displayed in the MyAccount, only *Active* ILL, Digitzation and Hold Requests are, while Purchase Requests are ALWAYS displayed, whatever their status (Active, Completed or Canceled).
(1) Do you plan to display in the future all Requests, whatever their Status? -> Also completed and canceled requests would be displayed.
(2) Do you plan to add also a Status Filter? For example only Active Requests (whatever their Type) would be displayed by default.
Peta Hopkins commented
We allow our community to place purchase requests themselves without mediation by a librarian.
So most of them do not have lots or purchase requests to view in Primo which would be the case for librarians mediating requests.
I'd like to see completed purchase requests disappear from My Library Card either when the user "dismisses" them or after a configurable period of time eg. 365 days. This would help any users who want to revisit records of resources they requested.
Or some other mechanism that only shows recent requests, but allows the user to "Show All".
Stacey van Groll commented
For visibility in Primo, there are a couple of benefits that make it appreciated:
1. Some staff are more comfortable with the Primo UI, rather than certain aspects of Alma like Manage Purchase Requests facets, and they are already actively using Primo for many activities when they may also like to check on a past purchase request. The speed of being able to do so from within the UI they're already typically actively using, especially as some will have no need to log into Alma on many days, is also a plus
2. There is the Primo feature from Requests of being able to click on the title and go directly to the full record, which is a quick workflow to find the record in discovery, grab a permalink, etc. Although I have set up Analytics reports for purchases which include the URL to the Primo record both from within Analytics and after export, this does again require them to navigate to the report. If they, for example, get a query from a user about a purchase request submitted on their behalf, they can quickly go to Primo, Requests, find the title, click on the entry, and go from there.
These aspects will inevitably be particular to workflows of different sites. As an example, we mediate all purchase requests through liaison librarians rather than offering the option for users to submit requests directly, And we also choose to publish all orders straight away to Primo, rather than waiting for receipt, so that users can see that requests have been actioned and anticipate addition to the collection.
As such, the visibility for these librarians of all the resources they've requested directly in Primo is a positive experience.
I can understand that sites without these sort of workflows might wish to remove these entries for non library staff users, but it's important that changes to UI take all usage variations into consideration, hence my alternate suggestion.
There is also the following idea:
Sort purchase requests in Primo, by newest
@Stacey: Thanks for your comment and the link. I don't understand why Primo is so important. Wouldn't your librarians be happy if their purchase requests would rather be visible in *Alma*?
I wish it would be possible to hide completed/rejected purchase requests with the Customization Package (it would make me happy), but we have not been successful in achieving that. Any hint?
Stacey van Groll commented
Our librarians quite like that their purchase requests are visible in Primo.
Perhaps, instead of removing them, a dropdown option could be introduced to Requests for all Requests History, as there currently exists in Loans for Historic Loans.
This would also fulfill this request: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/38591101-my-account-previous-historic-requests