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).212 votes
Thank you for posting this idea. We will check the option to add such capability for Primo VE forms
Completed purchase requests (rejected or approved) should not be visible in the Primo MyAccount.127 votes
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 ,… )
The FRBR Dedup Test utility is currently hidden in Discovery configuration (Primo VE). The team members who need to use this functionality are cataloguers so they can see what edits might be needed to troubleshoot issues preventing or causing unexpected FRBR/deduplication.
Adding it to the Resources menu in Alma is an option, another might be for cataloguers to be able to trigger it when comparing records in the metadata editor.34 votes
Thank you for posting this suggestion, we moved it to idea under Primo VE instead of Alma and make it under review for analysis.
We 'd like the possibility to use translations in OTB Display fields, not only in local fields.
Use case: we want to use a code for contributors & creators ($4), rather than tag Relator term ($e) and use the translation functionality to display this role in the language of the interface.1 vote
Thank you for this suggestion. this is currently under review.
- Don't see your idea?