Enable authentication on purchase request web form
The customization options on the purchase request web form are great, but we cannot use it until the requestor can authenticate. We need to know who they are.
At present they appear as "Guest" in the request. An accident waiting to happen - when we update the requester to the wrong person.
Also we would only want this service available to institutional members, and would want to avoid mischievous use by unknown persons.
Clare Allan commented
Thanks Laura. To explain a bit about our use case. We use the Alma built in purchase request form for our students to suggest books and we use the Rialto purchase request form for our staff who want to request books be ordered. On the Rialto form we have extra fields that we wouldn't want to bother students with. For example: Research/Teaching, Module Code, Semester, Textbook/Core reading. So it would be very useful for us to have the option to add authentication to the Rialto form (and for those who don't want authentication they can leave switched off).
Laura Krier commented
There is already a purchase request form built into Alma that requires authentication. The web form, as I understand it, was specifically designed to create an option that does not require authentication.
Stacey van Groll commented
It would be very welcome for this Rialto version Purchase Request form to have a configuration option to require authentication and allow to show only to specific user groups.
Optional configuration would support those sites who currently use this feature without authentication, while also expanding potential use to sites who do need it to be authenticated.
The flow-on benefits for authentication would be to associate the requests to the Alma user account, just as is done for the Primo Purchase Request form.
We currently use the Primo version Purchase Request form, but it's notably less unattractive than the Rialto form, and a bit of a clunky workflow via Citation Linker.
But it allows for us to show it only to specific authenticated staff and student user groups by Display Logic Rules, as embedded within the GetIt, and is a nicely streamlined workflow overall for staff processing.
We can't use the Main Menu direct link option as our institution requires a standard header, and even if we could it does not allow to show only to specific user groups accounts.
Patricia Farnan commented
I need to go and free up some votes, but for now I'll add that I definitely support this change as well. We wouldn't be able to use the function if it doesn't require authentication by requesters.