Add Mandatory choices for all Request forms in Primo VE
For the Digitization Request, Hold and Booking Request, and Purchase Request forms, the Alma mapping tables (under GetIt Configuration) define the fields that are displayed to users (Yes = viewable to users, No = not viewable to users).
We would like to have the possibility to configure mandatory fields if we want the user to specify a field in the form (as it is already the case with a check box in the Resource Sharing Request form).
Thank you for posting this idea. We will check the option to add such capability for Primo VE forms
This would be extremely useful so that requests are actioned in a timely and satisfactory manner and avoid cancelations due to lack of information. this would prevent double handling (e.g. cancelling requests and then getting patrons re-requesting with extra details).
This would be really helpful! We have to reject a significant amount of requests because users have not included information that is necessary for us.
Kirstie N commented
We would like to see this also - especially for the digitisation request form, as users will place digitisation requests without specifying pagination or chapter details.
Would you please open this idea for all Primos and not just Primo VE?
m schwendener commented
Mike Rogers commented
Thanks for the idea, François. I agree - mandatory fields will be helpful for processing the requests. Often users will only fill out cursory information which can make it difficult to know exactly what they need. We have tried to "fool" the request form in the past by adding an asterisk at the beginning of the field (making it seem like the field is mandatory), but this isn't good practice. It would be more flexible if each institution could determine which fields should be mandatory.
We also would like Exlibris allow users to customize the form, for example add radio button for selections and fields for notes.
The existing purchase request form does not have
1. special notes field from users
2. a button or somewhere to indicate delivery option, e.g. hold or deliver to the user.
3. rush the order or not.
4. Show the print DDA purchase form link without login. We would like to show users that a purchase request is possible without requiring them login.
Thank you Francois,
I would add that it would be necessary to be able to configure the fields displayed according to the type of reference, and in addition to the possibility of making certain of them compulsory, to add some (holding fields).
Nicolas Cocman, Caen, France